
HSM UNIX Command-Line Help



Contents


1.0 What's new for version 8.1.13
2.0 HSM client command reference
  2.1 Standard option formats
  2.2 Help for commands
  2.3 Displaying file and file system information
  2.4 Client return codes
  2.5 HSM command summary
  2.6 dmkilld
  2.7 dsmattr
  2.8 dsmautomig
  2.9 dsmdf
  2.10 dsmdu
  2.11 dsmls
  2.12 dsmmigfs add and update
  2.13 dsmmigfs addmultiserver, querymultiserver, and removemultiserver
  2.14 dsmmigfs control
  2.15 dsmmigfs deactivate, reactivate, and remove
  2.16 dsmmigfs globaldeactivate and globalreactivate
  2.17 dsmmigfs help
  2.18 dsmmigfs query
  2.19 dsmmigfs rollback
  2.20 dsmmigfs enablefailover, and disablefailover
  2.21 dsmmigfs stop, start, and restart
  2.22 dsmmigfs takeover
  2.23 dsmmighelp
  2.24 dsmmigquery
    2.24.1 HSM and backup-archive client dsmmigquery command shared
    options
  2.25 dsmmigrate
  2.26 dsmmigundelete
  2.27 dsmmonitord
  2.28 dsmq
  2.29 dsmrecall
  2.30 dsmrecalld
  2.31 dsmreconcile
  2.32 dsmrm
  2.33 dsmscoutd
  2.34 dsmsetpw
  2.35 dsmwatchd
3.0 Options files reference
  3.1 afmskipuncachedfiles
  3.2 candidatesinterval
  3.3 checkfororphans
  3.4 checkthresholds
  3.5 compression
  3.6 defaultserver
  3.7 errorlogname
  3.8 errorprog
  3.9 hsmdisableautomigdaemons
  3.10 hsmdistributedrecall
  3.11 hsmenableimmediatemigrate
  3.12 hsmeventdestroy
  3.13 hsmextobjidattr
  3.14 hsmgroupedmigrate
  3.15 hsmlogeventflags
  3.16 hsmlogmax
  3.17 hsmlogname
  3.18 hsmlogretention
  3.19 hsmlogsampleinterval
  3.20 hsmmaxrecalltapedrives
  3.21 hsmmigzeroblockfiles
  3.22 hsmmultiserver
  3.23 hsmoptimizedrecallonly
  3.24 hsmrecallbufferalignment
  3.25 hsmrecallbuffersize
  3.26 hsmrpcport
  3.27 inclexcl
  3.28 maxcandprocs
  3.29 maxmigrators
  3.30 maxrecalldaemons
  3.31 maxthresholdproc
  3.32 migfileexpiration
  3.33 migrateserver
  3.34 minmigfilesize
  3.35 minrecalldaemons
  3.36 reconcileinterval
  3.37 restoremigstate
  3.38 skipmigrated
4.0 Display a message


1.0 What's new for version 8.1.13


Learn about new features and updates for IBM Spectrum Protect for Space
Management 8.1.13.

Table 1. New features and updates, and their associated IBM Spectrum
Protect for Space Management releases

+---------+-----------------------------------------------------------+
| Release | New features and updates                                  |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.13  | Maintenance updates                                       |
|         |                                                           |
|         |  Updates for APARs and other minor updates are provided.  |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.11  | Dsmreconcile command enhanced                             |
|         |                                                           |
|         |  The dsmreconcile command is enhanced and you now run     |
|         | reconcile on any HSM node to support large                |
|         | multiple-server environments. For more information, see   |
|         | dsmreconcile.                                             |
|         |                                                           |
|         | Maintenance updates                                       |
|         |                                                           |
|         |  Updates for APARs and other minor updates are provided.  |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.10  | New HSM option                                            |
|         |                                                           |
|         |  With this release, and the new hsmoptimizedrecallonly    |
|         | option, you can manage how the space management client    |
|         | handles non-optimized recall processes.                   |
|         |                                                           |
|         | GSKit signature checking                                  |
|         |                                                           |
|         |  With this release, you can now check the GSKit signature |
|         | of the rpm package before installation.                   |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.9   | Signature checking                                        |
|         |                                                           |
|         |  With this release, you can now check the signature of    |
|         | the space management client package before installation.  |
|         |                                                           |
|         | Maintenance updates                                       |
|         |                                                           |
|         |  Updates for APARs and other minor updates are provided.  |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.7   | New HSM options                                           |
|         |                                                           |
|         |  With this release, and the new hsmrpcport option, you    |
|         | can control which port is used to distribute recalls      |
|         | among the HSM client nodes. It also allows you to         |
|         | configure HSM communication across a firewall.            |
|         |                                                           |
|         |  In addition, the new hsmrecallbufferalignment and        |
|         | hsmrecallbuffersize options are added to control handling |
|         | of buffers for recalling files, and to increase           |
|         | performance.                                              |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.4   | New client platform                                       |
|         |                                                           |
|         |  With this release, IBM Spectrum Protect for Space        |
|         | Management contains a new client platform ( UNIX HSM)     |
|         | called Linux on Power Systems Little Endian.              |
|         |                                                           |
|         |  The dsmmigundelete command now supports the              |
|         | FILELIST=file_path parameter, which collects information  |
|         | for file list-based operations. Alternatively, you can    |
|         | use the script dsmmigundelete.pl to query the             |
|         | information. For further details, see dsmmigundelete .    |
|         |                                                           |
|         |  In addition, the hsmextobjidattr option changed its      |
|         | default value from No to Yes . For a description of this  |
|         | option, see hsmextobjidattr.                              |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.2   | dsmmigfs command updated to include a new control         |
|         | parameter and a new inlinecopymode option                 |
|         |                                                           |
|         |  With this release, the IBM Spectrum Protect for Space    |
|         | Management dsmmigfs command is updated to include a new   |
|         | control parameter. This parameter is used to dynamically  |
|         | change space management client options that are applied   |
|         | from running space management daemons.                    |
|         |                                                           |
|         |  In addition, the dsmmigfs command is updated to include  |
|         | a new inlinecopymode option with the update parameter.    |
|         | This option specifies how a backup operation handles a    |
|         | migrated file and applies only if backup operations are   |
|         | processed on migrated files.                              |
|         |                                                           |
|         |  For a description of this command, parameter, and        |
|         | option, see dsmmigfs control,dsmmigfs add and update ,    |
|         |                                                           |
+---------+-----------------------------------------------------------+
|         |                                                           |
| 8.1.0   | AIX JFS2 no longer supported                              |
|         |                                                           |
|         |  With this release, the IBM Spectrum Protect for Space    |
|         | Management is no longer supported on AIX Enhanced         |
|         | Journaled File System (JFS2) systems.                     |
|         |                                                           |
|         |  The space management client continues to be supported on |
|         | AIX General Parallel File Systems ( GPFS ) and Linux      |
|         | General Parallel File System ( GPFS ) systems.            |
|         |                                                           |
+---------+-----------------------------------------------------------+


2.0 HSM client command reference


You can use commands to do all HSM tasks. You must use the correct
syntax and format when you enter commands.

When you issue commands and options, follow these rules:

*  Do not precede HSM commands with dsmc. Each space management client
   command is a separately executable command.

*  Enter the complete command name in lowercase letters. You cannot use
   uppercase letters or an abbreviation for a command name.

*  Do not stop any HSM process with the command kill -9.

*  Use the following wildcard characters in file, directory, or file
   system specifications. The shell in which you are running matches and
   expands wildcard characters.

   *
            Matches zero or more characters
   ?
            Matches any single character

*  Enter the characters in a command in a continuous string without
   pressing the Return key. You can enter as many as 256 characters on
   the command line.


2.1 Standard option formats


You can specify options on some commands. You must use a standard format
to specify all options.

Follow these guidelines when you use an option:

*  Uppercase letters in each option description indicate the minimum
   abbreviation of a an option. Type the complete option name or an
   abbreviation of the name.

*  Issue options in any combination of uppercase and lowercase letters.
   Options are not case-sensitive.

*  Precede each option with a hyphen (-). For example:

     dsmmigquery -mgmtclass -detail /home   

*  Separate each option with a blank space.

*  Issue more than one option in a command in any order before or after
   a file, directory, or file system specification.

*  If the option defines a value, separate the option name from the
   value with an equal sign (=). For example:

   dsmmigfs update -ht=90 /home

The table gives examples of options that do not define a value.

Table 2. Option format examples: options without values

+---------------------------------------------------------------------+
| Command                                                             |
+---------------------------------------------------------------------+
| dsmmigrate -recursive -detail /home/user1/file1                     |
| dsmmigrate -rec -det /home/user1/file1                              |
| dsmmigrate -r -d /home/user1/file1                                  |
| dsmmigrate /home/user1/file1 -r -d                                  |
+---------------------------------------------------------------------+

The table gives examples of options when a value is defined.

Table 3. Option format examples: options with values

+---------------------------------------------------------------------+
| Command                                                             |
+---------------------------------------------------------------------+
| dsmmigfs update -hthreshold=90 -lthreshold=20 /home                 |
| dsmmigfs update -hthresh=90 -lthreshold=20 /home                    |
| dsmmigfs update -ht=90 -l=20 /home                                  |
| dsmmigfs update /home -ht=90 -l=20                                  |
+---------------------------------------------------------------------+

In version 6.4 and later, the optionformat option is not supported.
Short option format is not supported. You must specify all options with
the standard option format.


2.2 Help for commands


Use the help option to display help for each command-line command or use
the dsmmighelp command.

You can display online help for HSM commands in either of the following
ways:

*  Issue the help option with any command. For example:

     dsmmigrate -help
     dsmmigrate -h

*  Issue the dsmmighelp command. A list of help topics displays from
   which you can select general help information for commands, help for
   a specific command, or help for a message.

Proper display of the help text requires a usable display width of 72
characters. A display width that is fewer than 72 characters causes
sentences that are 72 characters wide to wrap to the next line.Wrapping
can cause the displayed help text to begin somewhere within the section
rather than at the beginning. The skipped lines can be viewed by using
the terminal's scrolling function to move up.


2.3 Displaying file and file system information


There is a set of HSM commands you can use to display space management
information about your file systems, files, and directories.

Table 4. HSM commands to display file and file system information

   
  Command         Description                                          
 ---------------+----------------------------------------------------- 
  dsmdf           Displays space usage information for a file system.  
                  For example, to display space usage information for  
                  the /home file system, issue the following command:  
                   dsmdf /home                                         
 ---------------+----------------------------------------------------- 
  dsmls           Lists files in a directory and displays file         
                  conditions. For example, to display information      
                  about all files in the /home/user1 directory, issue  
                  the following command:                               
                   dsmls /home/user1/*                                 
 ---------------+----------------------------------------------------- 
  dsmdu           Displays space usage information for files and       
                  directories. For example, to display space usage     
                  information for each file in the /home/user/proj1    
                  directory and in all of its subdirectories, issue    
                  the following command:                               
                   dsmdu -Allfiles /home/user1/proj1                   
 ---------------+----------------------------------------------------- 
  dsmmigfs        Displays the current space management settings for   
  query           a file system. For example, to display the space     
                  management settings for the /home file system,       
                  issue the following command:                         
                   dsmmigfs query /home                                
 ---------------+----------------------------------------------------- 
  dsmmigundelet   Recreates deleted stub files for migrated files and  
  e               creates stub files for premigrated files if a        
                  corresponding original file does not exist on your   
                  local file system. The file then becomes a migrated  
                  file. For example, to recreate stub files for        
                  migrated files in the /home file system that are     
                  not marked for expiration (reconciliation was not    
                  run since the files were deleted) issue the          
                  command:                                             
                   dsmmigundelete /home                                



2.4 Client return codes


The space management client command-line interface exits with return
codes that accurately reflect the success or failure of the operation.

Scripts, batch files, and other automation facilities can use the return
code from the command-line interface. For operations that use the IBM
Spectrum Protect scheduler, the return codes are shown in the output of
the QUERY EVENT administrative command. For cases where the return code
is not 0, you can examine the dsmerror.log file. For scheduled events,
you can examine the dsmsched.log file.

Return codes have the following meanings:

Table 5. An explanation of client return codes

+---------+-----------------------------------------------------------+
| Code      Explanation                                               |
+---------+-----------------------------------------------------------+
| 0         All operations completed successfully.                    |
+---------+-----------------------------------------------------------+
| 4         The operation completed successfully, but some files were |
|           not processed. There were no other errors or warnings.    |
|           This return code is common. In most cases, files are not  |
|           processed for the following reasons:                      |
|            * The file satisfies an entry in an exclude list.        |
|           Excluded files generate log entries only during selective |
|           backups.                                                  |
|            * The file was in use by another application and could   |
|           not be accessed by the client.                            |
|            * The file changed during the operation to an extent     |
|           prohibited by the copy serialization attribute.           |
+---------+-----------------------------------------------------------+
| 8         The operation completed with at least one warning         |
|           message. Review the dsmerror.log file to determine what   |
|           warning messages were issued and to assess their effect   |
|           on the operation.                                         |
+---------+-----------------------------------------------------------+
| 12        The operation completed with at least one error message   |
|           (except for error messages for skipped files). For        |
|           scheduled events, the status is Failed . Review the       |
|           dsmerror.log file to determine what error messages were   |
|           issued and to assess their effect on the operation.       |
|           Generally, this return code means that the error was      |
|           severe enough to prevent the successful completion of the |
|           operation. For example, an error that prevents an entire  |
|           file system from being processed yields return code 12.   |
+---------+-----------------------------------------------------------+

The return code for a client macro is the highest return code issued
among the individual commands that comprise the macro. For example,
suppose that a macro consists of these commands:

selective "/home/devel/*" -subdir=yes
incremental "/home/devel/TestDriver/*" -subdir=yes
archive "/home/plan/proj1/*" -subdir=yes

If the first command completed with return code 0; the second command
completed with return code 8; and the third command completed with
return code 4, the return code for the macro is 8.


2.5 HSM command summary


The following is an alphabetical list of the HSM client commands and a
brief description of each one.

Table 6. HSM command summary

+-------------+-------------------------------------------------------+
| Command       Description                                           |
+-------------+-------------------------------------------------------+
| dmkilld       Valid only on GPFS file systems. Stops the master     |
|               recall daemon and all of its child processes, and     |
|               interrupts all active recalls.                        |
+-------------+-------------------------------------------------------+
| dsmattr                                                             |
|               Sets or displays the recall mode for a migrated file. |
+-------------+-------------------------------------------------------+
| dsmautomig    Starts parallel migration session for a file system.  |
+-------------+-------------------------------------------------------+
| dsmdf         Displays space usage information for a file system.   |
+-------------+-------------------------------------------------------+
| dsmdu         Displays space usage information for files and        |
|               directories.                                          |
+-------------+-------------------------------------------------------+
| dsmls         Lists files in a directory and displays file state.   |
+-------------+-------------------------------------------------------+
| dsmmigfs                                                            |
+-------------+-------------------------------------------------------+
|     add and   Adds space management to a file system, or updates    |
|      update   space management attributes for a file system.        |
+-------------+-------------------------------------------------------+
|  deactivate   Deactivates or reactivates space management for a     |
|           ,   file system, or removes space management from a file  |
| reactivate,   system.                                               |
| and remove                                                          |
+-------------+-------------------------------------------------------+
| enablefailo   Valid only on GPFS file systems.                      |
|   ver , and   Manages recovery from partial system failure.         |
| disablefail                                                         |
|        over                                                         |
+-------------+-------------------------------------------------------+
|       query   Displays current space management settings for a file |
|               system.                                               |
+-------------+-------------------------------------------------------+
| globaldeact   Deactivates or reactivates space management for your  |
|     ivate ,   client node.                                          |
| globalreact                                                         |
|       ivate                                                         |
+-------------+-------------------------------------------------------+
|    rollback   Valid only on GPFS file systems.                      |
|               Transfers the space management of a file system to an |
|               HSM client node within the same local IBM Spectrum    |
|               Scale node set.                                       |
+-------------+-------------------------------------------------------+
|      stop ,   Only valid on IBM Spectrum Scale AIX and IBM Spectrum |
| start , and   Scale Linux                                           |
|     restart   Stops, starts, and restarts daemons.                  |
+-------------+-------------------------------------------------------+
|    takeover   Valid only on GPFS file systems.                      |
|               Transfers the space management of a file system to    |
|               the preferred node if the node is different from the  |
|               current owner node.                                   |
+-------------+-------------------------------------------------------+
| dsmmighelp    Displays online help for commands.                    |
+-------------+-------------------------------------------------------+
| dsmmigquery   Displays space management information.                |
|               There are many space management client and            |
|               backup-archive client shared options available using  |
|               the dsmmigquery -o command.                           |
+-------------+-------------------------------------------------------+
| dsmmigrate    Moves selected files from your local file system to   |
|               IBM Spectrum Protect storage.                         |
+-------------+-------------------------------------------------------+
| dsmmigundel   Re-creates deleted stub files.                        |
| ete                                                                 |
+-------------+-------------------------------------------------------+
| dsmmonitord   Starts the space monitor daemon.                      |
+-------------+-------------------------------------------------------+
| dsmq          Displays information, including recall IDs, for all   |
|               files that are currently queued for recall.           |
+-------------+-------------------------------------------------------+
| dsmrecall     Moves selected files from storage to your local file  |
|               system.                                               |
+-------------+-------------------------------------------------------+
| dsmrecalld    Starts the recall daemon.                             |
+-------------+-------------------------------------------------------+
| dsmreconcil   Synchronizes the client and server.                   |
| e                                                                   |
+-------------+-------------------------------------------------------+
| dsmrm         Removes a recall process from the recall queue.       |
+-------------+-------------------------------------------------------+
| dsmscoutd     Starts, stops, and restarts the scout daemon and      |
|               provides scan information.                            |
+-------------+-------------------------------------------------------+
| dsmsetpw      Changes the IBM Spectrum Protect password for your    |
|               client node.                                          |
+-------------+-------------------------------------------------------+
| dsmwatchd     Checks the other space management daemons and starts  |
|               them again when necessary.                            |
|                                                                     |
+-------------+-------------------------------------------------------+


2.6 dmkilld


The dmkilld command stops the master recall daemon and all of its
children and interrupts all active recalls.

This command is valid only on GPFS file systems.

Syntax

>>-DMKILLD--+---------+----------------------------------------><
            '-options-'   



Parameters

options
         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.


2.7 dsmattr


The dsmattr command sets or changes the recall mode for one or more
migrated files. The recall mode determines how the space management
client recalls a migrated file when you access it.

You cannot set a recall mode for a resident or a premigrated file. The
recall mode that you set for a migrated file remains associated with
that file only while the file remains migrated.

If you do not specify any parameters, the command displays the current
recall mode, stub size, preview size, file name, and whether the
readstartsrecall option is set.

Syntax

                         .------------------------------.   
                         V                              |   
>>-DSMATTR--+---------+----+--------------------------+-+------><
            '-options-'    +-filespec-----------------+     
                           '- -FIlelist--=--file_path-'     



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -PREViewsize=n
                  Specifies the preview size of the stub file. Valid
                  values are 0 - 1,073,741,824, and must not be greater
                  than the stub size.

                  When the attributes are set and the preview size is
                  defined, a recall operation begins only when an
                  application reads the stub file beyond the preview
                  section of the stub file. If an operation reads only
                  the preview section of the stub file, the file is not
                  recalled.

         -REAdstartsrecall=No|Yes
                  Specifies whether a recall operation starts when an
                  application reads the stub file.

                  This option applies only if streaming recall mode is
                  set.

                  If the previewsize option is set for the stub file, a
                  recall operation starts only when an application reads
                  beyond the preview section of the stub file.

                  The default value is No.

                  Regardless of the value of the readstartsrecall
                  option, the file is recalled when either of the
                  following conditions are true:

                  *  The recall daemon determines that the stub file
                     does not contain all of the data that is required
                     by a read operation.

                  *  An operation modifies the file.

         -RECAllmode=value
                  Sets a recall mode for one or more migrated files. If
                  you do not specify the RECAllmode option, the space
                  management client displays the current recall mode for
                  the files that you specify. You can specify the
                  following values:

                  Normal
                           Recalls the migrated file to its originating
                           file system.Normal is the default. If the
                           file is not modified, it becomes a
                           premigrated file. If the file is modified, it
                           becomes a resident file.

                  Partialrecall
                           Specifies that the file is recalled by using
                           partial file recall, regardless of its size.
                           Valid only on GPFS file systems.

                  Streaming
                           Specifies that you want to enable an
                           asynchronous recall of migrated files. The
                           recalled portion of the file can be accessed
                           while the file is recalled. This parameter is
                           valid for read-only operations on the file.

         -RECUrsive
                  Sets or displays the recall mode for migrated files in
                  the directory and subdirectories that you specify.

filespec
         Note: This parameter is required only when you set a new recall
         mode. If you do not use the RECAllmode option, and you do not
         specify a path and a file name, the current recall mode
         displays for all files in the current directory.

         The path and file name of the file for which you want to set a
         new recall mode, or display the current recall mode. You can
         specify a single file, a group of files, or a directory. If you
         specify a directory, the space management client sets or
         displays that recall mode for each migrated file in the
         directory.

         You can use wildcard characters to specify a group of files
         with similar names. You can issue more than one file
         specification in a command. If you enter several file
         specifications, separate each specification with one or more
         blank spaces.

-FIlelist=file_path
         Specifies the path of a file that contains a list of files to
         be processed by this command.

         The entries in the list file must adhere to the following
         rules:

         *  Each entry is a fully qualified path to a file or a relative
            path to a file.

         *  No entry is a directory object.

         *  Each entry is on a separate line.

         The space management client ignores any entry that does not
         adhere to these rules.

         The following rules apply to a file list for the space
         management client. These rules differ from the rules for
         backup-archive client file lists.

         *  An entry can contain unprintable characters, but cannot
            contain a carriage return.

         *  Wildcard characters are allowed.

         *  A file path that contains blank spaces must be enclosed in
            quotation marks.

         *  An entry that begins with a quotation mark and ends with a
            quotation mark is tolerated. The space management client
            assumes that the quotation marks are not needed and omits
            them when the space management client processes the entry.
            If beginning and ending quotation marks are required to
            identify the file, add double quotation marks before the
            beginning and after the end of the entry.

         The following example shows a list of files within a list file:

           /home/dir/file1
           "/fs1/dir2/file3"
           "/fs2/my files/file4"
           ../tivoli/'file1'
           "'fs3'/dir3/'file.txt'"
           fs4/dir/a"file".txt
           '/fs4/dir/file.txt'
           /fs5/dir/file*with?wildcards.txt

         If the list file name that you specify with the filelist option
         does not exist, the command fails.

Examples

   
  Task                                   Command                       
 --------------------------------------+------------------------------ 
  Change the recall mode to partial      dsmattr                       
  file recall for all migrated files     -recall=partialrecall         
  in the /home/user2 directory and all   -Recursive /home/user2        
  of its subdirectories.                                               
 --------------------------------------+------------------------------ 
  Enable an asynchronous recall of       dsmattr -recall=streaming     
  migrated files in the /home/user2/     /home/user2/                  
  directory.                                                           
 --------------------------------------+------------------------------ 
  On the /myfs file system, stub files   dsmattr -preview=4096         
  are 32,768 bytes. For the migrated     -readstartsrecall=yes         
  files that are listed in files.lst ,   -recall=streaming             
  set the preview size to 4,096 bytes.   -filelist=/myfs/files.lst     
  If an application reads more than                                    
  the preview section of any of these                                  
  stub files, start the recall                                         
  process. (Streaming recall mode is a                                 
  requirement to start the recall                                      
  after an application reads the                                       
  preview section).                                                    
 --------------------------------------+------------------------------ 
  Display the recall attributes that     dsmattr                       
  are assigned to all files in the                                     
  current directory.                                                   
 --------------------------------------+------------------------------ 
  Display all files in the file list     dsmattr                       
  that is named /tmp/filelist.           -filelist=/tmp/filelist       



2.8 dsmautomig


The dsmautomig command starts parallel migration sessions to the IBM
Spectrum Protect server, migrating more than one file at a time.

You must have root user authority to use this command.

The dsmautomig command checks:

*  If a migration candidate requires a current backup version on the TDP
   for IBM(R) Lotus Notes(R) IBM Spectrum Protect server.

*  If a current backup version exists.

If the LANG environment variable is set to C, POSIX, only characters
with ASCII codes less than 128 are valid. The HSM client skips files
that have file names that contain invalid characters. If you are using a
single-byte character set (SBCS) such as English as your language
environment, all file names are valid and are migrated by the space
management client.

Multi-byte characters are interpreted as a set of single bytes all
containing valid characters. If you are using multi-byte character sets
(MBCS) as your language environment, the HSM client migrates file names
that consist of valid characters in the current environment. For
example, a file name consisting of Japanese characters might contain
invalid multi-byte characters if the current language environment is a
Chinese character set. File names containing invalid multi-byte
characters are not migrated or recalled. If such files are found during
migrate or recall no information is printed. The HSM daemons must run in
the en_US language locale to work properly.

Specify the number of parallel migration sessions with the maxmigrators
option in your dsm.sys file. Verify that sufficient resources are
available on the IBM Spectrum Protect server for parallel migration. Do
not set the maxmigrators option higher than the number of sessions that
the IBM Spectrum Protect server can use to store data. Start threshold
migration manually to reduce space usage on your file system before it
reaches the high threshold that you set.

Hidden directories and files are included in automatic migration. Files
can be excluded from automatic migration by adding the hidden
directories or files to the exclude list in the dsm.opt file.

The scout daemon (dsmscoutd) should be running if you start the
dsmautomig command manually. Otherwise, the dsmautomig command might not
be able to complete the migration if it runs out of candidates from the
candidates list.

The dsmautomig command must be found with the PATH variable, or the
dsmmonitord daemon cannot complete threshold migration.

Note: The HSM client does not migrate contents of symbolic links.

Syntax

>>-DSMAUTOMIG--------------------------------------------------->

   .-------------------------------------------------.   
   V                                                 |   
>----+---------------------------------------------+-+---------->
     +-filesystemspec------------------------------+     
     '-storage_pool_name::absolute_filesystem_path-'     

>--+---------+-------------------------------------------------><
   '-options-'   



Parameters

filesystemspec
         Specifies the name of the file system for which you want to run
         threshold migration. The default is all file systems for which
         space management is active. You can specify more than one file
         system name, and you can use wildcard characters within a file
         system name. If you specify more than one file system name,
         separate each name with one or more blank spaces.

storage_pool_name::absolute_filesystem_path
         Specifies the storage pools that are in the
         absolute_filesystem_path path that are migrated automatically.

options
         -Detail
                  Displays information about migrated files.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

Examples

   
  Task                                           Command               
 ----------------------------------------------+---------------------- 
  Start threshold migration for all storage      dsmautomig            
  pools on all file systems for which space                            
  management is active.                                                
 ----------------------------------------------+---------------------- 
  Start threshold migration for all storage      dsmautomig /home      
  pools in the /home file system.                                      
 ----------------------------------------------+---------------------- 
  Start threshold migration for all storage      dsmautomig /home      
  pools in the /home and /test1 file systems.    /test1                
 ----------------------------------------------+---------------------- 
  Start threshold migration for the storage      dsmautomig            
  pools that are named silver and gold for the   /silver::/fs1         
  /fs1 file systems.                             gold::/fs1            
 ----------------------------------------------+---------------------- 
  Start threshold migration for all storage      dsmautomig            
  pools in the /fs2 file systems and for the     gold::/fs1 /fs2       
  storage pool that is named gold in the /fs1                          
  file systems.                                                        



2.9 dsmdf


The dsmdf command displays the information for one or more file systems,
such as file system state, inode information, and space information.

Specifically, the dsmdf command displays information about:

*  File system state: active (a), inactive (i), or global inactive (gi)
*  Sum of the sizes of all migrated files
*  Amount of space that is used on your local file system for
   premigrated files
*  Number of inodes that are used for migrated or premigrated files
*  Number of unused inodes on your local file system
*  Amount of free space on your local file system

Only migration and recall processes dynamically update status
information for your file systems. If any other process changes the
state of a file, the change is not reflected in the information that the
dsmdf command displays until reconciliation is run.

For GPFS file systems only:
         Migrating newly created files less than five (5) minutes old
         might display incorrect results (resident size) when you use
         the dsmdf and dsmdu commands. The reason is because IBM
         Spectrum Scale is not synchronized on all nodes when you
         migrate files. The last block of a file is not released from
         the disk although the file migrated successfully. This
         procedure can cause a deviation from an assumed disk usage if
         many small files are migrated and the block size is high.

Note: You can display only information about mounted file systems. If a
file system is space managed but not mounted, it does not appear within
the command output.



Syntax

>>-+-DSMDF-+--+---------+--+--------------------+--------------><
   '-DDF---'  '-options-'  | .----------------. |   
                           | V                | |   
                           '---filesystemspec-+-'   



Parameters

options
         -Detail
                  Displays information about file systems with each
                  value appearing on its own line. Values representing
                  the amount of space is shown in kilobytes only.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

filesystemspec
         The name of the file system for which you want to display
         information. The default is all file systems to which you added
         space management. You can specify more than one file system
         name, and you can use wildcard characters within a file system
         name. If you specify more than one file system name, separate
         each name with one or more blank spaces.

Examples

   
  Task                    Command                                      
 -----------------------+--------------------------------------------- 
  Display information     dsmdf                                        
  for all file systems                                                 
  to which you added                                                   
  space management.                                                    
 -----------------------+--------------------------------------------- 
  Display information     dsmdf /home                                  
  for the /home file                                                   
  system.                                                              
 -----------------------+--------------------------------------------- 
  Specify the log file    dsmdf -Logname=mylogfile                     
  to be used by the       dsmdf -detail -Logname=/tmp/dsmdflog /home   
  dsmdf command           dsmdf -d -L=mylogfile                        



2.10 dsmdu


The dsmdu command displays space usage information for files and
directories. For migrated files, the dsmdu command uses the actual size
of the files that are stored in IBM Spectrum Protect storage to
calculate space usage. In contrast, the du command (provided with your
operating system) uses the size of the stub files that are stored in
your local file system.

This command is valid only on GPFS file systems.

The dsmdf and dsmdu commands can display incorrect resident file size
when you migrate newly-created files. This is because IBM Spectrum Scale
is not synchronized on all nodes when you migrate files. The last block
of a file is not released from the disk although the file migrated
successfully. This can cause deviation from assumed disk usage if many
small files are migrated and blocksize is high.

Attention: Running dsmls or dsmdu on remotely mounted GPFS file systems
might show incorrect values. See Table 7 for an example of this
situation.

Table 7. Space management for locally and remotely mounted file systems

+----------------------------------+----------------------------------+
| Cluster A                        | Cluster B                        |
+----------------------------------+----------------------------------+
| A space management client is     | A space management client is     |
| installed                        | installed                        |
+----------------------------------+----------------------------------+
| File system A                    | File system A (from Cluster A    |
|                                  | remotely mounted on Cluster B)   |
+----------------------------------+----------------------------------+
| Mounted locally                  | Mounted remotely                 |
+----------------------------------+----------------------------------+
| Space-managed by A               | Not Space-managed by B           |
+----------------------------------+----------------------------------+



Only file systems of the local cluster can be managed by HSM. The local
Cluster A file system is space-managed by Cluster A, but cannot be
space-managed by Cluster B, although it is remotely mounted on Cluster
B. The Data Management Application Programming Interface (DMAPI)
interface does not work for remotely mounted file systems, so incorrect
values might be reported by dsmls or dsmdu.

Syntax

>>-+-DSMDU-+--+---------+--+-------------------+---------------><
   '-DDU---'  '-options-'  | .---------------. |   
                           | V               | |   
                           '---directoryspec-+-'   



Parameters

options
         If you do not specify either of the following options, the
         space management client displays the number of 1 KB blocks that
         the specified directory and each of its subdirectories use.

         -Allfiles
                  Displays the number of 1 KB blocks that each file in
                  the specified directory and each of its subdirectories
                  use.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -Summary
                  Displays only the total of 1 KB blocks that the
                  specified directory and its subdirectories use.

directoryspec
         The directory for which you want to display information. The
         default is the current directory and its subdirectories. Use
         wildcard characters to specify more than one directory. You can
         issue more than one directory specification in one command. If
         you issue several directory specifications, separate each name
         with one or more blank spaces.

Examples

   
  Task                                          Command                
 ---------------------------------------------+----------------------- 
  Display space usage information for the       dsmdu                  
  current directory and all of its                                     
  subdirectories.                                                      
 ---------------------------------------------+----------------------- 
  Display space usage information for the       dsmdu /migfs3/test     
  /migfs3/test directory and all of its                                
  subdirectories.                                                      
 ---------------------------------------------+----------------------- 
  Display space usage information for each      dsmdu -a /migfs2/test  
  file in the /migfs2/test directory and in                            
  all of its subdirectories.                                           
 ---------------------------------------------+----------------------- 
  Display the total number of 1 KB blocks       dsmdu -Summary         
  that the /migfs2/test directory and all of    /migfs2/test           
  it subdirectories use.                                               



2.11 dsmls


The dsmls command displays file information, such as sizes and state.

Specifically, the dsmls command displays the following information about
a list of files:

*  Actual size (in bytes)
*  Resident size (in bytes)
*  Resident block size (in KB)
*  File state and recall mode
*  Name of the coupled IBM Spectrum Protect server
*  File name

For a resident or premigrated file, the actual size and resident size
are the same. For a migrated file, the actual size is the size of the
original file. The resident size is the size of the stub file that
remains on your local file system.

The file state for a file can have any of the following values: migrated
(m), premigrated (p), or resident (r)). A dash - indicates a directory
or a non-regular file; for example, a character special file or a named
pipe file. For a migrated file, the dsmls command also indicates the
recall mode that you set for the file:

*  If you set the recall mode to normal, additional information does not
   appear in the file state column.
*  If you set the recall mode to partial file recall, the notation (p)
   displays in the file state column.
*  If you set the recall mode to streaming, the notation (s) displays in
   the file state column.

Restriction:

*  Running dsmls or dsmdu on remotely mounted GPFS file systems might
   show incorrect values. Consider the following example:

Table 8. Space management for locally and remotely mounted file systems

+---------------------+-----------------------------------------------+
| Cluster A           | Cluster B                                     |
+---------------------+-----------------------------------------------+
| A space management  | A space management client is installed        |
| client is installed |                                               |
+---------------------+-----------------------------------------------+
| File system A       | File system A (from Cluster A remotely        |
|                     | mounted on Cluster B)                         |
+---------------------+-----------------------------------------------+
| Mounted locally     | Mounted remotely                              |
+---------------------+-----------------------------------------------+
| Space-managed by A  | Not Space-managed by B                        |
+---------------------+-----------------------------------------------+

Only file systems of the local cluster can be managed by HSM. The local
Cluster A file system is space-managed by Cluster A, but cannot be
space-managed by Cluster B, although it is remotely mounted on Cluster
B. The Data Management Application Programming Interface (DMAPI)
interface does not work for remotely mounted file systems, so incorrect
values might be reported by dsmls or dsmdu.

Syntax

                           .------------------------------.   
                           V                              |   
>>-+-DSMLS-+--+---------+----+--------------------------+-+----><
   '-DLS---'  '-options-'    +-filespec-----------------+     
                             '- -FIlelist--=--file_path-'     



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -Noheader
                  Omits column headings from the output for this
                  command.

         -Recursive
                  Displays information about files in subdirectories of
                  the directory.

filespec
         The path name for the files that you want to list. The default
         is all files in the current directory. Use wildcard characters
         to specify a group of files or all the files in a directory.
         You can enter more than one file specification in a command. If
         you enter several file specifications, separate each
         specification with one or more blank spaces.

-FIlelist=file_path
         Specifies the path of a file that contains a list of files to
         be processed by this command.

         The entries in the list file must adhere to the following
         rules:

         *  Each entry is a fully qualified path to a file or a relative
            path to a file.

         *  No entry is a directory object.

         *  Each entry is on a separate line.

         The space management client ignores any entry that does not
         adhere to these rules.

         The following rules apply to a file list for the space
         management client. These rules differ from the rules for
         backup-archive client file lists.

         *  An entry can contain unprintable characters, but cannot
            contain a carriage return.

         *  Wildcard characters are allowed.

         *  A file path that contains blank spaces must be enclosed in
            quotation marks.

         *  An entry that begins with a quotation mark and ends with a
            quotation mark is tolerated. The space management client
            assumes that the quotation marks are not needed and omits
            them when the space management client processes the entry.
            If beginning and ending quotation marks are required to
            identify the file, add double quotation marks before the
            beginning and after the end of the entry.

         The following example shows a list of files within a list file:

           /home/dir/file1
           "/fs1/dir2/file3"
           "/fs2/my files/file4"
           ../tivoli/'file1'
           "'fs3'/dir3/'file.txt'"
           fs4/dir/a"file".txt
           '/fs4/dir/file.txt'
           /fs5/dir/file*with?wildcards.txt

         If the list file name that you specify with the filelist option
         does not exist, the command fails.

Examples

   
  Task                                       Command                   
 ------------------------------------------+-------------------------- 
  List all files in the current directory.   dsmls                     
 ------------------------------------------+-------------------------- 
  List all files in the /migfs2/test         dsmls /migfs2/test        
  directory.                                                           
 ------------------------------------------+-------------------------- 
  List all files in the /migfs2/test         dsmls -Recursive          
  directory and in its subdirectories.       /migfs2/test              
 ------------------------------------------+-------------------------- 
  List all files whose names begin with tf   dsmls /migfs2/test/tf*    
  in the /migfs2/test directory.                                       
 ------------------------------------------+-------------------------- 
  List all files in the list file named      dsmls                     
  /tmp/filelist.                             -filel=/tmp/filelist      



2.12 dsmmigfs add and update


Use the dsmmigfs command with the add parameter to add space management
to the file system. Use the dsmmigfs command with the update parameter
to update space management settings for your file system.

You must have root user authority to use this command.

For information about configuring IBM Spectrum Scale integration with
the space management client, see Technote 7018848.

Before you run dsmmigfs add filesystem on GPFS file systems, ensure that
the file system is mounted and enabled for Data Management Application
Programming Interface (DMAPI) management. Issue the following commands:

For GPFS file systems:

  /usr/lpp/mmfs/bin/mmlsfs DevicePath -z

If it is required, change the value as follows:

  /usr/lpp/mmfs/bin/mmchfs DevicePath -z yes 

Run only one dsmmigfs command within the local IBM Spectrum Scale node
group at the same time.

You cannot add space management to your root ( / ), /tmp, /usr, or /var
file systems.

Note: You can query only information about mounted file systems. If a
file system is space-managed, but not mounted, it does not show up
within the query command

Syntax

                                      .--------------------.   
                                      V                    |   
>>-DSMMIGFS--+-Add----+--+---------+------filesystemSpec---+---><
             '-Update-'  '-options-'                           



Parameters

Add
         Adds space management to your file systems.

Update
         Updates one or more space management settings for a file system
         to which you added space management.

         If you change the high and low thresholds or the premigration
         percentage, the new values take effect immediately. If you
         change the stub file size, the new size is used for files that
         are migrated after the change. The size of existing stub files
         does not change.

         If you change the minmigfilesize option value, the new value is
         used the next time a migration candidates list is built. Also,
         the new value is used only for files that are migrated after
         the value is changed.

         If you change the readstartsrecall option value, the new value
         is used only for files that are migrated after the value is
         changed.

         You can set the quota to less than the amount of currently
         migrated and premigrated data. No more files are migrated until
         automatic and selective recalls reduce the amount of currently
         migrated and premigrated data to less than the new quota.

filesystemSpec
         Specifies a file system name. You can specify more than one
         file system name, and you can use wildcard characters within a
         file system name. If you specify more than one file system
         name, separate each name with one or more blank spaces.

options
         Use the option settings that are provided for this command to
         add or update space management settings.

         On GPFS file systems, you can use the GPFS policy engine to
         monitor space thresholds and search for migration candidates.
         If you configure the GPFS policy engine to drive automatic
         migration, the following options for the dsmmigfs command have
         no consequence:

         *  hthreshold

         *  lthreshold

         *  maxcandidates

         *  maxfiles

         *  minpartialrecallsize

         *  minmigfilesize

         -HThreshold=n
                  Specifies the high threshold percentage that you set
                  for space usage on your file systems. Specify a value
                  of 0 -100 percent. The default is 90 percent.

         -Lthreshold=n
                  Specifies the low threshold percentage that you set
                  for space usage on your file systems. Specify a value
                  of 0 through 100 percent. The default is 80 percent.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -INlinecopymode=MIG|PREMIG|OFF
                  Specifies how a backup operation handles a migrated
                  file. This option applies only if backup operations
                  are processed on migrated files.
                  If the inlinecopymode option is set to MIG and a
                  migrated file is a candidate for a backup the file
                  will be cloned inside the space management storage
                  pool in the IBM Spectrum Protect server. The clone of
                  the file will be stored in the backup storage pool in
                  the IBM Spectrum Protect server. This operation is
                  called inline copy.
                  If the inlinecopymode option is set to PREMIG and a
                  premigrated or a migrated file is a candidate for
                  backup the file the inline copy will happen.
                  If the inlinecopymode option is set to OFF and a
                  migrated file is a candidate for backup the file will
                  be recalled and the file state will change to
                  premigrated. Then the backup processing will happen.

                  Note: The backup of a migrated file is impossible if
                  the 3.23 hsmoptimizedrecallonly option is set to YES,
                  and inlinecopymode option is set to OFF.
                  The inline copy function will be automatically
                  disabled if one of the following takes place:

                  *  The space management storage pool and the backup
                     storage pool are not stored in the same IBM
                     Spectrum Protect server instance.

                  *  The file to be backed up has ACL or extended
                     attribute metadata.
                  Note:

                  *  The inline copy prevents data transfer between the
                     IBM Spectrum Protect backup-archive client and the
                     IBM Spectrum Protect server for backup processing
                     and can be used if the file has a valid copy in the
                     space management storage pool.

                  *  IBM Spectrum Protect container storage pools do not
                     support cloning. If container storage pools are
                     used for space management data the inlinecopymode
                     option must be set to OFF.
                  The default value is MIG.

         -LOGname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

         -Maxcandidates=n
                  Specifies the maximum number of migration candidates
                  the dsmscoutd daemon delivers to the automatic
                  migration process during automigration. A value 50 -
                  1000 is sufficient for good performance. The
                  acceptable range is 9 - 9999999. The default is 10000.

         -MAXFiles=n
                  Specifies the maximum number of files for which the
                  CFI database is sized. The acceptable range is 0 -
                  4294967295. The default is 0.

                  If the specified value is less than the number of
                  currently used blocks, an error occurs. The value must
                  be greater than the current number of files in the
                  file system. The value must be less than the total
                  likely number of inodes.

                  You can configure the size of the complete file index
                  (CFI). This value can be queried or set with the
                  maxfiles parameter. If this parameter is set to 0, the
                  CFI allocates the maximum required space. The maximum
                  required space is the maximum number of blocks that
                  are possible in the file system. Less file system
                  space is needed to create the CFI. If the specified
                  value is out of bounds, the nearest boundary is used
                  to allocate the configurable CFI size.

         -MINMigfilesize=n
                  Specifies the minimum size (in bytes) for a file to
                  qualify for migration. The size is the space that a
                  file occupies on the file system. Valid values are 0 -
                  2147483647. The default is 0. If you specify 0, the
                  space management client uses the current file system
                  stub size plus 1 byte as the minimum size for files
                  that can be migrated. If you specify a nonzero value,
                  the value must be greater than the current file system
                  stub size. A valid value for a file system takes
                  precedence over the global minmigfilesize option
                  setting that is specified in the dsm.sys file.

         -MINPartialrecallsize=n
                  Specifies the minimum size (in megabytes) for a file
                  to qualify for partial file recall. The acceptable
                  range is 0 - 999999999. The default value of 0
                  disables partial file recall for all files.

                  Valid only on GPFS file systems.

         -MINStreamfilesize=n
                  Specifies the minimum file size (in megabytes) for
                  streaming recall mode. Streaming recall mode is set
                  for files that are larger than the value of the
                  minstreamfilesize option. Smaller files are recalled
                  in normal recall mode.

                  Valid values are 0 - 999999999. The default is 0.

                  During a streaming recall, the recalled part of the
                  file can be accessed before the complete file is
                  recalled.

                  Note: Regardless of the STREAMSeq value, all incoming
                  read data events are pending until at least the
                  MINStreamfilesize value is first recalled. All
                  subsequent read data events are responded to as soon
                  as the STREAMSeq value portion, that covers the
                  appropriate read data event offset, is written back to
                  the local file system.

         -Pmpercentage=n
                  Specifies the percentage of file system space that is
                  available to contain premigrated files. The minimum
                  value is 0. The maximum value is the low threshold. A
                  warning is displayed if the premigration percentage is
                  greater than the difference between the low threshold
                  and the minimum size of the file system. A
                  premigration percentage greater than this difference
                  can result in insufficient space for the file system,
                  and can result in endless attempts to find
                  premigration candidates.

         -PREViewsize=n
                  Specifies the preview size of the stub file. Valid
                  values are 0 - 1,073,741,824, and must not be greater
                  than the stub size.

                  When the attributes are set and the preview size is
                  defined, a recall operation begins only when an
                  application reads the stub file beyond the preview
                  section of the stub file. If an operation reads only
                  the preview section of the stub file, the file is not
                  recalled.

         -Quota=n
                  Specifies the maximum number of megabytes of data that
                  you can migrate and premigrate from your file system
                  to IBM Spectrum Protect storage. Specify a value from
                  0 to 999999999999999. The default is the number of
                  megabytes that are allocated for your file system. If
                  you set the quota to 0 for your file system, files do
                  not migrate to storage. If you set the quota to
                  999999999999999, the amount of data you can migrate
                  and premigrate is unlimited.

         -READEVEnttimeout=n
                  Specifies the maximum time of inactivity (in seconds)
                  before a streaming recall process times out. The
                  acceptable range is 0 - 999999999. A value of
                  999999999 means that a streaming recall process does
                  not time out. The default value is 600. This option
                  applies to streaming recall mode only.

         -REAdstartsrecall=No|Yes
                  Specifies whether a recall operation starts when an
                  application reads the stub file.

                  This option applies only if streaming recall mode is
                  set.

                  If the previewsize option is set for the stub file, a
                  recall operation starts only when an application reads
                  beyond the preview section of the stub file.

                  The default value is No.

                  Regardless of the value of the readstartsrecall
                  option, the file is recalled when either of the
                  following conditions are true:

                  *  The recall daemon determines that the stub file
                     does not contain all of the data that is required
                     by a read operation.

                  *  An operation modifies the file.

         -SErver=server_name
                  Overrides the default migration server for this file
                  system. Specify the server to contact for space
                  management services. Define the server in a stanza in
                  your dsm.sys file. If you do not specify a server
                  name, the default migration server that you defined is
                  used. Use a dash (-) to set the server to the default
                  migration server.

         -STREAMSeq=n
                  Specifies the number of megabytes that are buffered
                  before the recall daemon flushes the data to disk. The
                  acceptable range is 0 - 1024. The default value of 0
                  means that buffering is disabled. This option applies
                  only to streaming recall mode.

         -STUBSize=n
                  Specifies the size of stub files that remain on the
                  file system when files are migrated to storage.

                  For the space management client on GPFS file systems,
                  you can specify 0 or a multiple of the file system
                  block size. The default value is 0.

                  For all file system types, the maximum value for a
                  stub file size is 1 GB.

If HSM is globally deactivated on a node (dsmmigfs globaldeactivate), it
is reset to active state, if one of the following commands are
performed:

   dsmmigfs add
   dsmmigfs remove
   dsmmigfs update
   dsmmigfs takeover
   dsmmigfs rollback
   dsmmigfs globalreactivate

Examples

Commands are provided for the example tasks.

   
  Task                                Command                          
 -----------------------------------+--------------------------------- 
  Add space management to the         dsmmigfs Add -MAXFiles=0         
  /hsmmanagedfs1 file system. Set     /hsmmanagedfs1                   
  the space to the maximum number                                      
  of blocks in the file system.                                        
 -----------------------------------+--------------------------------- 
  Update the space management         dsmmigfs update                  
  settings for the /hsmmanagedfs2     -MAXFiles=10000000               
  file system. Set the space          /hsmmanagedfs2                   
  (number of blocks) to the                                            
  specified number.                                                    
 -----------------------------------+--------------------------------- 
  Add space management to the /home   dsmmigfs Add -HT=80 -L=70        
  file system. Set the high           -STUBS=256k /home                
  threshold to 80 percent. Set the                                     
  low threshold to 70 percent. Set                                     
  the size of stub files to 256K                                       
  (KB).                                                                
 -----------------------------------+--------------------------------- 
  Add space management to more than   dsmmigfs Add /home /test1        
  one file system and accept the      /proj*                           
  default values for all space                                         
  management settings.                                                 
 -----------------------------------+--------------------------------- 
  Update the space management         dsmmigfs Update -HT=80 -L=70     
  settings for the /home file         -STUBS=1m /home                  
  system as follows:                                                   
   * Change the high threshold to                                      
  80 percent.                                                          
   * Change the low threshold to 70                                    
  percent.                                                             
   * Set the size of stub files to                                     
  1 megabyte.                                                          
 -----------------------------------+--------------------------------- 
  Specify the minimum size of files   dsmmigfs Update -minp=100        
  in the /home/user1 file system      /home/user1                      
  that are recalled with partial                                       
  file recall.                                                         
 -----------------------------------+--------------------------------- 
  Specify that the minimum size for   dsmmigfs Update -minm=1048576    
  a file that can be migrated from    /home/user2                      
  the /home/user2 file system is 1                                     
  megabyte.                                                            
 -----------------------------------+--------------------------------- 
  Add space management to the /myfs   dsmmigfs add -maxfiles=1000000   
  file system. Set the high           -lt=50 -ht=80 -pm=10 /myfs       
  threshold to 80 percent. Set the                                     
  low threshold to 50 percent. Set                                     
  the space (number of blocks) to                                      
  the specified number.                                                
 -----------------------------------+--------------------------------- 
  When a file is migrated from the    dsmmigfs update -stubs=32768     
  /myfs file system, create a stub    -preview=16384                   
  file with the following             -minstreamfilesize=2             
  specifications:                     readstartsrecall=yes /myfs       
   * The stub size is 32,768 bytes.                                    
   * The stub preview size is                                          
  16,384 bytes.                                                        
   * If an application reads more                                      
  than the preview size of the stub                                    
  file, and the file is greater                                        
  than 2 MB, recall the file.                                          



2.13 dsmmigfs addmultiserver, querymultiserver, and removemultiserver


Use the dsmmigfs command with the addmultiserver, querymultiserver, or
removemultiserver parameter to manage space in an environment with
multiple IBM Spectrum Protect servers.



Syntax

>>-DSMMIGFS--+-ADDMultiserver----+--filesystemspec-------------->
             +-QUERYMultiserver--+                   
             '-REMOVEMultiserver-'                   

>--+---------+-------------------------------------------------><
   '-options-'   



Parameters

ADDMultiserver
         Adds one IBM Spectrum Protect server to the list of servers
         that can manage the file system.

QUERYMultiserver
         Queries the status of the multiple-server environment. The
         command prints all IBM Spectrum Protect servers that can manage
         the specified file system. For each server, the output displays
         the number of files, number of bytes, and migration throughput.

REMOVEMultiserver
         Removes an existing IBM Spectrum Protect server from the list
         of servers that can manage the specified file system. That IBM
         Spectrum Protect server is no longer a target for migration and
         backup. The current migration and backup processes are not
         affected. Removal does not affect the recall or restore of
         files that are migrated or backed up to the IBM Spectrum
         Protect server.

         After you remove the IBM Spectrum Protect server from the list
         of servers, and before physically removing the server, run the
         dsmRemoveServer.pl script. The dsmRemoveServer.pl script
         recalls all files from the IBM Spectrum Protect server to the
         local file systems. After you run the dsmRemoveServer.pl
         script, you can migrate and back up files to another IBM
         Spectrum Protect server.

filesystemspec
         The file system name. Specify only one file system.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

         -SErver=server_name
                  Specify the target server for the task. This option is
                  valid only in a multiple-server environment, and must
                  be used only with the two-way, orphan-check
                  reconciliation mode.

                  If a file is coupled with a server, the value of this
                  option must be that coupled server. If you specify
                  another IBM Spectrum Protect server, the task fails.


2.14 dsmmigfs control


Use the dsmmigfs command with the control parameter to dynamically
change space management client options applied from running space
management daemons.

You must have root user authority to use this command.

Syntax

>>-DSMMIGFS----Control----+---------+--------------------------><
                          '-options-'   



Parameters

Control
         Send a control statement to a space management client daemon to
         change the behavior of the daemon.

options
         Use the option settings that are provided for this command to
         change client option settings applied from space management
         client daemons.

         The control command applies for the space management client
         daemons watch daemon (dsmwatchd) and recall daemon
         (dsmrecalld).

-Type=enabletrace|disabletrace
         The argument Type is mandatory. Specify whether the space
         management client tracing function should be enabled or
         disabled for a specified space management client daemon.

-PROcess=WD|RMD|RDD
         The parameter PROcess is mandatory. Specify the space
         management client daemon process you want to update with new
         space management client option settings.

         Specify the option WD to update the space management watch
         daemon (dsmwatchd).

         Specify the option RMD to update the space management master
         recall daemon (dsmrecalld with PPID=1).

         Specify the option RDD to update the space management
         distributor recall daemon (dsmrecalld with PPID=PID from master
         recall daemon).

-Options=name:value[::name:value]
         The parameter Options is mandatory if the parameter -Type is
         set to enabletrace.

         Specify the option TRACEFILE in combination with option value
         trace file name. Specify the option TRACEFLAGS in combination
         with the option value trace flags.

         The trace file name must specify a file name in a directory
         that can be accessed from the space management client daemon
         process.

         The remote node is not properly configured on the server.

         Ensure that the remote node is properly configured and
         connected to the server by using TLS. This validates the remote
         node configuration and ensures that the information related to
         the remote node is sent to the server.

         The trace flags must be one space management client trace flag
         or a list of space management client trace flags separated with
         blanks and enclosed with double quotes.

         Note: In the current implementation of the control statement
         only trace options can be controlled for the specified space
         management client daemons.

Examples

Commands are provided for the example tasks.

   
  Task                                Command                          
 -----------------------------------+--------------------------------- 
  Enable tracing for the space        dsmmigfs control                 
  management client daemon watch      -type=enabletrace -process=WD    
  daemon with the                     -options=tracefile:/tmp/dsmwatc  
  /tmp/dsmwatchd.trc trace file and   hd.trc::traceflags:"SM           
  the SM SMVERBOSE SERVICE trace      SMVERBOSE SERVICE"               
  options.                                                             
 -----------------------------------+--------------------------------- 
  Disable tracing for the space       dsmmigfs control                 
  management client daemon recall     -type=disabletrace -process=RMD  
  master daemon.                                                       



2.15 dsmmigfs deactivate, reactivate, and remove


Use the dsmmigfs command with the deactivate, reactivate, or remove
parameter to deactivate, reactivate, or remove space management from a
file system.

You must have root user authority to use this command.

Syntax

                             .--------------------.   
                             V                    |   
>>-DSMMIGFS--+-Deactivate-+------filesystemspec---+------------->
             +-REActivate-+                           
             '-REMove-----'                           

>--+---------+-------------------------------------------------><
   '-options-'   



Parameters

Deactivate
         Deactivates space management for a file system. The space
         management client cannot migrate or recall files, and cannot
         reconcile the file system. However, you can update space
         management settings for your file system, and access resident
         and premigrated files.

REActivate
         Reactivates space management for a file system.

REMove
         Removes space management from a file system. If you deactivated
         space management for your file system, reactivate it before you
         remove space management. If any orphaned stub files are
         located, the command fails. To remove space management, resolve
         all orphaned stub files, and issue the dsmmigfs command again.
         If the 3.23 hsmoptimizedrecallonly option is set to YES, recall
         all files in an optimized way, before you remove space
         management from a file system. Alternatively, set the 3.23
         hsmoptimizedrecallonly option to NO, and restart space
         management daemons before attempting the command again.

filesystemspec
         The file system name. You can specify more than one file system
         name, and you can use wildcard characters within a file system
         name. If you specify more than one file system name, separate
         each name with one or more blank spaces.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

   
  Task                                      Command                    
 -----------------------------------------+--------------------------- 
  Deactivate space management for the       dsmmigfs Deactivate /home  
  /home file system.                                                   
 -----------------------------------------+--------------------------- 
  Reactivate space management for the       dsmmigfs REActivate /home  
  /home file system.                                                   
 -----------------------------------------+--------------------------- 
  Remove space management from the /home    dsmmigfs REMove /home      
  file system.                                                         



2.16 dsmmigfs globaldeactivate and globalreactivate


Use the dsmmigfs command with the globaldeactivate or globalreactivate
parameter to either deactivate or reactivate space management for a
space-managed client node.

You must have root user authority to use this command.

Syntax

>>-DSMMIGFS--+-GLOBALDeactivate-+--+---------+-----------------><
             '-GLOBALReactivate-'  '-options-'   



Parameters

GLOBALDeactivate
         Deactivates space management for all file systems on your
         client node. The space management client cannot migration or
         recall any files and cannot reconcile any file system. However,
         you can update space management settings for file systems, add
         space management to other file systems, or access resident and
         premigrated files.

GLOBALReactivate
         Reactivates space management for your client node. All file
         systems to which you added space management return to their
         previous state, including that which you added while space
         management was globally deactivated.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

   
  Task                                    Command                      
 ---------------------------------------+----------------------------- 
  Globally deactivate space management    dsmmigfs GLOBALDeactivate    
  for your client node.                                                
 ---------------------------------------+----------------------------- 
  Globally reactivate space management    dsmmigfs GLOBALReactivate    
  for your client node.                                                



2.17 dsmmigfs help


Use the dsmmigfs command with the help parameter to display the dsmmigfs
command syntax and options.



Syntax

>>-DSMMIGFS--Help--+---------+---------------------------------><
                   '-options-'   



Parameters

Help
         Displays the syntax of the dsmmigfs command including command
         parameters, options, and valid ranges of options values.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

   
  Task                                    Command                      
 ---------------------------------------+----------------------------- 
  Display the syntax of the dsmmigfs      dsmmigfs h                   
  command.                                                             



2.18 dsmmigfs query


Use the dsmmigfs command with the query parameter to display the current
space management settings for a file system.



Syntax

>>-DSMMIGFS--Query--+---------+--+--------------------+--------><
                    '-options-'  | .----------------. |   
                                 | V                | |   
                                 '---filesystemspec-+-'   



Parameters

Query
         Display the current space management settings for the named
         file system.

options
         -Detail
                  Display detailed HSM settings for the file system.
                  Some settings are displayed only when queried with the
                  detail option:

                  *  The maximum number of migration candidates that are
                     identified by the scout daemon

                  *  The minimum partial file recall size

                  *  The minimum streaming recall size

                  *  The minimum size (in bytes) that qualifies a file
                     for migration

                  *  The local status for the distributed recall
                     environment

                  *  The status for the failover environment

                  For GPFS file systems only:
                           The dsmmigfs query command without the detail
                           option displays only locally managed file
                           systems. Use the detail option to display
                           information for all space-managed file
                           systems within the IBM Spectrum Scale
                           cluster.

                           When you specify the detail option, the HSM
                           client also displays the node name for each
                           node ID.

         -Failover
                  Display a status overview of the failover environment
                  of all HSM managed cluster nodes. Valid only on GPFS
                  file systems. The output displays the status for the
                  node name, and node ID. The following status can be
                  displayed:

                  ENABLED
                           The node can take over space-managed file
                           systems when another HSM node fails. If the
                           node fails, control of the space-managed file
                           systems fails over to other HSM nodes.

                  ENABLED_TAKEOVER
                           The node can take over space-managed file
                           systems when another HSM node fails. If the
                           node fails, control of the space-managed file
                           systems does not fail over to other HSM
                           nodes.

                  ENABLED_HANDOVER
                           If the node fails, control of the
                           space-managed file systems fails over to
                           other HSM nodes. The node does not take over
                           space-managed file systems when another HSM
                           node fails.

                  DISABLED
                           The HSM node does not take control of another
                           HSM node's space-managed file systems. If the
                           node fails, control of the space-managed file
                           systems does not fail over to other HSM
                           nodes.



                  To enable failover of HSM management of GPFS file
                  systems on source nodes within a cluster environment,
                  issue the dsmmigfs enablefailover command on each
                  source node.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

         -Node=node_value -parsable
                  Display the IBM Spectrum Scale status of cluster nodes
                  that are managed by the HSM client. Valid only on GPFS
                  file systems. The minimum abbreviation of the option
                  is one character (-n=node_value). The output displays
                  the following information for each node:

                  *  IBM Spectrum Scale node name

                  *  IBM Spectrum Scale node ID

                  *  IBM Spectrum Scale status. The IBM Spectrum Scale
                     status can be arbitrating, active, down, or
                     unknown. The status is displayed when you specify
                     the detail option.

                  *  Recall daemon session ID

                  *  Mount disposition

                  *  Ping recall daemon

                  *  Watch daemon session ID

                  *  HSM status. The HSM status can be active or down.



                  Specify node_value by using one of three formats:

                  Specify node_value as a node name
                           Example: -node=system1

                  Specify node_value as a file that contains a list of
                  node names
                           Example:
                           -node=/usr/tivoli/tsm/data/nodes.list

                  Specify node_value by using a key word that defines a
                  class of nodes
                           Specify one of the following node classes:

                           all
                                    All nodes in the IBM Spectrum Scale
                                    cluster.

                           clientnodes
                                    All nodes that do not participate in
                                    file system administration
                                    activities.

                           managernodes
                                    All nodes in the pool of nodes from
                                    which file system managers and token
                                    managers are selected.

                           nonquorumnodes
                                    All non-quorum nodes in the IBM
                                    Spectrum Scale cluster.

                           nsdnodes
                                    All NSD server nodes in the IBM
                                    Spectrum Scale cluster.

                           quorumnodes
                                    All quorum nodes in the IBM Spectrum
                                    Scale cluster.
                           Example: -node=quorumnodes

                  When you specify the node option, you can specify the
                  parsable option. The parsable option is optional. The
                  parsable option displays output in a format that can
                  be easily parsed. The minimum abbreviation of the
                  option is four characters (-pars). The parsable format
                  displays the following attributes in order:

                     Command name
                     Query type
                     IBM Spectrum Scale node name
                     IBM Spectrum Scale node ID
                     IBM Spectrum Scale status
                     HSM status
                     Recall master session ID
                     Mount disposition
                     Recall daemon readiness
                     Watch daemon session ID

                  Each attribute value ends with a colon.

                  The following output is an example of the format when
                  you specify the parsable option:

filesystemspec
         The file system name that displays current space management
         settings. The default is all space managed file systems.

Examples

   
  Task                                    Command                      
 ---------------------------------------+----------------------------- 
  Display the space management settings   dsmmigfs query /migfs2       
  for the /migfs2 file system.                                         
 ---------------------------------------+----------------------------- 
  Display the space management entries    dsmmigfs query               
  that are made in the log file           -L=/tmp/migfslog /migfs2     
  /tmp/migfslog.                                                       



2.19 dsmmigfs rollback


Use the dsmmigfs command with the rollback parameter to transfer the
space management of file systems to the preferred node if the node is
different from the current owner node.

This command is valid only on GPFS file systems.

You must have root user authority to use this command.

Syntax

>>-DSMMIGFS--ROLLback--+---------+-----------------------------><
                       '-options-'   



Parameters

ROLLback
         Transfers the HSM management of file systems to the preferred
         node if the node is different from the current owner node.
         Enter this command on the preferred node.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

   
  Task                                    Command                      
 ---------------------------------------+----------------------------- 
  Transfer to the preferred node.         dsmmigfs rollback            



2.20 dsmmigfs enablefailover, and disablefailover


Use the dsmmigfs command with the enablefailover or disablefailover
parameter to manage recovery from partial system failure.

This command is valid only on GPFS file systems.

You must have root user authority to use this command.

One space management client can take over from an HSM client that is
involved in a partial system failure if the following conditions are
true:

*  The failing space management client node has failover enabled.

*  There are one or more additional space management client nodes within
   the same IBM Spectrum Scale cluster with failover enabled.

*  The space-managed file system is mounted on at least one of these
   nodes.

*  A synchronous time exists on the failing nodes and the client nodes.

*  The peer node is online

Syntax

>>-DSMMIGFS--+-ENABLEFailover--+--+---------+------------------><
             '-DISABLEFailover-'  '-options-'   



Parameters

ENABLEFailover
         Activates the node for failover operations within the IBM
         Spectrum Scale cluster.

DISABLEFailover
         Deactivates failover operations on the node.

options
         -MODE=value
                  Specifies a failover mode. The mode option is valid
                  only with the enablefailover parameter. You can
                  specify the following values for the mode option:

                  TAKEOVER
                           The node can take over space-managed file
                           systems when another HSM node fails. If the
                           node fails, control of the space-managed file
                           systems does not fail over to other HSM
                           nodes.

                  HANDOVER
                           If the node fails, control of the
                           space-managed file systems fails over to
                           other HSM nodes. The node does not take over
                           space-managed file systems when another HSM
                           node fails.

                  ENABLED
                           The node can take over space-managed file
                           systems when another HSM node fails. If the
                           node fails, control of the space-managed file
                           systems fails over to other HSM nodes.

                  The default is ENABLED

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

Commands are provided for the example tasks.

   
  Task                                      Command                    
 -----------------------------------------+--------------------------- 
  Enable failover operations on the space   dsmmigfs enablef           
  management client node. If the node       -mode=HANDOVER             
  fails, control of the space-managed                                  
  file systems fails over to other HSM                                 
  nodes. The node does not take over                                   
  space-managed file systems when another                              
  HSM node fails.                                                      
 -----------------------------------------+--------------------------- 
  Deactivate failover operations on the     dsmmigfs disableFailover   
  space management client node.                                        



2.21 dsmmigfs stop, start, and restart


use the dsmmigfs command with the stop, start, or restart parameter to
control space management daemons.

Valid only on GPFS file systems.

You must have root user authority to use this command.

Use the dsmmigfs command with the stop, start, or restart parameter to
control daemons:

*  Start all daemons

*  Stop all daemons, dsmrecall and dsmmigrate processes except dsmwatchd

*  Restart all daemons, stop dsmrecall and dsmmigrate except dsmwatchd.

Note: Be aware that the daemons will be started with the same
environment as the dsmwatchd daemon, which means that options files
dsm.opt and dsm.sys in the default installation path
/usr/tivoli/tsm/client/ba/bin will be used.

Syntax

>>-DSMMIGFS--+-START---+--+---------+--------------------------><
             +-STOP----+  '-options-'   
             '-RESTART-'                



Parameters

START
         Starts all HSM daemons on the local client node. The dsmwatchd
         daemon is not affected.

STOP
         Stops all HSM daemons. The dsmrecall and dsmmigrate processes
         are stopped. The dsmwatchd daemon is not affected.

RESTART
         Restarts all HSM daemons. The dsmrecall and dsmmigrate
         processes are started. The dsmwatchd daemon is not affected.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

   
  Task                                    Command                      
 ---------------------------------------+----------------------------- 
  Start all daemons                       dsmmigfs START               
 ---------------------------------------+----------------------------- 
  Stop all daemons                        dsmmigfs STOP                
 ---------------------------------------+----------------------------- 
  Restart all daemons. For example, let   dsmmigfs RESTART             
  them update the configuration set in                                 
  your dsm.opt and dsm.sys options                                     
  files.                                                               



2.22 dsmmigfs takeover


Use the dsmmigfs command with the takeover parameter to transfer the HSM
management of a file system to another space management client node
within the same local IBM Spectrum Scale node set.

Valid only on GPFS file systems.

You must have root user authority to use this command.

Syntax

>>-DSMMIGFS--TAKEover--filespec--+---------+-------------------><
                                 '-options-'   



Parameters

TAKEover
         The dsmmigfs command transfers the HSM management of the
         specified file system to the space management client node on
         which you invoke this command. The transfer must be initiated
         on a node within the same local IBM Spectrum Scale node set.

filespec
         The name of the file system you want to takeover.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

Examples

   
  Task                                    Command                      
 ---------------------------------------+----------------------------- 
  Transfer the HSM management of the      dsmmigfs takeover            
  current directory to the space          /home/filesystem             
  management client node within the                                    
  same local IBM Spectrum Scale node                                   
  set.                                                                 



2.23 dsmmighelp


The dsmmighelp command displays online help topics from which you can
select general help for commands or message information.



Syntax

>>-DSMMIGHELP--+---------+-------------------------------------><
               '-options-'   



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

Examples

   
  Task                                               Command           
 --------------------------------------------------+------------------ 
  Display online help for HSM commands.              dsmmighelp        



2.24 dsmmigquery


The dsmmigquery command displays information about migrated files,
candidates, and management classes.

You must have root user authority to use this command.

The dsmmigquery command displays the following information for one or
more file systems:

*  Migration candidates list
*  Ordered recall list for migrated files
*  Available management classes
*  Current(R) client and server options
*  List of all files in the file system

Output from this command is directed to stdout. Use redirection
characters and a file name at the end of the command to redirect the
output to a file.

Syntax

>>-DSMMIGQUERY--+----------------+--+---------+----------------><
                '-filesystemspec-'  '-options-'   



Parameters

options
         -Detail
                  Use with the mgmtclass option to display information
                  about each available management class. If you do not
                  use this option, the HSM client displays the
                  management class name and a brief description only.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -Mgmtclass
                  Displays information about each management class that
                  you can assign to your files.

         -Options
                  Displays the current settings for your client and
                  server options. This option is the default.

         -SErver=server_name
                  Specify the target server for the task. This option is
                  valid only in a multiple-server environment. In a
                  multiple-server environment you must specify the
                  server option.

                  This option is valid with the sortedall and
                  sortedmigrated options.

         -SORTEDAll
                  Lists all files in the file system in this order:
                  resident files, premigrated files, migrated files.
                  Sorts migrated files in the most efficient order for
                  recall.

         -SORTEDMigrated
                  Lists all files that you migrated from the file system
                  to IBM Spectrum Protect storage in the most efficient
                  order for recall.

filesystemspec
         The file system for which you want to display information. The
         default is the current file system. You can specify more than
         one file system name, and you can use wildcard characters
         within a file system name. If you specify more than one file
         system name, separate each name with one or more blank spaces.

Examples

   
  Task                                     Command                     
 ----------------------------------------+---------------------------- 
  Display the current settings for the     dsmmigquery                 
  client and server options.                                           
 ----------------------------------------+---------------------------- 
  Display information about management     dsmmigquery -Mgmtclass      
  classes that you can assign to files     -Detail                     
  on your client node.                                                 



2.24.1 HSM and backup-archive client dsmmigquery command shared options


The dsmmigquery -o command displays both HSM options and many options
that are shared between the space management client and the
backup-archive client.

The following is a list of the options that are shared between the space
management client and the backup-archive client.

*  asnodename
*  commmethod
*  compression
*  defaultserver
*  detail
*  diskbuffsize
*  enablelanfree
*  errorlogmax
*  errorlogname
*  errorlogretention
*  exclude
*  exclude.compression
*  inclexcl
*  include
*  include.compression
*  lanfreecommmethod
*  lanfreetcpport
*  lanfreeshmport
*  makesparsefile
*  nodename
*  passwordaccess
*  passworddir
*  servername
*  shmport
*  skipacl
*  tcpbuffsize
*  tcpnodelay
*  tcpport
*  tcpserveraddress
*  tcpwindowsize


2.25 dsmmigrate


The dsmmigrate command selects specific files from the local file system
and migrates them to the IBM Spectrum Protect server.

Tip: On large file systems, selective migration can take a long time.
Migration can be quicker if you premigrate files before you migrate
them. The quickest way to create free space requires two steps:

1. Prepare for migration by premigrating files.

2. When you need to create free space quickly, use the stubpremigrated
   option to migrate only premigrated files.

If the file exists in a file system with a different server stanza than
the last processed file, a new session starts for each migrated file.
This action can happen as a result of links from one file system to
another.

Note:

1. You are prompted either to wait for the medium to mount or to skip
   the file when the following two conditions are met:

   *  The tapeprompt option is set to YES in the dsm.opt file.

   *  The destination for the migrated file is a storage pool that
      consists of removable media (such as tape)

2. The space management client does not migrate contents of symbolic
   links. Symbolic links are not followed during recursive selective
   migration.

The first file migrates even if the file size exceeds the quota that you
specified for the file system. When migration occurs, the ddf command
displays zero migrated and premigrated bytes for the file system. If the
total number of bytes exceeds the quota after the file migrates, the
next file is not migrated.

Syntax

                            .------------------------------.   
                            V                              |   
>>-DSMMIGRATE--+---------+----+-filespec-----------------+-+---><
               '-options-'    '- -FIlelist--=--file_path-'     



Parameters

options
         -Detail
                  Displays the size and file name for each file that you
                  migrate.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

         -Premigrate
                  A copy of the file is sent to IBM Spectrum Protect
                  storage, and the file remains on the local file
                  system. The file state changes to premigrated. You
                  cannot use the premigrate option and the
                  stubpremigrated option at the same time.

         -PREViewsize=n
                  Specifies the preview size of the stub file. Valid
                  values are 0 - 1,073,741,824, and must not be greater
                  than the stub size.

                  When the attributes are set and the preview size is
                  defined, a recall operation begins only when an
                  application reads the stub file beyond the preview
                  section of the stub file. If an operation reads only
                  the preview section of the stub file, the file is not
                  recalled.

         -REAdstartsrecall=No|Yes
                  Specifies whether a recall operation starts when an
                  application reads the stub file.

                  This option applies only if streaming recall mode is
                  set.

                  If the previewsize option is set for the stub file, a
                  recall operation starts only when an application reads
                  beyond the preview section of the stub file.

                  The default value is No.

                  Regardless of the value of the readstartsrecall
                  option, the file is recalled when either of the
                  following conditions are true:

                  *  The recall daemon determines that the stub file
                     does not contain all of the data that is required
                     by a read operation.

                  *  An operation modifies the file.

         -Recursive
                  Migrates files in any subdirectory of the specified
                  directory that matches the file specification. If you
                  do not use this option, only those files from the
                  directories that you specify are migrated.

                  The space management client does not migrate contents
                  of symbolic links. Symbolic links are not followed
                  during recursive selective migration.

         -SErver=server_name
                  Specify the target server for the task. This option is
                  valid only in a multiple-server environment, and must
                  be used only with the two-way, orphan-check
                  reconciliation mode.

                  If a file is coupled with any IBM Spectrum Protect
                  server, you must specify that server. If a file is not
                  coupled with any server, you can specify any IBM
                  Spectrum Protect server that was added to the
                  multiple-server environment.

         -STUBSize=n
                  Specifies the size of stub files that remain on the
                  file systems when files are migrated to storage.

                  For the space management client on GPFS file systems,
                  you can specify 0 or a multiple of the file system
                  block size. The default value is 0.

                  For all file system types, the maximum value for a
                  stub file size is 1 GB.

         -STUBPremigrated
                  Only files that are in premigrated state are migrated.
                  The migration process yields free space on the file
                  system quickly. File copies exist in IBM Spectrum
                  Protect storage. The migration process only replaces
                  the local files with stub files.

filespec
         The path and file name of the files that you want to migrate.
         This parameter is required. You can use wildcard characters to
         specify a group of files or all files in a directory. You can
         enter more than one file specification in one command. If you
         enter more than one file specification, separate each
         specification with one or more blank spaces.

-FIlelist=file_path
         Specifies the path of a file that contains a list of files to
         be processed by this command.

         The entries in the list file must adhere to the following
         rules:

         *  Each entry is a fully qualified path to a file or a relative
            path to a file.

         *  No entry is a directory object.

         *  Each entry is on a separate line.

         The space management client ignores any entry that does not
         adhere to these rules.

         The following rules apply to a file list for the space
         management client. These rules differ from the rules for
         backup-archive client file lists.

         *  An entry can contain unprintable characters, but cannot
            contain a carriage return.

         *  Wildcard characters are allowed.

         *  A file path that contains blank spaces must be enclosed in
            quotation marks.

         *  An entry that begins with a quotation mark and ends with a
            quotation mark is tolerated. The space management client
            assumes that the quotation marks are not needed and omits
            them when the space management client processes the entry.
            If beginning and ending quotation marks are required to
            identify the file, add double quotation marks before the
            beginning and after the end of the entry.

         The following example shows a list of files within a list file:

           /home/dir/file1
           "/fs1/dir2/file3"
           "/fs2/my files/file4"
           ../tivoli/'file1'
           "'fs3'/dir3/'file.txt'"
           fs4/dir/a"file".txt
           '/fs4/dir/file.txt'
           /fs5/dir/file*with?wildcards.txt

         If the list file name that you specify with the filelist option
         does not exist, the command fails.

Examples

   
  Task                            Command                              
 -------------------------------+------------------------------------- 
  Migrate all files in a          dsmmigrate -Recursive -Detail        
  directory that is named         /migfs2/test/dir1                    
  /migfs2/test/dir1 and in all                                         
  of its subdirectories.                                               
  Display the information.                                             
 -------------------------------+------------------------------------- 
  Migrate a file that is named    dsmmigrate -Detail -L=/tmp/miglog    
  tf04 from the current           tf04                                 
  directory and display the                                            
  information. Log the results                                         
  in the file /tmp/miglog .                                            
 -------------------------------+------------------------------------- 
  Migrate all files in a file     dsmmigrate -logname=/tmp/miglog      
  list that is named              -filelist=/tmp/filelist              
  /tmp/filelist . Log the         -stubsize=4096 -previewsize=2048     
  results in the file             -readstartsrecall=yes                
  /tmp/miglog . Set the stub                                           
  size to 4096 bytes and the                                           
  preview size to 2048 bytes.                                          
  Restriction: When a file is                                          
  recalled, the preview size                                           
  affects recall processing                                            
  only if streaming recall mode                                        
  is set and                                                           
  readstartsrecall=yes . You                                           
  can set streaming recall mode                                        
  with the minstreamfilesize                                           
  option on the dsmmigfs                                               
  command or with the                                                  
  recallmode option on the                                             
  dsmattr command.                                                     
 -------------------------------+------------------------------------- 
  Use a shell application to      find /hsmfilesystem -user ibm        
  build a list of files that      -print > /tmp/filelist dsmmigrate    
  are owned by user ibm, and      -filelist=/tmp/filelist              
  then migrate the files.                                              
 -------------------------------+------------------------------------- 
  Premigrate the file             dsmmigrate -p /migfs2/test/file1     
  /migfs2/test/file1 , but do                                          
  not replace the local file                                           
  with a stub.                                                         
 -------------------------------+------------------------------------- 
  Migrate all premigrated files   dsmmigrate -R -ST /migfs2/test/dir1  
  in directory                                                         
  /migfs2/test/dir1/ and in all                                        
  of the subdirectories                                                



2.26 dsmmigundelete


The dsmmigundelete command re-creates deleted stub files for migrated
files, and creates stub files for premigrated files for which an
original file does not exist on your local file system. The file then
becomes a migrated file.

You must have root user authority to use this command.

When a stub file or an original copy of a premigrated file is deleted
from your local file system, the corresponding migrated or premigrated
file is marked for expiration when reconciliation runs again.

Note: The dsmmigundelete command does not support hard-linked files. If
you re-create a stub file for a hard-linked file, a stub file is not
re-created unless all of the hard-linked files are deleted from your
local file system. When one file in a set of hard-linked files is
migrated, all of the hard-linked files in the set become stub files.
When the dsmmigundelete command re-creates a stub file for a hard-linked
file, the stub file has the same name as the file that was originally
migrated. Stub files are not re-created for any other files that were
previously in the hard-linked set of files.

Note: When node replication is used on the IBM Spectrum Protect failover
server, you can restore files from the failover server. However,
restoring stub files from the failover server is not supported. Instead
of restoring the stub files, the resident files will be restored. In
such a case, when you reconfigure HSM to connect to a failover server,
the dsmmigundelete and dsmreconcile commands are not supported.

Syntax

>>-DSMMIGUNDELETE--+----------------+--+---------+-------------><
                   '-filesystemspec-'  '-options-'   



Parameters

options
         -Recover
                  Re-creates stub files that have been removed from your
                  file system. Use this option if you need better
                  performance during the recover process.

                  Important: This option re-creates all of the existing
                  stub files that overwrites all premigrated or recalled
                  files. Data is lost from the last migration up to when
                  this option is used! After the dsmmigundelete -recover
                  command is issued, there is no way you can check
                  whether the data of the local stub file is different
                  from the contents of the file in the IBM Spectrum
                  Protect server.

                  Use this option only if all or most of the files in
                  the file system are stub files and you need good
                  performance during stub file recreation.

                  For performance purposes, do not use this option with
                  the detail option.

                  Files that were never migrated are not re-created.

         -Detail
                  Displays detailed information about which stub file is
                  being re-created to the file system.

                  Do not use this option with the recover option.

         -Expiring
                  Re-creates a stub file for a migrated file if a
                  corresponding stub file does not exist on your local
                  file system, whether the migrated file was marked for
                  expiration or not. Or, it creates a stub file for a
                  premigrated file if a corresponding original file does
                  not exist on your local file system, whether the
                  premigrated file was marked for expiration or not.

                  Issue the dsmmigundelete command with the expiring
                  option if you ran reconciliation since the files were
                  deleted.

                  If you do not use the expiring option, the HSM client
                  re-creates a stub file for a migrated file if a
                  corresponding stub file does not exist on your local
                  file system and the migrated file was not marked for
                  expiration. Or, it creates a stub file for a
                  premigrated file if a corresponding original file does
                  not exist on your local file system, and the
                  premigrated file was not marked for expiration.

                  Enter the dsmmigundelete command without the expiring
                  option if you did not run reconciliation since the
                  files were deleted.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

         -FILELIST=file_path
                  Specifies the path of a file that contains a list of
                  files to be processed by this command. The format of a
                  file list entry is <extobjid> <file path>\n. To have
                  the required information in place for a file
                  list-based recreation of stub files, it is recommended
                  to collect this information regularly from the file
                  system. This information is collected by using the IBM
                  Spectrum Scale policy engine and storing it in
                  temporary files or alternatively use the script
                  dsmmigundelete.pl to query the information from the
                  IBM Spectrum Protect server.

         -SErver=server_name
                  Specify the target server for the task. This option is
                  valid only in a multiple-server environment, and must
                  be used only with the two-way, orphan-check
                  reconciliation mode.

                  If a file is coupled with a server, the value of this
                  option must be that coupled server. If you specify
                  another IBM Spectrum Protect server, the task fails.

filesystemspec
         The name of the file system for which you want to re-create
         deleted stub files and create stub files for premigrated files
         that were deleted from your local file system. The default is
         all file systems for which space management is active. You can
         specify more than one file system name. If you specify several
         file system names, separate each name with one or more blank
         spaces.

Examples

   
  Task                                       Command                   
 ------------------------------------------+-------------------------- 
  Re-create stub files that were             dsmmigundelete -expiring  
  accidentally deleted from the /home file   -Logname=/tmp/undeletelo  
  system. Re-create stub files regardless    g /home                   
  of the expiration status of the                                      
  migration copies (use the expiring                                   
  option). Reconciliation was run since                                
  the files were deleted. Results are                                  
  logged in the log file /tmp/undeletelog                              
  .                                                                    
 ------------------------------------------+-------------------------- 
  Re-create stub files for migrated files    dsmmigundelete            
  in the /home file system. Re-create stub   -L=/tmp/undeletelog       
  files only for those migration copies      /home                     
  that are not marked for expiration (do                               
  not use the expiring option).                                        
  Reconciliation was not run because the                               
  files were deleted. Entries are made in                              
  the log file /tmp/undeletelog .                                      
 ------------------------------------------+-------------------------- 
  Re-creates stub files for migrated files   dsmmigundelete -recover   
  that had been removed from the /trullofs   /trullofs                 
  file system.                                                         



2.27 dsmmonitord


The dsmmonitord command starts the HSM space monitor daemon if it has
stopped. If you issue this command and the space monitor daemon is
running, action is not taken.

You must have root user authority to use this command.

Syntax

>>-DSMMONITORD--+---------+------------------------------------><
                '-options-'   



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.


2.28 dsmq


The dsmq command displays following information about each recall
process that is queued for processing.

You must have root user authority to use this command.

The dsmq command displays the following information:

*  The recall ID
*  The hostname of the host that recalls the file
*  The start time for the recall process
*  The inode number for the recalled file
*  The name of the coupled IBM Spectrum Protect server
*  The name of the file system where the file is being recalled
*  The original name of the file at the time it was migrated

If you set the maxrecalldaemons option in your dsm.sys file lower than
the current number of requested recalls, some recall requests do not
display in the output for this command until recall daemons are
available to perform the requests. To remove a recall process from the
queue, use the dsmrm command.

Note: If the IBM Spectrum Protect server is busy, the original name of
the file might display as UNKNOWN. If the connection between the space
management client and the IBM Spectrum Protect server is slow, the
original name of the file might display as UNKNOWN. Issue the dsmq
command again to display the file name.

If the recall daemon process ID (DPID) is zero, the recall is complete.
You cannot remove the recall process from the queue.

The dsmq command does not display information about recalls triggered by
the optimized tape recall processing.



Syntax

>>-DSMQ--+---------+-------------------------------------------><
         '-options-'   



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

Examples

   
  Task                                                Command          
 ---------------------------------------------------+----------------- 
  Display the status of recall processes.             dsmq             



2.29 dsmrecall


The dsmrecall command selectively recalls migrated files or parts of
migrated files to the local file system. Space management must be
active.

Note: On large file systems, selective recall can take a long time. If
the 3.23 hsmoptimizedrecallonly option is set to YES on the file system
owner node, all non-optimized recalls are blocked.

If the file resides in a file system whose server stanza is different
from the stanza of the last processed file, a new session is started for
each recalled file. This process can happen as a result of links from
one file system to another.

To display a list of all migrated files, use the dsmmigquery command. To
display information about a list of migrated files from a particular
file system or directory, use the dsmls command.

Syntax

>>-DSMRECALL--+---------+--------------------------------------->
              '-options-'   

       .----------.                                          
       V          |                                          
>----+---filespec-+------------------------------------+-------><
     '--FILEList--=--list_file--+------------------+-'     
                                  '-file_system_name-'       



Parameters

options
         -Detail
                  Display the size, path, and file name for each file
                  that you recall.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -OFFset=n
                  Specify the offset from the beginning of the file of
                  the required data range for partial recall (in bytes,
                  kilobytes, megabytes, or gigabytes). Multipliers (k,
                  m, g, K, M, or G) can be used. The range of acceptable
                  values is 0 - 2147483647. There is no default value.

                  Valid only on GPFS file systems.

                  Remember: Use this option only with the size option
                  and when a file system is specified. The recursive,
                  detail, and filelist options are not valid with the
                  offset option.

                  Examples are: -offset=10 (bytes), -offset=23k
                  (kilobytes), -off=5M (megabytes), -off=2G (gigabytes).



         -PREView
                  Generate list files that are optimized for tape
                  recalls but do not recall the files. You must also
                  specify filelist and a file system. The preview option
                  is not valid when filelist specifies a collection
                  file.

         -Logname=file_path
                  Specifies the path and file name of the log file to be
                  used by this command. The kinds of events that are
                  logged to the file are specified with the
                  hsmlogeventflags option. Error events are not logged
                  to the file.

         -Recursive
                  Recall files that match the file specification in a
                  directory and its subdirectories. If you do not use
                  this option, files are recalled only for those
                  directories that you specify.

         -RESident
                  When files are recalled, change the state to resident.
                  If you do not use the resident option, the recalled
                  files are in the premigrated state.

                  Remember: During the next reconciliation of the file
                  system, files in resident state are marked for
                  expiration on the IBM Spectrum Protect server.

         -SIZE=n
                  Specify the size of the required data range for
                  partial recall (in bytes, kilobytes, megabytes, or
                  gigabytes). Multipliers (k, m, g, K, M, or G) can be
                  used. The range of acceptable values is 0 -
                  4294967295. There is no default value.

                  Valid only on GPFS file systems.

                  Remember:

                  *  Use this option only with the offset and the
                     filespec options. The recursive, detail, and
                     filelist options are not valid with the size
                     option.

                  *  The actual size value will round up to a multiple
                     of file system block size. For example, if the file
                     system block size is 4M and the specified size
                     value is 10M, the actual size recalled is 12M.

                  Examples are: -size=10 (bytes), -size=23k (kilobytes),
                  -size=5M (megabytes), -size=2G (gigabytes).



         -SErver=server_name
                  Specify the target server for the task. This option is
                  valid only in a multiple-server environment. If the
                  file system is managed by multiple servers and you do
                  not specify server, the task is attempted with the
                  default migration server.

                  If a file is coupled with a server, the value of
                  server must be that coupled server. If you specify
                  another IBM Spectrum Protect server, the task fails
                  with a warning message.

filespec
         Specify the path and file name of the files to recall. This
         parameter is required. You can use wildcard characters to
         specify a group of files or all files in a directory, or more
         than one file specification in one command. When you use
         wildcard characters in a file specification, the space
         management client recalls all files that match the
         specification. If a file matches the specification but it is
         not migrated, an error message displays. If you enter more than
         one file specification, separate each specification with at
         least one blank space.

-FILEList=list_file
         Process the files that are listed in list_file.

         The entries in the list file must adhere to the following
         rules:

         *  Each entry is a fully qualified path to a file or a relative
            path to a file.

         *  No entry is a directory object.

         *  Each entry is on a separate line.

         The space management client ignores any entry that does not
         adhere to these rules.

         The following example shows a list of files within a list file:

           /home/dir/file1
           "/fs1/dir2/file3"
           "/fs2/my files/file4"
           ../tivoli/'file1'
           "'fs3'/dir3/'file.txt'"
           fs4/dir/a"file".txt
           '/fs4/dir/file.txt'
           /fs5/dir/file*with?wildcards.txt

         If the list file name that you specify with the filelist option
         does not exist, the command fails.

         You can specify a collection file generated by dsmrecall or a
         list file generated by another application. You can specify
         only one list file or collection file, and you can specify the
         filelist option only once in each command.

         If you also specify the preview option:
                  You must also specify file_system_name. The space
                  management client generates tape-optimized list files
                  and a collection file. No files are recalled.

         If you do not specify the preview option:
                  The space management client recalls files.

                  If you also specify file_system_name:
                           The space management client performs a
                           tape-optimized recall.

                           If the list file is a collection file that
                           was generated by dsmrecall:
                                    Recall starts. The list files
                                    referenced by the collection are
                                    processed in the order defined in
                                    the collection file. You must
                                    specify the collection file
                                    generated by dsmrecall; you cannot
                                    specify a tape list file or disk
                                    list file.

                           If the list file was not generated by
                           dsmrecall:
                                    The space management client first
                                    reorders the list to optimize
                                    recalls from tape. Then the space
                                    management client recalls the files.

                  If you do not specify file_system_name:
                           The space management client recalls the files
                           in the list file. The space management client
                           does not reorder the list to optimize recalls
                           from tape.

file_system_name
         Specify a file system. You must also specify the filelist
         option. The space management client optimizes the processing of
         files stored on tape.

Examples

   
  Task                                  Command                        
 -------------------------------------+------------------------------- 
  Recall a single file named            dsmrecall -Detail              
  /migfs1/test/tf04 and display         /migfs1/test/tf04              
  detailed information.                                                
 -------------------------------------+------------------------------- 
  Recall all migrated files in a        dsmrecall -Recursive           
  directory named /mfs4/user1 and all   /mfs4/user1/*                  
  migrated files in its                                                
  subdirectories.                                                      
 -------------------------------------+------------------------------- 
  Recall all files in the FILElist      dsmrecall                      
  named /tmp/filelist . Results are     -Logname=/tmp/recalllog        
  logged in the log file                -filelist=/tmp/filelist        
  /tmp/recalllog .                                                     
 -------------------------------------+------------------------------- 
  Recall the specified portion of a     dsmrecall -offset=10M          
  file named /mfs1/file10 in partial    -size=500M /mfs1/file10        
  recall mode.                                                         



2.30 dsmrecalld


The dsmrecalld command starts a recall daemon if it is not running.

You must have root user authority to use this command.

Note:

*  No action is taken if you issue this command while a recall daemon is
   running.

*  When using the backup-archive client to restore space-managed files,
   dsmrecalld must be running.

Syntax

>>-DSMRECALLD--+---------+-------------------------------------><
               '-options-'   



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.


2.31 dsmreconcile


The dsmreconcile command synchronizes the file systems on your client
node with the IBM Spectrum Protect server that you contact for space
management services. Use this command at any time to reconcile one or
more file systems. Specify how often to automatically reconcile with the
reconcileinterval option and how long to keep obsolete copies with the
migfileexpiration option in the dsm.sys file.

You must have root user authority to use this command.

Note:

*  The dsmreconcile command must be found with the PATH variable, or the
   dsmmonitord daemon cannot reconcile the file system.

*  In a multiple-server environment, you can run the dsmreconcile
   command on any HSM node, not just the node that owns the file system.
   In a non-multiple-server environment, you can run only the
   dsmreconcile command on the node that owns the file system.

*  When node replication is used on the IBM Spectrum Protect failover
   server, you can restore files from the failover server. However,
   restoring stub files from the failover server is not supported.
   Instead of restoring the stub files, the resident files will be
   restored. In such a case, when you reconfigure HSM to connect to a
   failover server, the dsmmigundelete and dsmreconcile commands are not
   supported.

Syntax

>>-DSMRECONCILE--+---------+-----------------------------------><
                 '-options-'   



Parameters

options
         -Detail
                  Prints progress messages.

         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -FILEINFO
                  Expires and deletes obsolete copies from the IBM
                  Spectrum Protect server. This option is the basic
                  reconciliation task and is the default option.

         -FILELIST=file_path
                  Specifies the path of a file that contains a list of
                  files to be processed by this command.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

         -ORPHANCHECK
                  Checks for orphaned files in the local file system.

                  The HSM client verifies that valid objects for each
                  local stub file exist in the space management pool of
                  the IBM Spectrum Protect server. The dsmreconcile
                  process determines all migrated and premigrated files,
                  and checks that corresponding objects exist on the
                  server. When orphans are located, their names are
                  recorded in the
                  file_system_name/.SpaceMan/orphan.stubs file. This
                  command option overrides the value of the
                  checkfororphans option in the dsm.sys file.

                  If you previously ran the dsmreconcile command with
                  the preptwo option, IBM Spectrum Protect reconciles
                  with a two-way orphan check.

                  The two-way orphan check processing identifies orphans
                  on the file system and on the IBM Spectrum Protect
                  server. The two-way check is done in a single pass and
                  the orphan identification process uses parallel
                  processing.

                  Tip: If reconciliation is controlled by the space
                  management client space monitor daemon, the scout
                  daemon must be running when you specify this option.
                  If reconciliation is controlled by the GPFS policy
                  engine, the scout daemon is not necessary.

                  When the reconciliation process is running in
                  orphan-check mode, metadata information is updated on
                  the server. Obsolete copies of files are not expired
                  or deleted on the server.



         -PREPTWO
                  This option prepares a file system for a two-way
                  orphan check. Use this option when reconciliation is
                  controlled by the GPFS policy engine.
                  When reconciliation is controlled by the GPFS policy
                  engine, migrated and premigrated files are associated
                  with DMAPI attribute extObjId. If you set
                  hsmextobjidattr=YES, the DMAPI attribute extObjId is
                  associated with the files when they are migrated or
                  premigrated. The preptwo option makes the association
                  for any files that were not associated with the
                  extObjId attribute when the files were migrated or
                  premigrated.

                  The preptwo option is valid only if
                  hsmextobjidattr=YES.

                  When you specify the preptwo option, do not specify
                  any of the following options:

                  *  fileinfo

                  *  filelist

                  *  orphancheck

         -SErver=server_name
                  Specify the target server for the task. This option is
                  valid only in a multiple-server environment, and must
                  be used only with the two-way, orphan-check
                  reconciliation mode.

                  If a file is coupled with a server, the value of this
                  option must be that coupled server. If you specify
                  another IBM Spectrum Protect server, the task fails.

         filesystemspec
                  The name of the file system to reconcile. If you do
                  not specify a file system name, the space management
                  client reconciles all file systems on your workstation
                  for which space management is active. If you enter
                  more than one file system name, separate each name
                  with at least one blank space.

Examples

   
  Task                                         Command                 
 --------------------------------------------+------------------------ 
  Start reconciliation for all file systems    dsmreconcile            
  for which space management is active.                                
 --------------------------------------------+------------------------ 
  Start reconciliation for the /migfs1 file    dsmreconcile /migfs1    
  system.                                                              
 --------------------------------------------+------------------------ 
  Start an orphan check reconciliation         dsmreconcile            
  process for the /migfs1 file system.         -orphancheck /migfs1    
 --------------------------------------------+------------------------ 
  Start reconciliation for file systems        dsmreconcile /home      
  /home and /test1.                            /test1                  
 --------------------------------------------+------------------------ 
  Prepare the two-way orphan check             dsmreconcile -preptwo   
  reconciliation for the /migfs1 file          /migfs1                 
  system.                                                              
 --------------------------------------------+------------------------ 
  Start the policy-based reconciliation on     dsmreconcile            
  the files that are listed in the             -orphancheck            
  /home/dsn/filelist file list.                -filelist=/home/dsn/fi  
                                               lelist                  



2.32 dsmrm


The dsmrm command removes a recall process from the queue. To obtain the
required recall ID to remove a recall process, use the dsmq command.

You must have root user authority to use this command.

Note: After a recall process starts, issue the dsmrm command to stop the
process. Do not use Ctrl+C to stop a recall process.

The dsmrm command cannot stop recalls triggered by the optimized tape
recall processing. For more information on stopping optimized tape
recall processing, see 'Optimized tape recall processing' in the User's
Guide.

Syntax

          .--------------.                
          V              |                
>>-DSMRM------recallid---+--+---------+------------------------><
                            '-options-'   



Parameters

recallid
         The recall process ID that you want to remove from the queue.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

Examples

   
  Task                                               Command           
 --------------------------------------------------+------------------ 
  Remove recall ID 10 from the queue.                dsmrm 10          
 --------------------------------------------------+------------------ 
  Remove recall ID 5 and recall ID 6 from the        dsmrm 5 6         
  queue.                                                               



2.33 dsmscoutd


The dsmscoutd command starts, stops, and restarts the scout daemon. You
can also use the command to start a scan, show future scan times, and
show past scan information for file systems.

You must have root user authority to use this command.

Syntax

                .-start-.                                    
>>-DSMSCOUTD--+-+-------+-------------------+--+---------+-----><
              +---stop----------------------+  '-options-'   
              +---restart-------------------+                
              +-+-scanplan-----------+------+                
              | | .-all------------. |      |                
              | '-+-filesystemspec-+-'      |                
              +-scannow--+-filesystemspec-+-+                
              |          '-all------------' |                
              +-statistics--filesystemspec--+                
              '-help------------------------'                



Parameters

All parameters must be entered as indicated. The parameters must be
entered in lowercase. The parameters have no abbreviation. The
parameters have no short format.

start
         Starts the scout daemon. This option is the default, when no
         parameters are specified.

stop
         Stops the scout daemon.

restart
         Stops and restarts the daemon.

scanplan
         Displays information about the next scan time, include the
         remaining time until the next scan, for one or more file
         systems. If the results of this command do not show the status
         of space-managed file systems, the dsmscoutd daemon lost its
         communication paths. Communications paths can be lost because
         of unexpected file system issues such as unmounting a file
         system. Use the dsmscoutd restart command to recover the
         communication paths for the daemon.

all
         Use this option to include all file systems in the specific
         action.

filesystemspec
         The file system name. You can specify more than one file system
         name, and you can use wildcard characters within a file system
         name. If you specify more than one file system name, separate
         each name with one or more blank spaces.

scannow
         Starts scanning of one or more file systems.

statistics
         Provides statistics about the current (if there is one) and
         last scan of the file system.

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.


2.34 dsmsetpw


The dsmsetpw command changes the IBM Spectrum Protect password for your
client node.

You must have root user authority to use this command.

To keep your password secure, issue the dsmsetpw command without your
old password and new password. The system prompts you for each one. When
you are prompted to enter your old and new passwords, you eliminate the
possibility that another user can display your password.

If your IBM Spectrum Protect server is at version 6.3.3 or later, and if
you use an LDAP directory server to authenticate passwords
         Use any of the following characters to create a password:

         a b c d e f g h i j k l m n o p q r s t u v w x y z
         A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
         0 1 2 3 4 5 6 7 8 9 . ! @ # $ % ^ & * _ - + = ` ( ) 
         | { } [ ] : ; < > , ? / ~

         Passwords are case-sensitive and are subject to more
         restrictions that can be imposed by LDAP policies.

If your IBM Spectrum Protect server is at version 6.3.3 or later, and if
you do not use an LDAP directory server to authenticate passwords
         Use any of the following characters to create a password:

         a b c d e f g h i j k l m n o p q r s t u v w x y z
         A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
         0 1 2 3 4 5 6 7 8 9 . ! @ # $ % ^ & * _ - + = ` ( ) 
         | { } [ ] : ; < > , ? / ~

         Passwords are stored in the IBM Spectrum Protect server
         database and are not case-sensitive.

If your IBM Spectrum Protect server is earlier than version 6.3.3
         Use any of the following characters to create a password:

         a b c d e f g h i j k l m n o p q r s t u v w x y z
         A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
         0 1 2 3 4 5 6 7 8 9
         _ - & + . 

         Passwords are stored in the IBM Spectrum Protect server
         database and are not case-sensitive.

On the command line, enclose a password in single quotation marks (') if
the password contains one or more special characters. The quotation
marks ensure that the special characters are correctly interpreted as
password characters. Without quotation marks, the special characters can
be interpreted as shell escape characters, file redirection characters,
or other characters that have significance to the operating system.

Syntax

>>-DSMSETPW--+---------+---------------------------------------->
             '-options-'   

>--+----------------------------------+------------------------><
   '- --oldpassword-- --newpassword-'   



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.

oldpassword
         The current IBM Spectrum Protect password for your client node.

newpassword
         The new IBM Spectrum Protect password to set for your client
         node.

Examples

   
  Task                                          Command                
 ---------------------------------------------+----------------------- 
  Change your current IBM Spectrum Protect      dsmsetpw osecret       
  password from osecret to nsecret.             nsecret                



2.35 dsmwatchd


The dsmwatchd command starts the watch daemon.

The watch daemon checks the status of the recall daemon, the monitor
daemon, and the scout daemon. If any of these daemons end or become
corrupted, dsmwatchd automatically recovers the failed daemon.

Valid only on GPFS file systems.

You must have root user authority to use this command.

Restriction: Do not use this command from the console. During
installation, it is added to /etc/inittab. The dsmwatchd command
requires an IBM Spectrum Scale cluster.

The dsmwatchd command writes error messages to the /dsmerror.log. If you
want dsmwatchd to use another /dsmerror.log file, you have the following
options:

*  Use the errorlogname option as a command option when you start
   dsmwatchd.

*  Use the errorlogname option in the dsm.sys file to qualify the path
   and the file name in which to store information about errors that
   occur during processing. The value of this option overrides the
   DSM_LOG environment variable.

*  Set the environment variable, DSM_LOG. For example:

   DSM_LOG=/usr/tivoli.tsm/client/hsm/bin/dsmerror.log

*  Restart the dsmwatchd daemon. When the dsmwatchd daemon starts, it
   reads the new errorlogname option value or the new DSM_LOG
   environment variable setting.

   On Red Hat Enterprise Linux Version 6 (RHEL6):
            Stop and restart the daemon with the following commands:

            initctl stop HSM  
            initctl start HSM

   On all other systems besides RHEL6:
            Stop the dsmwatchd daemon by using the command kill -15
            dsmwatchd_pid. The dsmwatchd daemon is restarted by the next
            init process.

You can stop the dsmwatchd daemon permanently.

On Red Hat Enterprise Linux Version 6 (RHEL6):
         Stop the daemon with the following command:initctl stop HSM.

On all other systems besides RHEL6:
         Remove the dsmwatchd entry from the /etc/inittab file.

Note:

1. For IBM Spectrum Scale AIX, set the DSM_LOG environment variable in
   the /etc/environment file.

2. For IBM Spectrum Scale Linux, the /etc/environment file does not
   exist. Use the errorlogname option.

Syntax

>>-DSMWATCHD--+---------+--------------------------------------><
              '-options-'   



Parameters

options
         -ERRORLOGName=file_path
                  Specifies the path and file name of the error log file
                  to be used by this command. Output from only this
                  command is logged to the specified file. Other
                  commands and daemons write output to the error log
                  file specified by the errorlogname option in options
                  file dsm.sys or dsm.opt, or as specified by the
                  DSM_LOG environment variable. If any part of the path
                  you specify does not exist, the space management
                  client creates it.

         -Help
                  Displays syntax and options for the command. Do not
                  specify other options when you specify the help
                  option.


3.0 Options files reference


The space management client provides system and space management options
that you set either in your dsm.sys file or in your dsm.opt file. The
values that you set for space management options determine which server
your client node contacts for space management services and affect
automatic migration, reconciliation, and recall.




3.1 afmskipuncachedfiles


The afmskipuncachedfiles option specifies whether uncached and dirty
files in IBM Spectrum Scale Active File Management file sets are
processed for backup, archive, and migration operations.

IBM Spectrum Scale Active File Management and uncached and dirty file
states are explained in General Parallel File System product
information.

Running HSM on GPFS file systems that use Active File Management file
sets is explained in Configuring IBM Spectrum Protect for IBM Spectrum
Scale Active File Management. If you back up, archive, or migrate files
from a file system that contains Active File Management file sets, set
afmskipuncachedfiles=yes.

Restriction: If Active File Management is running in Local Update (LU)
mode, the afmskipuncachedfiles option in the cache file set must be set
to No.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                         .-NO--.   
>>-AFMSKIPUNCACHEDFILES--+-----+-------------------------------><
                         '-YES-'   



Parameters

NO
         The Active File Management file state is ignored during backup,
         archive, and migration operations. Migration operations on
         uncached or dirty files fail and yield error message ANS9525E.
         Back up and archive operations on uncached files require Active
         File Management fetch operations. The fetch operations can
         cause significant network traffic between the Active File
         Management home and cache.

YES
         Uncached or dirty files in Active File Management file sets are
         skipped during backup, archive, and migration processing.


3.2 candidatesinterval


The candidatesinterval option specifies how often the dsmscoutd daemon
searches the file systems for migration candidates.

The dsmscoutd daemon scans the file systems and stores the information
in a complete file index (CFI), which is used to search for migration
candidates.

Tip: When automatic migration is driven by GPFS policy, the dsmscoutd
daemon is disabled, and the candidatesinterval option has no effect.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-CANDIDATESINTERVAL--scan_interval---------------------------><



Parameters

scan_interval
         Specifies the maximum interval of time that elapses between
         each successive time the dsmscoutd daemon automatically scans
         for files in the file systems. The range of values is 0 to
         9999. The default is 1.

         Specify 0 to continuously scan the file systems. When scanning
         reaches the end of a file system, the dsmscoutd daemon
         immediately begins scanning again from the beginning of the
         file system.

         Specify 1 to scan the file systems at intervals that depend on
         the percentage of the file system content that has changed. The
         dsmscoutd daemon increases the frequency of scanning as the
         percentage of file system changes increases. The dsmscoutd
         daemon reduces the frequency of scanning as the percentage of
         file system changes decreases. This is the default.

         Specify a value from 2 to 9999 to define the number of hours
         between file system scans. After scanning reaches the end of
         the file system, the dsmscoutd daemon waits the specified
         number of hours before starting the next scan.


3.3 checkfororphans


The checkfororphans option specifies whether or not the dsmreconcile
command checks for migrated files that are no longer present on the
server but whose stub files still remain on the client (orphans). The
option parameter that you set determines whether or not the dsmreconcile
command queries the scout daemon for all migrated and premigrated files.



Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                     .-NO--.   
>>-CHECKFororphans --+-----+-----------------------------------><
                     '-YES-'   



Parameters

NO
         The dsmreconcile command checks for orphans only when you
         remove the space management client from your file system, or
         when you specify the -o parameter with the dsmreconcile
         command. Queries to the scout daemon for migrated and
         premigrated files are not done. This is the default.

YES
         The dsmreconcile command checks for orphans. When orphans stubs
         are located, their names are recorded in
         .SpaceMan/orphan.stubs. The dsmreconcile command queries the
         scout daemon for all migrated and premigrated files.

         The scout daemon must be running if the checkfororphans option
         is set to YES.


3.4 checkthresholds


The checkthresholds option specifies how often the space monitor daemon
checks space usage on your file systems. The space monitor daemon checks
each file system to which you added space management.

Tip: When automatic migration is driven by GPFS policy, the dsmmonitord
daemon is disabled, and the checkthresholds option has no effect.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-CHECKThresholds--interval-----------------------------------><



Parameters

interval
         Specifies the number of minutes that must elapse before the
         space monitor daemon checks space usage on your file systems.
         The range of values is 1 through 9999. The default is 5.


3.5 compression


The compression option compresses files before you send them to the
server. Compressing your files reduces data storage for backup versions
and archive copies of your files. It can, however, affect IBM Spectrum
Protect throughput.

Tip: This option controls compression only if your administrator
specifies that your client node determines the selection. The server
also can define this option.

A fast processor on a slow network connection benefits from compression,
but a slow processor on a fast network connection does not. Use this
option with the backup-archive client option, compressalways.

If you specify compressalways YES, compression continues even if the
file size increases. To stop compression if the file size grows, and
resend the uncompressed file, specify compressalways NO.

If you specify compression YES, you can control compression processing
in the following ways:

*  Use the exclude.compression option in your include-exclude options
   file to exclude specific files or groups of files from compression
   processing.
*  Use the include.compression option in your include-exclude options
   file to include files within a broad group of excluded files for
   compression processing.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

                .-NO--.   
>>-COMPRESSIon--+-----+----------------------------------------><
                '-YES-'   



Parameters

NO
         Files are not compressed before they are sent to the server.
         This is the default.

YES
         Files are compressed before they are sent to the server.


3.6 defaultserver


The defaultserver option specifies the default server to which you back
up and archive your files from your local file systems. If you do not
specify a migration server with the migrateserver option, this option
can also specify the server to which files are migrated from your local
file systems.



Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-DEFAULTServer--servername-----------------------------------><



Parameters

servername
         Use the defaultserver option to specify the name of the IBM
         Spectrum Protect server to contact for backup-archive services
         if more than one server is defined in the dsm.sys file. By
         default, the space management client contacts the server that
         is defined by the first stanza in the dsm.sys file. This option
         is only used if the servername option is not specified.

         If you do not specify a migration server with the migrateserver
         option, this option specifies the server to which you want to
         migrate files.

         You can override this option with the following command:
         dsmmigfs upd /FS -SErver=servername. Replace servername with
         the name of your server.

         The value of defaultserver in the dsm.sys file overrides
         defaultserver in the dsm.opt file.


3.7 errorlogname


The errorlogname option specifies the path of the file that logs error
messages for the space management client and the backup-archive client.

This option specifies the fully qualified path and file name of the
error log file. If this option is not specified, the default log file is
used. The default error log file is the dsmerror.log file in the current
working directory.

Authorized user: The value for this option overrides the DSM_LOG
environment variable.

The log file path cannot be a symbolic link.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

>>---ERRORLOGName--filespec------------------------------------><



Parameters

filespec
         The fully qualified path in which to store error log
         information. If any part of the path you specify does not
         exist, the space management client creates it.

         The log file path cannot be a symbolic link.


3.8 errorprog


The errorprog option specifies a program to which you want to send a
message if a severe error occurs during space management processing.

The errorprog option specifies a program to which you want to send a
message if a severe error occurs during space management processing.

The program is started only in case of very severe errors such as DMI or
file system errors. Also, only processes that do not have an output
channel, such as daemons, use this option. Use the full path to specify
the program. The error message is sent to the standard input of the
program.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-ERRORProg--program-name-------------------------------------><



Parameters

program-name
         Specifies the path and file name of the program to which you
         want to send a message if a severe error occurs during space
         management processing.

         Some examples:

            errorprog /usr/bin/cat >/tmp/tsm_severe_errors.txt

            errorprog /usr/bin/perl /root/dsmseverror.pl


3.9 hsmdisableautomigdaemons


Use the hsmdisableautomigdaemons option to control the start of the
dsmscoutd and dsmmonitord daemons.

When a GPFS policy monitors migration thresholds, the dsmscoutd and
dsmmonitord daemons can be disabled. Stop and restart the dsmwatchd
daemon to activate a new value of the hsmdisableautomigdaemons option.
The dsmwatchd daemon is restarted by the init process or the initctrl
process.

Supported Clients

This option is valid only on GPFS file systems.

Options File

Place this option in the client options file dsm.opt.

Syntax

                             .-NO--.   
>>-HSMDISABleautomigdaemons--+-----+---------------------------><
                             '-YES-'   



Parameters

NO
         Specifies that the space management client automatic migration
         daemons dsmscoutd and dsmmonitord are started. This is the
         default.

YES
         Specifies that thedsmscoutd and dsmmonitord daemons are not
         started.

Tip: The dsmscoutd and dsmmonitord daemons can also be started by the
GPFS daemon (mmfsd).


3.10 hsmdistributedrecall


The hsmdistributedrecall option specifies whether a node that is running
as owner node can delegate recall requests to other nodes in an IBM
Spectrum Scale cluster.

To stop distributed recalls for an entire cluster, set this option to NO
for all HSM nodes in the cluster and restart the dsmrecalld daemons.
Then, only the HSM owner node can recall migrated files to the
space-managed file systems it owns.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                         .-YES-.   
>>-HSMDISTRibutedrecall--+-----+-------------------------------><
                         '-NO--'   



Parameters

YES
         The node can delegate recall requests to other nodes in an IBM
         Spectrum Scale cluster. This is the default.

NO
         The node cannot delegate recall requests to other nodes in an
         IBM Spectrum Scale cluster.


3.11 hsmenableimmediatemigrate


The hsmenableimmediatemigrate option determines if files that are less
than 2 minutes old can be migrated during selective migration.

When a file is created, file status information can take some time to
become synchronized among IBM Spectrum Scale nodes. If you create a
file, then migrate the file before file information is synchronized, the
file size information returned from a dsmdu or dsmdf command can be
inaccurate. Because of the typical time needed for IBM Spectrum Scale
synchronization, by default the space management client does not migrate
a file that is less than 2 minutes old.

To migrate files that are less than 2 minutes old, set
hsmenableimmediatemigrate=YES. When you set
hsmenableimmediatemigrate=YES, the space management client issues system
synchronization commands before migrating each file that is less than 2
minutes old.

This option applies only during selective migration.

Options File

Place this option in the client options file dsm.opt.

Syntax

                              .-NO--.   
>>-HSMENABLEIMMediatemigrate--+-----+--------------------------><
                              '-YES-'   



Parameters

NO
         Files that are less than 2 minutes old cannot be migrated. This
         is the default.

YES
         Files that are less than 2 minutes old can be migrated during
         selective migration.


3.12 hsmeventdestroy


The hsmeventdestroy option specifies whether immediate reconciliation
occurs.

When you set HSMEVENTDESTROY yes, the dsmreconciled daemon starts on the
affected nodes. The dsmreconciled daemon synchronizes the expirations on
the IBM Spectrum Protect server with deletions on the space-managed file
system.

Options File

Place this option in the client options file dsm.opt.

Syntax

                    .-NO--.   
>>-HSMEVENTdestroy--+-----+------------------------------------><
                    '-YES-'   



Parameters

NO
         Immediate reconciliation does not occur. A migrated or
         premigrated file that is deleted on the space-managed file
         system is expired on the IBM Spectrum Protect server only
         during a reconciliation of the file system. This is the
         default.

YES
         Immediate reconciliation occurs. When a migrated or premigrated
         file is deleted on the space-managed file system, the migration
         copy on the IBM Spectrum Protect server is expired immediately.


3.13 hsmextobjidattr


The hsmextobjidattr option specifies whether the dsmreconcile,
dsmmigrate, dsmrecall, or dsmrecalld command assigns an object ID to the
file as a Data Management Application Programming Interface (DMAPI)
extended attribute (extObjId).

The extObjId DMAPI extended attribute is required for two-way orphan
check reconciliation.

The two-way orphan check processing identifies orphans on the file
system and on the IBM Spectrum Protect server. The two-way check is done
in a single pass and the orphan identification process uses parallel
processing.

Place this option in the client options file dsm.opt.

Syntax

                     .-YES-.   
>>-HSMEXTOBjidattr --+-----+-----------------------------------><
                     '-NO--'   



Parameters

YES
         An object ID is stored in the file that is processed by the
         dsmmigrate, dsmrecall, dsmrecalld, or the dsmreconcile command
         with the preptwo option. This is the default.

NO
         An object ID is not assigned to the file that is processed by
         the dsmmigrate, dsmrecall, dsmrecalld, or the dsmreconcile
         command with the preptwo option. When a reconciliation is run
         with the preptwo option, files are not prepared for the two-way
         orphan check.


3.14 hsmgroupedmigrate


The hsmgroupedmigrate option specifies whether the dsmmigrate command
migrates more than one file with each transaction.

The transfer of multiple files per transaction can improve performance
when migrating many small or medium size files (up to 100 MB).

The default action is to migrate each file in a single transaction and
make a stub file when the transaction is successful.

When this option is set to YES the HSM transaction grouping is
activated. A group of files is migrated in each transaction with the IBM
Spectrum Protect server when either the transaction byte limit or the
transaction group limit is reached. The transaction byte limit has a
default of 25 MB, and can be set with the txnbytelimit option. The
transaction group limit is specified with the txngroupmax option. The
txngroupmax option is set on the server in the options file or on the
node definition on the server. If a file with a different management
class setting is added to the group, the group is migrated immediately.

If a file with a different file system root is added to the group, the
group is migrated immediately.

The hsmgroupedmigrate option works in LAN-free configurations and when
data is transferred over LAN.

Options File

Place this option in the client options file dsm.opt.

Syntax

                      .-NO--.   
>>-HSMGROUPedmigrate--+-----+----------------------------------><
                      '-YES-'   



Parameters

NO
         The dsmmigrate command migrates one file per transaction with
         the IBM Spectrum Protect server. This is the default.

YES
         The dsmmigrate command migrates a group of files in each
         transaction with the IBM Spectrum Protect server.


3.15 hsmlogeventflags


The hsmlogeventflags option specifies which kinds of events are added to
the HSM log file.

You must use an authorized user ID to use this option.

If this option is not specified, or if no flags are included in the
specification, no HSM log entries are made.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

>>---HSMLOGEVENTFLAGS--Flags-----------------------------------><



Parameters

Flags
         Indicate one or more of the following values:

         FILE
                  File events are logged. File events include file
                  migration and recall processing.

         FS
                  File system events are logged. File system events
                  include threshold migration, reconciliation, and
                  HSM-related file system configuration changes.


3.16 hsmlogmax


The hsmlogmax option specifies the maximum size of the HSM log, in
megabytes.

You must use an authorized user ID to use this option.

If you use the hsmlogretention option instead of the hsmlogmax option,
all existing log entries are retained and the log is pruned according to
the new hsmlogretention option age criteria.

If you use the hsmlogmax option instead of the hsmlogretention option,
all records in the existing log are copied to the pruned log file,
dsmhsm.pru. Then the existing log is emptied, and logging begins under
the hsmlogmax option size criteria.

If you change the value of the hsmlogmax option, the existing log is
extended or shortened to accommodate the new size. If the value is
reduced, the oldest entries are deleted to reduce the file to the new
size.

Restriction: You cannot specify a nonzero hsmlogmax option value and
activate the hsmlogretention option.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

>>---HSMLOGMAX--size-------------------------------------------><



Parameters

size
         Specifies the maximum size, in megabytes, for the log file. The
         range of values is 0 - 2047; the default is 0, which specifies
         that the log file has no size limit.


3.17 hsmlogname


The hsmlogname option specifies the HSM log file name.

This option specifies the fully qualified path and file name of the HSM
log file. If this option is not specified, the default log file is used.
The default log file is dsmhsm.log and is in the same directory as the
dsmerror.log file.

You must use an authorized user ID to use this option.

The value for this option overrides the DSM_LOG environment variable.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

>>---HSMLOGName--filespec--------------------------------------><



Parameters

filespec
         The fully qualified path and file name of the HSM log file. If
         any part of the path you specify does not exist, the space
         management client creates it.

         The log file path cannot be a symbolic link.


3.18 hsmlogretention


The hsmlogretention option specifies how many days to maintain HSM log
entries before pruning, and whether to save the pruned entries.

The HSM log is pruned when the first entry is written to the log after a
space management client command or daemon is started. Some daemons run
continuously. Stop the daemons and start them again or activate one of
the HSM commands to prune the HSM log.

You must use an authorized user ID to use this option.

If you use the hsmlogmax option instead of the hsmlogretention option,
all records in the existing log are copied to the pruned log file,
dsmhsm.pru. Then the existing log is emptied, and logging begins under
the new size criteria.

If you use the hsmlogretention option instead of the hsmlogmax option,
all existing log entries are retained and the log is pruned according to
the new hsmlogretention option age criteria.

Restriction: You cannot specify the hsmlogretention option and a nonzero
value for the hsmlogmax option.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

                    .-N-----------.   
>>-HSMLOGRetention--+-------------+----------------------------><
                    |       .-D-. |   
                    '-days--+---+-'   
                            '-S-'     



Parameters

N
         Do not prune the log. The HSM log grows indefinitely. This is
         the default.

days
         The number of days to keep log file entries before pruning the
         log. The range of values is 0 - 9999.

D or S
         Specifies whether to save the pruned entries. You must also
         specify the days parameter. Enter a space or comma to separate
         the days parameter from the D or S parameter.

         D
                  Discard the HSM log entries when you prune the log.
                  This is the default.

                  Example task: Prune the log every 7 days. Discard the
                  pruned log entries.

                  Example command: hsmlogr 7 d

         S
                  Save the HSM log entries when you prune the log. The
                  pruned entries are copied from the HSM log to the
                  dsmhsm.pru file that is in the same directory as the
                  HSM log.

                  Example task: Prune the log every 100 days. Save the
                  pruned log entries.

                  Example command: hsmlogr 100,s


3.19 hsmlogsampleinterval


The hsmlogsampleinterval option specifies how often to gather file
system data for the HSM log file.

You must be an authorized user to use the hsmlogsampleinterval option.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

>>---HSMLOGSampleinterval--interval----------------------------><



Parameters

interval
         Specifies the number of seconds between each gathering of file
         system data. The range of values is 0 - 9999999 and the default
         value is 3600 (one hour). If 0 is specified, no file system
         data is gathered.


3.20 hsmmaxrecalltapedrives


The hsmmaxrecalltapedrives option controls how many tape drives
participate in tape-optimized recall processing.

By limiting the available tape drives for tape optimized recall
processing, you can prevent all drives from being blocked. In this way,
some drives remain accessible for transparent recall processing and
migration.

If the value of the hsmmaxrecalltapedrives option is greater than the
number of tape drives available, a recall thread waits for the next
available tape drive. If you plan to run tape-optimized recalls
processes in parallel, the number can be decreased accordingly for
parallel processing without running out of tape drives.

If the maxnummp option is defined on the IBM Spectrum Protect server,
you can set the hsmmaxrecalltapedrives option to a number that is less
than or equal to the maxnummp option. You can reserve tape drives for
other operations if you set the number lower than the maxnummp option
and the maximum number of tape drives.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>---HSMMAXREcalltapedrives--value-----------------------------><



Parameters

value
         Specifies the number of tape drives available for a
         tape-optimized recall. The range of values is 1 -10. The
         default is 5.


3.21 hsmmigzeroblockfiles


The hsmmigzeroblockfiles option specifies whether the space management
client migrates files that allocate zero data blocks in the file system.

Some files are so small that the metadata and the file content fit
completely in the inode. The file system allocates no data blocks for
such small files. Migrating such small files does not save space on the
file system. By default, the space management client migrates such small
files when the files meet migration criteria. You can set
HSMMIGZEROBLOCKFILES NO if you do not want to migrate such small files.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                         .-YES-.   
>>-HSMMIGZEROBLOCKFILES--+-----+-------------------------------><
                         '-NO--'   



Parameters

YES
         Files that allocate zero data blocks in the file system, but
         have a logical size greater than zero, can be migrated. This is
         the default.

NO
         Files that allocate zero data blocks in the file system cannot
         be migrated.


3.22 hsmmultiserver


The hsmmultiserver option enables and disables migration and backup in
an environment of multiple IBM Spectrum Protect servers.

You can enable migration and backup from a single file system to
multiple IBM Spectrum Protect servers. You must set hsmmultiserver=YES
for each space management client in the IBM Spectrum Scale cluster.

If you set hsmmultiserver=NO, all of the command options for the
multiple-server environment are disabled. When you set
hsmmultiserver=NO, you can recall files only from the IBM Spectrum
Protect migration server that is configured in the dsm.sys options file.
If a file was migrated to a server other than the server that is
configured in the dsm.sys options file, you cannot recall the file.

Supported Clients

The option is available only for IBM Spectrum Scale AIX clients and IBM
Spectrum Scale Linux clients.

Options File

Place this option in the client options file dsm.opt.

Syntax

                   .-NO--.   
>>-HSMMULTIServer--+-----+-------------------------------------><
                   '-YES-'   



Parameters

NO
         All of the command options for the multiple-server environment
         are disabled. All HSM commands have standard input and output.
         This is the default.

YES
         All of the command options for the multiple-server environment
         are enabled. All HSM commands that display a list add an
         additional column that shows the IBM Spectrum Protect server
         name.


3.23 hsmoptimizedrecallonly


The hsmoptimizedrecallonly option specifies whether the space management
client blocks all non-optimized recall processes.

By default, with hsmoptimizedrecallonly set to No, all recalls are
allowed and users and applications can access all migrated files. If
hsmoptimizedrecallonly is set to YES, access to migrated files, which
require recalling data from the IBM Spectrum Protect server, are blocked
and the application receives no access and the error code EACCES. No
access includes reading the content of migrated files, and changing the
content to migrated files. Reading of premigrated files is not blocked
as the data is located in the local file system. If a recall is blocked,
the dsmrecalld command writes the message ANS2735W to the error log file
every 24 hours. If the recall is triggered by the dsmrecall command or
the dsmc command, the message ANS4007E is also logged to the error log
file.

To recall the content of migrated files with hsmoptimizedrecallonly set
to YES, compile a list of files, and follow the instructions for
'Recalling files with optimization for tape' in the User's Guide.

Supported Clients

The option is available only for IBM Spectrum Scale on AIX clients and
IBM Spectrum Scale Linux clients.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                           .-NO--.   
>>-HSMOPTIMIZEDRecallonly--+-----+-----------------------------><
                           '-YES-'   



Parameters

NO
         All recalls are allowed. This is the default.


YES
         All non-optimized recalls are blocked.


3.24 hsmrecallbufferalignment


The hsmrecallbufferalignment option specifies whether and how the
internal buffer address for recall operations is aligned in the recall
process memory. The alignment can significantly impact the recall
performance.



Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                             .-4----------------.   
>>-HSMRECALLBUFFERAlignment--+------------------+--------------><
                             '-address_boundary-'   



Parameters

address_boundary
         Specifies the alignment (in kilobytes) at which the internal
         buffer address is aligned. The range of values is 1 -
         2147483647.
         The default value is 4. If a value of 2147483647 is specified,
         no internal memory alignment occurs.
         The option controls the buffer address alignment in the heap
         and system memory. For more information, see the man pages for
         the posix_memalign() system call.


3.25 hsmrecallbuffersize


The hsmrecallbuffersize option specifies the size (in kilobytes) of the
buffer that is used to collect data before the data is written to a file
system as part of a recall operation.



Supported Clients

The HSM client internally buffers data that is received from the IBM
Spectrum Protect server until the amount of data that is specified by
the hsmrecallbuffersize option is collected, and then writes the
collected data to the file system.



Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

                        .-0-----------.   
>>-HSMRECALLBUFFERSize--+-------------+------------------------><
                        '-buffer_size-'   



Parameters

buffer_size
         Specifies the size of the buffer (in kilobytes) that is used to
         store recalled data before the data is restored to the file
         system. The range of values is 0 - 2147483647.
         The default value is 0. In this case, the HSM client uses the
         file system block size as the buffer size. If a value of
         2147483647 is specified, no internal buffering occurs and the
         data is written back to the file system as the data is returned
         from the IBM Spectrum Protect server.
         You might be able to improve file system performance by
         specifying a buffer size that is a multiple of the file system
         block size. A larger value reduces the number of
         resource-intensive operations on the file system. However, a
         larger value also requires more CPU and memory resources.


3.26 hsmrpcport


The hsmrpcport option specifies a Remote Procedure Call (RPC) TCP/IP
port address for the HSM recall services.



Supported Clients

The option is available only for IBM Spectrum Scale on AIX clients and
IBM Spectrum Scale Linux clients.

Options File

Place this option in the client system options file dsm.sys within a
server stanza.

Syntax

>>-HSMRPCPort--port_address------------------------------------><



Parameters

port_address
         Specifies the TCP/IP port address that is used by HSM
         processes. The range of values is 1024 - 65535. By default, the
         HSM services contact the rpcbind daemon to access the RPC port.
         This option should be identical on all HSM client nodes. Ports
         ranging from 23152 to 23157 (or higher) might be used by other
         HSM daemons. Ensure that the port used with the hsmrpcport
         option does not overlap with this port range.
         If the dsmrecalld starts and is not able to use the port
         defined with the hsmrpcport option, one of the messages
         ANS8956E or ANS8957E will be written to the error log file.


3.27 inclexcl


Use the inclexcl option to define the filename and path of your
include-exclude options file.



Syntax

>>-inclexcl --filespec-----------------------------------------><



Parameters

filespec
         Specifies the path and file name for your include-exclude file.


3.28 maxcandprocs


The maxcandprocs option specifies the number of parallel threads in the
scout daemons that can scan for file systems.

Tip: When automatic migration is driven by GPFS policy, the dsmscoutd
daemon is disabled, and the maxcandprocs option has no effect.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MAXCANDProcs--number----------------------------------------><



Parameters

number
         Specifies the maximum number parallel threads in the scout
         daemons that can scan file systems. The range of values is 2 -
         20. The default is 5.


3.29 maxmigrators


The maxmigrators option specifies the maximum number of parallel
migration sessions that can run in parallel for each file system. Ensure
that you have sufficient resources on the server for parallel migration
to occur.

Tip: When automatic migration is driven by GPFS policy, the maxmigrators
option has no effect.

Do not set the maxmigrators option higher than the number of parallel
sessions that the server can use to store data.

This option can be set by the IBM Spectrum Protect server.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MAXMIGRators--number----------------------------------------><



Parameters

number
         Specifies the maximum number of parallel migration sessions
         that you can set. The range is 1 - 20. The default is 5. If
         this option is changed from the default, make a corresponding
         increase in the IBM Spectrum Protect server configuration to
         update the HSM node MAXNUMMP value.


3.30 maxrecalldaemons


The maxrecalldaemons option specifies the maximum number of recall
daemons that you can run at one time to recall files for the client
node. If the number of recall daemons that are running at one time is
close to the maximum number, increase the value.

For example, if you use an application that opens many migrated files at
once, the application can use all available recall daemons. Another
process cannot access a migrated file until a recall daemon is
available.

Note: The IBM Spectrum Scale configuration option dmapiWorkerThreads can
limit the maximum concurrent recall tasks to less than the value
ofmaxrecalldaemons.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MAXRECAlldaemons--number------------------------------------><



Parameters

number
         Specifies the maximum number of recall daemons that can run in
         parallel to recall files for the client node. The range is 2 -
         99. The default is 20.


3.31 maxthresholdproc


The maxthresholdproc option specifies the maximum number of threshold
migration processes that the space management client can start at one
time. When a file system runs out of space, the HSM client does not
verify the maximum number of threshold migration processes that
currently are running. It starts threshold migration as part of the
demand migration process regardless of the number of threshold migration
processes in progress.

Tip: When automatic migration is driven by GPFS policy, the
maxthresholdproc option has no effect.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MAXThresholdproc--number------------------------------------><



Parameters

number
         Specifies the maximum number of automatic threshold migration
         processes that the space management client can start at one
         time. The range of values is 1 - 99. The default is 3.


3.32 migfileexpiration


The migfileexpiration option specifies the number of days that copies of
migrated or premigrated files remain on the server after they are
modified on your local file system or are deleted from your local file
system.



Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MIGFileexpiration--days-------------------------------------><



Parameters

days
         Specifies the number of days a copy of a migrated or
         premigrated file remains in storage after it is modified on
         your local file system, or deleted from your local file system.
         The range of values is 0 - 9999. The default is 7 days.

         Note: If you specify a value of 0, an obsolete copy of a
         migrated or premigrated file is deleted from the server during
         the next reconciliation run. If you delete a file from the
         local file system and reconcile runs with the migfileexpiration
         value as 0, the file can not be recreated by the dsmmigundelete
         process.


3.33 migrateserver


The migrateserver option specifies the name of the server to which you
want to migrate files from your client node. Specify one migration
server for each client node.

If you do not specify a server with the migrateserver option, your files
migrate to the server that you specify with the defaultserver option. If
you do not specify a server with either of these options, your files
migrate to the server that you identify in the first stanza of your
dsm.sys file.

You can override this option with the following command: dsmmigfs upd
/FS -SErver=servername. Replace servername with the name of your server.

The value of migrateserver in dsm.sys overrides migrateserver in
dsm.opt.

After your files migrate to the server that you specified, do not
specify a different migration server unless your administrator transfers
your migrated files from the specified server to another. Otherwise, the
server cannot locate your migrated files until you specify the server to
which your files were originally migrated.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MIGRateserver--servername-----------------------------------><



Parameters

servername
         Specifies the name of the server to which you want to migrate
         files from your client node. Your dsm.sys file must contain a
         stanza beginning with the servername option and it must contain
         the required communication options for the server that you
         specify with the migrateserver option.


3.34 minmigfilesize


The minmigfilesize option specifies the minimum file size for a file to
be eligible for migration.

This option applies to all of the space-managed file systems for which
you have not specified a file system specific value for minmigfilesize
using the dsmmigfs add or dsmmigfs add commands. See 2.12 dsmmigfs add
and update for details.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MINMIGfilesize --fileSize-----------------------------------><



Parameters

fileSize
         Specifies the minimum file size, in bytes, for a file to be
         eligible for migration. The range of values is 0 through
         2147483647. The default is 0.

         On GPFS file systems, if you specify the default, the space
         management client uses the current file system stub size as the
         minimum size for files that can be migrated. For other
         (non-GPFS) file systems, the space management client uses the
         file system block or fragment size or stub size as the minimum
         size for files that can be migrated, whichever is larger.

         If you specify a non-zero value, for GPFS file systems, the
         value must be greater than the stub size. For other (non-GPFS)
         file systems, it must be greater than both the file system
         block or fragment size or stub size. Otherwise, the value is
         ignored.


3.35 minrecalldaemons


The minrecalldaemons option specifies the minimum number of recall
daemons that can run in parallel to recall files for the client node.



Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-MINRecalldaemons--number------------------------------------><



Parameters

number
         Specifies the minimum number of recall daemons that can run in
         parallel. The range of values is 1 - 99. The default is 3.


3.36 reconcileinterval


The reconcileinterval option specifies how often the space monitor
daemon reconciles your file systems. Depending on the checkfororphans
option, the reconciliation either expires or deletes obsolete objects on
the server and updates the status file, or checks for orphan stub files
and makes metadata updates.

Tip: When hsmdisableautomigdaemons=YES, the reconcileinterval option has
no effect.

Options File

Place this option at the beginning of the dsm.sys file before any server
stanzas.

Syntax

>>-RECOncileinterval--interval---------------------------------><



Parameters

interval
         Specifies the number of hours that must elapse between each
         successive time your file systems are automatically reconciled
         on your workstation. If you specify a value of 0, your file
         systems are not reconciled automatically. The range of values
         is 0 - 9999. The default is 24.


3.37 restoremigstate


The restoremigstate option specifies whether you want to restore or
retrieve stub files or backup-archive versions of migrated files during
a restore-retrieve operation. Use this option with the backup-archive
client restore and retrieve commands.

You can restore or retrieve a stub file for a migrated file only when
the following is true:

*  The file exists in the migration storage pool
*  The file is backed up or archived and migrated to the same server

When the number of days elapse that you specified with the
migfileexpiration option, the migrated file is removed from storage.

If you specify restoremigstate YES, and if the migrated file is not
expired, the file is restored or retrieved to a stub file, regardless of
whether it is marked for expiration.

On a space-managed file system, you can restore a stub file only during
standard-query restore processing. During no-query restore processing to
a space-managed file system, you cannot restore stub files.

The restoremigstate option restores a file if it is backed up after
migration. If the file is backed up before migration, you cannot restore
a stub file because a server stub file copy does not exist.

Files with access control lists (ACLs) are restored in a resident state
regardless of the setting for restoremigstate. The restore operation
affects files that are restored to a GPFS file system with more storage
pools than the default system pool.

If you restore a file from the IBM Spectrum Protect target server, and
the file system is managed by the space management client, you must not
restore the file as a stub file. You must restore the complete file. Use
the restoremigstate=no option to restore the complete file. If you
restore the file as a stub from the target server, the following
consequences can occur:

*  You cannot recall the file from the IBM Spectrum Protect source
   server by using the space management client.

*  A space management client reconciliation process that runs against
   the IBM Spectrum Protect source server expires the file. If the file
   is expired by a reconciliation process, you can restore the complete
   file with the backup-archive client and the restoremigstate=no
   option.

Tip: The restoremigstate option does not support hard linked files. If
you want to restore or retrieve a stub file for a hard linked file,
delete all files from your local file system that are hard linked
together. When one file in a set of hard linked files is migrated, all
of the hard linked files in the set become stub files. When you enter
the restore command with the restoremigstate option to restore a stub
file for a hard linked file, the stub file has the same name as the file
that was originally migrated. Stub files are not restored for any other
files that previously were in the hard linked set of files.

Options File

Place this option in the dsm.opt or dsm.sys file.

Syntax

                    .-YES-.   
>>-RESToremigstate--+-----+------------------------------------><
                    '-NO--'   



Parameters

YES
         Restores or retrieves migrated files to stub files on your
         local file system during a restore or retrieve operation. The
         files remain migrated. This is the default.

         Note: A stub file that is created during a restore or retrieve
         operation contains the information that is necessary to recall
         the migrated file from storage. It does not contain any leading
         bytes of data from the file. Any recall mode that was set
         previously for the migrated file (for example, streaming or
         partial file recall) is not stored in the stub file. The recall
         mode is set to normal for all files that are restored or
         retrieved to stub files.

NO
         Restores or retrieves backup-archive versions of migrated files
         to your local file system during a restore or retrieve
         operation. The files become resident.

Command line

This option is valid on the command line.


3.38 skipmigrated


The skipmigrated option specifies whether the IBM Spectrum Protect
backup-archive client process migrated files during a backup or archive
operation. Use this option with the backup-archive client archive,
backup image, incremental, and selective commands.

When the skipmigrated option is set to yes, the backup-archive client
does not back up or archive any stub files. When the skipmigrated option
is set to no, the backup-archive client can process stub files during
some operations.

Options File

Place this option in the dsm.opt file.

Syntax

                 .-NO--.   
>>-SKIPMigrated--+-----+---------------------------------------><
                 '-YES-'   



Parameters

NO
         The backup-archive client does not check the migration status
         of files during a backup or archive operation. This is the
         default.

YES
         The backup-archive client checks the migration status of files
         during a backup or archive operation. The backup-archive client
         does not back up or archive stub files.

Command line

This option is valid on the command line.


4.0 Display a message


To display a message, enter the message number. The prefix is optional.

------------------------------------------------------------------------
ANS0101E

Unable to open English message repository file name.



Explanation:

The default English message repository file cannot be opened. Either the
file access permissions prevent reading the file or the file is not
present in the expected location.

System action:

IBM Spectrum Protect is unable to complete the requested operation.
Processing is terminated.

User response:

Make sure the file in your DSM_DIR is set up properly. If the problem
continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0102W

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



Explanation:

The default message repository file for the current locale cannot be
opened. Either the file access permissions prevent reading the file, the
file is not present in the expected location, or the language specified
in the option file is not supported on this workstation.

System action:

IBM Spectrum Protect continues processing using the English language
message repository.

User response:

Make sure the file in your DSM_DIR is set up properly. If the problem
continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0103E

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



Explanation:

The message repository file header record cannot be obtained.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the file has not been altered from the installation. If the
problem continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0104I

A message repository is not available for your system's configured
language 'language'. The US English message repository is used instead.



Explanation:

IBM Spectrum Protect does not have language support for the specified
language. Therefore, it uses the US English message repository by
default.

System action:

The US English message repository is used.

User response:

No action is necessary if you want to continue to use US English. If you
want to use a different language that is supported by IBM Spectrum
Protect, then: * (Windows) Add the LANGUAGE option to the client option
file and specify a supported language. For example, to configure the
client to use the French language repository, add the option LANGUAGE
FRA to the client option file. Refer to the reference information for
the LANGUAGE option in the backup-archive client product manual. * (UNIX
and Linux) Set the LANG environment variable to a supported language and
region code. For example, to configure the client to use the French
language repository, set LANG to fr_FR. Refer to the backup-archive
client manual for the supported language codes.

------------------------------------------------------------------------
ANS0105E

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



Explanation:

The message text for the specified message number cannot be read.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the file has not been altered from the installation. If the
problem continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0106E

Message index not found for message number.



Explanation:

The message repository file does not contain the message text for the
message number.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the DSM_DIR is set up properly and it does not point to an old
copy. If the problem continues, see your system administrator for
further help.

------------------------------------------------------------------------
ANS0107E

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



Explanation:

The message header information cannot be obtained for the message number
in the message file.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the file has not been altered from the installation. If the
problem continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0108E

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



Explanation:

The message text cannot be obtained for the message number in the
message file.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the file has not been altered from the installation. If the
problem continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0109E

Insufficient memory for allocation of message structure.



Explanation:

There is not enough memory in your system to allocate the storage needed
for the message text.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Stop IBM Spectrum Protect and restart IBM Spectrum Protect. Then retry
the operation. If unsuccessful, close all unneeded applications and
retry the operation.

------------------------------------------------------------------------
ANS0110E

Unable to open error log file file name for output.



Explanation:

The error log cannot be opened for output.

System action:

IBM Spectrum Protect is unable to complete the requested operation. File
permissions may be set such that writing is not allowed.

User response:

Stop and restart IBM Spectrum Protect. Then retry the operation. If
unsuccessful, make sure the file is not being locked by another
application and that file permissions allow write access.

------------------------------------------------------------------------
ANS0113E

Message repository file name has an invalid control record.



Explanation:

The message repository file contains an incorrect control information.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the message file was not altered from the installation. Check
DSM_DIR to make sure it is set up properly.

------------------------------------------------------------------------
ANS0118E

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



Explanation:

The schedule log file cannot be opened for output.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Stop IBM Spectrum Protect and restart IBM Spectrum Protect. Then retry
the operation. If unsuccessful, make sure the file has not been locked
by another application.

------------------------------------------------------------------------
ANS0119E

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



Explanation:

The response string information for the message number cannot be
obtained from the message repository file. It is possible the message
repository has been corrupted.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Make sure the message file was not altered from the installation. Check
DSM_DIR to make sure it is set up properly.

------------------------------------------------------------------------
ANS0120E

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



Explanation:

An illegal multibyte sequence for the current locale was found in the
message. Either the message repository has been corrupted or is coded in
a language other than that of the current locale.

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

If the message repository is not corrupted, process the operation in the
supported locale.

------------------------------------------------------------------------
ANS0121W

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



Explanation:

The iconv converter for the default message repository for the current
locale cannot be opened. The iconv converter used to convert from UTF-8
to the current locale is not installed on this work station.

System action:

IBM Spectrum Protect continues processing using the English language
message repository.

User response:

Make sure the required iconv converter is installed properly. If the
problem continues, see your system administrator for further help.

------------------------------------------------------------------------
ANS0200E

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



Explanation:

The virtual machine was backed up with a later version of the
backup-archive client. The objects of the virtual machine backup that
were retrieved cannnot be correctly displayed.

System action:

The backup information for the virtual machine will not be displayed.

User response:

Query the virtual machine on a later version of the backup-archive
client to view backup details. If a query of all virtual machines does
not display virtual machines that were backed up at the same client
version, issue the Query VM command for individual virtual machines.

------------------------------------------------------------------------
ANS0201E

Invalid parameter was found.



Explanation:

The system encountered an internal program error due to an invalid
parameter.

System action:

The system returns to the calling procedure.

User response:

Ask your service representative to check the error log.

------------------------------------------------------------------------
ANS0202E

Not authorized to restore the other node's data.



Explanation:

The client is not authorized to restore the other node's data.

System action:

The system returns to the calling procedure.

User response:

Get authorization from the other node.

------------------------------------------------------------------------
ANS0203E

The objName field has no leading directory separator.



Explanation:

The objName field does not have a leading directory separator.

System action:

The system returns to the calling procedure.

User response:

Correct the value for the objName.

------------------------------------------------------------------------
ANS0204E

Wildcards are not allowed in the objName directory path.



Explanation:

Wildcards are not allowed in the objName directory path.

System action:

The system returns to the calling procedure.

User response:

Correct the value for the objName.

------------------------------------------------------------------------
ANS0205E

Unable to open error log file.



Explanation:

The system is unable to open the error log file.

System action:

The system returns to the calling procedure.

User response:

Verify the DSMI_LOG value and access permission. On the AS/400 platform,
verify the value specified for ERRORLOGNAME in the API options file.

------------------------------------------------------------------------
ANS0206E

The log file cannot be written to.



Explanation:

There was an error writing to the log file.

System action:

The system returns to the calling procedure.

User response:

Verify the DSMI_LOG value and access permission. on the AS/400 platform,
verify the value specified for ERRORLOGNAME in the API options file.

------------------------------------------------------------------------
ANS0207E

The log file name was not specified.



Explanation:

The system is unable to open the error log file.

System action:

The system returns to the calling procedure.

User response:

Verify the DSMI_LOG value and access permission. On the AS/400 platform,
verify the value specified for ERRORLOGNAME in the API options file.

------------------------------------------------------------------------
ANS0208E

The TCP/IP WINSOCK.DLL file cannot be found.



Explanation:

The TCP/IP WINSOCK.DLL file cannot be found.

System action:

Processing stopped.

User response:

Verify your TCP/IP installation.

------------------------------------------------------------------------
ANS0209E

An error occurred while loading a library.



Explanation:

An error occurred while loading a library. The TCP/IP DLL load failed.

System action:

Processing stopped.

User response:

Verify your TCP/IP installation.

------------------------------------------------------------------------
ANS0210E

The TCP/IP load function failed.



Explanation:

An error occurred while locating a function. The TCP/IP load function
failed.

System action:

Processing stopped.

User response:

Verify your TCP/IP installation.

------------------------------------------------------------------------
ANS0211E

The object name pointer is NULL.



Explanation:

There is no value provided for the object name pointer.

System action:

The system returns to the calling procedure.

User response:

Provide an address for the dsmObjName structure.

------------------------------------------------------------------------
ANS0212E

The data block pointer is NULL.



Explanation:

There is no value provided for the data block pointer.

System action:

The system returns to the calling procedure.

User response:

Provide an address for the DataBlk structure.

------------------------------------------------------------------------
ANS0213E

The object attribute pointer is NULL.



Explanation:

There is no value provided for the object attribute pointer.

System action:

The system returns to the calling procedure.

User response:

Provide an address for the ObjAttr structure.

------------------------------------------------------------------------
ANS0214E

There is no server session information.



Explanation:

The server did not respond with the session information.

System action:

The system returns to the calling procedure.

User response:

Verify the server status.

------------------------------------------------------------------------
ANS0215E

There is no server policy information.



Explanation:

The server did not respond with the policy information.

System action:

The system returns to the calling procedure.

User response:

Verify the server policy definitions.

------------------------------------------------------------------------
ANS0216E

The dataBlk bufferLen value is zero.



Explanation:

The value for the dataBlk bufferLen is zero.

System action:

The system returns to the calling procedure.

User response:

Provide a non-zero value for the bufferLen.

------------------------------------------------------------------------
ANS0217E

The dataBlk bufferPtr is NULL.



Explanation:

There is no value provided for the dataBlk bufferPtr.

System action:

The system returns to the calling procedure.

User response:

Provide an address for the bufferPtr.

------------------------------------------------------------------------
ANS0218E

The objType is invalid.



Explanation:

The value for the objType is invalid.

System action:

The system returns to the calling procedure.

User response:

The value for dsmObjName.objType must be:

   DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for Backup, or
   DSM_OBJ_FILE for Archive.

------------------------------------------------------------------------
ANS0219E

The dsmEndTxn vote is invalid.



Explanation:

The dsmEndTxn vote is invalid.

System action:

The system returns to the calling procedure.

User response:

The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.

------------------------------------------------------------------------
ANS0220E

An invalid option was found during option parsing.



Explanation:

An invalid option was found.

System action:

The system returns to the calling procedure.

User response:

Verify the options in dsm.opt, dsm.sys, and the options string. Check
the error log for more details about the error. on the AS/400 platform,
verify the options in *LIB/QOPTIBM Spectrum Protect(APIOPT).

------------------------------------------------------------------------
ANS0221E

There was an error in the IBM Spectrum Protect API internals.



Explanation:

The system encountered an error in the API internals.

System action:

The system returns to the calling procedure.

User response:

Shut down the process and retry the operation. Verify that any previous
dsmInit calls were cleaned up and terminated by a dsmTerminate call. If
the problem continues, contact your system administrator or service
representative.

------------------------------------------------------------------------
ANS0222E

The repository type is invalid.



Explanation:

The repository type is invalid.

System action:

The system returns to the calling procedure.

User response:

For dsmDeleteFS the repository must be one of the following:

*  DSM_ARCHIVE_REP

*  DSM_BACKUP_REP

*  DSM_REPOS_ALL.

------------------------------------------------------------------------
ANS0223E

Filespace name should start with the directory delimiter.



Explanation:

The filespace name is invalid.

System action:

The system returns to the calling procedure.

User response:

Filespace name should start with the directory delimiter.

------------------------------------------------------------------------
ANS0224E

The object name is either an empty string or has no leading delimiter.



Explanation:

The object name is invalid because of an empty string or there is no
leading delimiter.

System action:

The system returns to the calling procedure.

User response:

Verify the format of the dsmObjName full path.

------------------------------------------------------------------------
ANS0225E

Low level qualifier of the object name should start with the directory
delimiter.



Explanation:

The low level qualifier for the object name is invalid.

System action:

The system returns to the calling procedure.

User response:

Start the low level qualifier of the object name with the directory
delimiter.

------------------------------------------------------------------------
ANS0226E

The object owner is invalid.



Explanation:

The object owner must be either the root user, or the object owner must
be the same as the session owner.

System action:

The system returns to the calling procedure.

User response:

Verify the session owner and object owner.

------------------------------------------------------------------------
ANS0227E

The dsmBindMC sendType is invalid.



Explanation:

The dsmBindMC 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

------------------------------------------------------------------------
ANS0228E

The dsmSendObj sendType is invalid.



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

------------------------------------------------------------------------
ANS0229E

The dsmDeleteObj delType is invalid.



Explanation:

The dsmDeleteObj delType is invalid.

System action:

The system returns to the calling procedure.

User response:

The delType must be dtBackup or dtArchive.

------------------------------------------------------------------------
ANS0230E

The query Backup objState is invalid.



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

------------------------------------------------------------------------
ANS0231E

The management class name was not found.



Explanation:

A query or send operation is unable to find the management class name.

System action:

The system returns to the calling procedure.

User response:

Verify the management class name.

------------------------------------------------------------------------
ANS0232E

The drive letter is not an alphabetic character.



Explanation:

The drive letter is not an alphabetic character. This return code is
valid on Microsoft Windows only.

System action:

The system returns to the calling procedure.

User response:

Verify that the drive designation is an alphabetic character. The
referenced field is dsmDosFSAttrib.driveLetter.

------------------------------------------------------------------------
ANS0233E

The Register Filespace name is NULL.



Explanation:

There is no value provided for the Register Filespace name.

System action:

The system returns to the calling procedure.

User response:

Provide a filespace name on dsmRegisterFS.

------------------------------------------------------------------------
ANS0234E

The new password value is NULL or blank.



Explanation:

There is no value provided for new password.

System action:

The system returns to the calling procedure.

User response:

Provide a new password on dsmChangePW.

------------------------------------------------------------------------
ANS0235E

The old password value is NULL or blank.



Explanation:

There is no value provided for old password.

System action:

The system returns to the calling procedure.

User response:

Provide an old password on dsmChangePW.

------------------------------------------------------------------------
ANS0236E

On dsmInit, the owner is not allowed to establish a session when
PASSWORDACCESS=generate.



Explanation:

PASSWORDACCESS=GENERATE establishes a session with the current login
user as the owner. The application should set clientOwnerNameP to NULL
when PASSWORDACCESS=GENERATE is in effect.

System action:

The system returns to the calling procedure. Whether the application can
continue processing depends on how the application handles the error.

User response:

This message applies to applications that utilize the IBM Spectrum
Protect API, and is intended primarily for the vendor of the application
for which the message is issued. Depending on the application, this
could be a configuration issue.

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.

------------------------------------------------------------------------
ANS0237E

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



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.

------------------------------------------------------------------------
ANS0238E

The sequence of calls is invalid.



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 Spectrum Protect API.

*  A bug in the IBM Spectrum Protect server.

*  A bug in the application (IBM or third party) that uses the IBM
   Spectrum 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 Spectrum Protect server activity log file,
   client side dsierror.log log file, and log files that are specific to
   the problem application.

*  Search the IBM support pages for APARs that match the problem. The
   support site is at IBM Spectrum Protect Support Portal
   (https://www.ibm.com/mysupport/s/topic/0TO50000000IQWvGAO/spectrum-protect)

*  If the API application is developed by a third party (not IBM),
   search that third party's support pages for known issues that match
   the problem.

If none of the above actions resolve the problem, report the problem to
the vendor of the application that uses the IBM Spectrum Protect API.

A developer of an application that uses the IBM Spectrum Protect API
must investigate the reason for the problem, including reviewing the IBM
Spectrum Protect API state diagram. The IBM Spectrum Protect API state
diagram is in the product documentation at IBM Spectrum Protect product
documentation (https://www.ibm.com/docs/en/spectrum-protect/8.1.13)

------------------------------------------------------------------------
ANS0239E

On dsmSendObj, wildcards are not allowed for the objName.



Explanation:

On dsmSendObj, wildcards are not allowed for the objName.

System action:

The system returns to the calling procedure.

User response:

Provide a fs, hl, and ll on the dsmObjName.

------------------------------------------------------------------------
ANS0240E

The filespace to delete/set access cannot be found.



Explanation:

The filespace to delete cannot be found.

System action:

The system returns to the calling procedure.

User response:

Verify the filespace name.

------------------------------------------------------------------------
ANS0241E

On dsmSendObj, dsmDeleteObj, or dsmUpdateFS the filespace is not
registered.



Explanation:

On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not
registered.

System action:

The system returns to the calling procedure.

User response:

Verify the filespace name.

------------------------------------------------------------------------
ANS0242W

On dsmRegisterFS the filespace is already registered.



Explanation:

On dsmRegisterFS the filespace is already registered.

System action:

The system returns to the calling procedure.

User response:

Verify the filespace name.

------------------------------------------------------------------------
ANS0243E

On dsmBeginGetData the objID is NULL.



Explanation:

On dsmBeginGetData, the objID is NULL.

System action:

The system returns to the calling procedure.

User response:

Verify the following:

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

------------------------------------------------------------------------
ANS0244E

On dsmInit, the caller API version is different than the IBM Spectrum
Protect library version.



Explanation:

On dsmInit, the caller API version is later than the IBM Spectrum
Protect library version.

System action:

The system returns to the calling procedure.

User response:

Install the latest IBM Spectrum Protect API library.

------------------------------------------------------------------------
ANS0245E

The caller's structure version is different than the IBM Spectrum
Protect library version.



Explanation:

The caller's structure version is different than the IBM Spectrum
Protect library version.

System action:

The system returns to the calling procedure.

User response:

Ensure that the stVersion field is set with the value in the header
file. Recompile the application with the latest header files.

------------------------------------------------------------------------
ANS0246E

Issue dsmEndTxn and then begin a new transaction session.



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:

Issue dsmEndTxn and start a new transaction session.

------------------------------------------------------------------------
ANS0247E

The backup or archive object is excluded from processing.



Explanation:

The backup or archive object is excluded from processing.

System action:

The system returns to the calling procedure.

User response:

Verify the objName and Exclude lists.

------------------------------------------------------------------------
ANS0248E

The backup object does not have a copy group.



Explanation:

The backup object does not have a copy group.

System action:

The system returns to the calling procedure.

User response:

Verify server policy definitions.

------------------------------------------------------------------------
ANS0249E

The archive object does not have a copy group.



Explanation:

The archive object does not have a copy group.

System action:

The system returns to the calling procedure.

User response:

Verify server policy definitions.

------------------------------------------------------------------------
ANS0250E

Memory used by the IBM Spectrum Protect API has been corrupted.



Explanation:

Memory used by the IBM Spectrum Protect API has been corrupted.

System action:

The system returns to the calling procedure.

User response:

Retry the operation. If the problem continues, contact your system
administrator or service representative.

------------------------------------------------------------------------
ANS0251E

The sendObj Archive description is too long.



Explanation:

The sendObj Archive description is too long.

System action:

The system returns to the calling procedure.

User response:

The sndArchiveData.descr string must be less than or equal to
DSM_MAX_DESCR_LENGTH.

------------------------------------------------------------------------
ANS0252E

The sendObj ObjAttr.objInfo is too long.



Explanation:

The sendObj ObjAttr.objInfo is too long.

System action:

The system returns to the calling procedure.

User response:

The objInfo field must be less than or equal to DSM_MAX_OBJINFO_LENGTH.

------------------------------------------------------------------------
ANS0253E

The sendObj dsmObjName.hl is too long.



Explanation:

The sendObj dsmObjName.hl is too long.

System action:

The system returns to the calling procedure.

User response:

The hl field must be less than or equal to DSM_MAX_HL_LENGTH.

------------------------------------------------------------------------
ANS0254E

The password, or encryptionPassword string provided is too long.



Explanation:

The value provided for password or encryptionPassword is too long.

System action:

The system returns to the calling procedure.

User response:

The password or encrypionPassword field must be less than
DSM_MAX_VERIFIER_LENGTH.

------------------------------------------------------------------------
ANS0255E

The sendObj dsmObjName.fs is too long.



Explanation:

The sendObj dsmObjName.fs is too long.

System action:

The system returns to the calling procedure.

User response:

The fs field must be less than or equal to DSM_MAX_FS_LENGTH.

------------------------------------------------------------------------
ANS0256E

The sendObj dsmObjName.ll is too long.



Explanation:

The sendObj dsmObjName.ll is too long.

System action:

The system returns to the calling procedure.

User response:

The ll field must be less than or equal to DSM_MAX_LL_LENGTH.

------------------------------------------------------------------------
ANS0257E

On RegisterFS or UpdateFS the fsAttr's fsInfo is too long.



Explanation:

On RegisterFS or UpdateFS the fsAttr's fsInfo is too long.

System action:

The system returns to the calling procedure.

User response:

The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH.

------------------------------------------------------------------------
ANS0258I

On dsmGetNextQObj or dsmGetData there is more available data.



Explanation:

On dsmGetNextQObj or dsmGetData there is more available data.

System action:

The system returns to the calling procedure.

User response:

Call the function again.

------------------------------------------------------------------------
ANS0259E

The dataBlk buffer is too small for the query response.



Explanation:

The dataBlk buffer is too small for the query response.

System action:

The system returns to the calling procedure.

User response:

On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as
the query response structure.

------------------------------------------------------------------------
ANS0260E

An invalid option keyword was found during option parsing.



Explanation:

An invalid option keyword was found in the dsmInit configuration file,
the option string, dsm.sys, or dsm.opt.

System action:

The system returns to the calling procedure.

User response:

Correct the spelling of the option keywords. Verify that the dsmInit
configuration file only has a subset of the dsm.sys options. Check the
error log for more details about the error.

------------------------------------------------------------------------
ANS0261E

The configuration file specified on dsmInit cannot be opened.



Explanation:

The configuration file specified on dsmInit cannot be opened.

System action:

The system returns to the calling procedure.

User response:

Verify the file name.

------------------------------------------------------------------------
ANS0262E

The Include/Exclude definition file was not found.



Explanation:

The Include/Exclude definition file was not found.

System action:

The system returns to the calling procedure.

User response:

Verify the file name on the Inclexcl option.

------------------------------------------------------------------------
ANS0263E

Either the dsm.sys file was not found, or the Inclexcl file specified in
dsm.sys was not found.



Explanation:

Either the dsm.sys file was not found, or the Inclexcl file specified in
dsm.sys was not found.

System action:

The system returns to the calling procedure.

User response:

The dsm.sys file must be in the directory referenced by the environment
variable DSMI_DIR. Verify the file name on the Inclexcl option in the
dsm.sys file.

------------------------------------------------------------------------
ANS0264E

Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.



Explanation:

Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.

System action:

The system returns to the calling procedure.

User response:

Run this program as a root user.

------------------------------------------------------------------------
ANS0265E

You must issue dsmBindMC before dsmSendObj.



Explanation:

You must issue dsmBindMC before dsmSendObj.

System action:

The system returns to the calling procedure.

User response:

Modify your program.

------------------------------------------------------------------------
ANS0266I

The dsmEndTxn vote is ABORT, so check the reason field.



Explanation:

After a dsmEndTxn call, the transaction is aborted by either the server
or client with a DSM_VOTE_ABORT and the reason is returned.

System action:

The system returns to the calling procedure.

User response:

Check the reason field for the code which explains why the transaction
has been aborted.

------------------------------------------------------------------------
ANS0267E

Invalid command line option/value: 'option'



Explanation:

The option is not valid on this command line.

System action:

Processing stops

User response:

Verify that the option and value are not misspelled and are valid with
the current command.

------------------------------------------------------------------------
ANS0268E

Server problem: Destination not defined.



Explanation:

Server problem: Destination not defined.

System action:

Processing stopped.

User response:

Have your service representative check the error log.

------------------------------------------------------------------------
ANS0270S

The data buffer overflowed.



Explanation:

The data buffer overflowed. This is a programming failure and the client
program ends.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, contact your system
administrator.

------------------------------------------------------------------------
ANS0271E

No more files can be restored or retrieved since the destination
directory is full.



Explanation:

No more files can be restored or retrieved since the destination
directory is full.

System action:

Processing stopped.

User response:

Free up disk space, or restore or retrieve the file to another disk.

------------------------------------------------------------------------
ANS0272I

The operation is finished.



Explanation:

The operation is finished.

System action:

The system returns to the calling procedure.

User response:

Proceed with next function call.

------------------------------------------------------------------------
ANS0273E

The dsmtca execution/owner permissions are invalid.



Explanation:

The dsmtca execution/owner permissions are invalid.

System action:

Processing stopped.

User response:

Have your system administrator check the installation instructions for
the client to ensure that the dsmtca permissions are set correctly.

------------------------------------------------------------------------
ANS0274S

Process killed.



Explanation:

Processing stopped. This is a programming failure and the client program
ends.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, contact your system
administrator.

------------------------------------------------------------------------
ANS0275S

The dsmtca would block the operation.



Explanation:

The dsmtca blocks the operation. This is a programming failure and the
client program ends.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, contact your system
administrator.

------------------------------------------------------------------------
ANS0276S

The area for the include/exclude pattern is too small.



Explanation:

The area for the include/exclude pattern is too small. This is a
programming failure and the client program ends.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, contact your system
administrator.

------------------------------------------------------------------------
ANS0277S

There is no closing bracket in the pattern.



Explanation:

There is no closing bracket in the pattern. This is a programming
failure and the client program ends.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, contact your system
administrator.

------------------------------------------------------------------------
ANS0278S

The transaction will be aborted.



Explanation:

The server encountered an error and will abort the transaction.

System action:

The transaction will be aborted. The reason code is passed on the
dsmEndTxn call.

User response:

Issue the dsmEndTxn with a vote of DSM_VOTE_COMMIT and examine the
reason code.

------------------------------------------------------------------------
ANS0279I

A file was skipped during a restore operation because the file is off
line and the application has chosen not to wait for a tape mount.



Explanation:

A file was skipped during a restore operation because the file is off
line and the application has chosen not to wait for a tape mount.

System action:

File skipped.

User response:

Verify the application sets the mountWait value correctly on
dsmBeginGetData.

------------------------------------------------------------------------
ANS0280E

Unable to find the dsmtca module.



Explanation:

IBM Spectrum Protect was unable to find the dsmtca module in the
specified directory.

System action:

Processing ends.

User response:

Make sure the dsmtca module is in the directory specified by DSMI_DIR.

------------------------------------------------------------------------
ANS0282E

Password file is not available.



Explanation:

The file containing the stored password for the specified server-name is
unavailable.

System action:

Processing ends.

User response:

The root user must set and store a new password.

------------------------------------------------------------------------
ANS0283E

High level qualifier of the object name should start with the directory
delimiter.



Explanation:

The high level qualifier for the object name is invalid.

System action:

The system returns to the calling procedure.

User response:

High level qualifier of the object name should start with the directory
delimiter.

------------------------------------------------------------------------
ANS0284E

The number of objects on dsmBeginGetData exceeds DSM_MAX_GET_OBJ |
DSM_MAX_PARTIAL_GET_OBJ.



Explanation:

The number of objects (numObjId) specified on the dsmBeginGetData call
exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ.

System action:

The system returns to the calling procedure.

User response:

Check the number of objects before calling dsmBeginGetData. If it is
greater than DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ, then issue
multiple Get call sequences.

------------------------------------------------------------------------
ANS0285E

The update action is invalid.



Explanation:

The dsmUpdateFS or dsmUpdateObj action is invalid.

System action:

The system returns to the calling procedure.

User response:

Correct the action value. Valid values are defined in dsmapitd.h and
documented in our Using the API book.

------------------------------------------------------------------------
ANS0286E

The key file is missing.



Explanation:

The key file for Data Protection for Oracle cannot be found.

System action:

The system returns to the calling procedure.

User response:

Ensure that you have ordered the Data Protection for Oracle, and install
the key file.

------------------------------------------------------------------------
ANS0287E

The key file content is invalid.



Explanation:

The key file content for Data Protection for Oracle is invalid.

System action:

The system returns to the calling procedure.

User response:

Ensure that you have ordered the Data Protection for Oracle, and install
the key file.

------------------------------------------------------------------------
ANS0296I

Encryption key passwords are not the same. Please try again...



Explanation:

Encryption key passwords do not match.

System action:

You are prompted for the encryption key password.

User response:

Enter the correct encryption key password.

------------------------------------------------------------------------
ANS0297E

Error opening specified file.



Explanation:

The specified file could not be located or opened.

System action:

Attempts to open file failed.

User response:

Make sure the file exists.

------------------------------------------------------------------------
ANS0298E

Session Rejected: The specified user id is currently locked



Explanation:

The user id you specified is currently locked on the server.

System action:

Session was not started.

User response:

Check with your system administrator to find out why your user id is
locked.

------------------------------------------------------------------------
ANS0299E

Scheduler cannot be started manually because the value of
MANAGEDSERVICES option is SCHEDULE.



Explanation:

if MANAGEDSERVICES SCHEDULE is indicated in the option file, the IBM
Spectrum Protect scheduler cannot be started in the traditional manner.

System action:

Scheduler stopped.

User response:

If you are not going to use dsmcad to manage the schedule anymore, stop
dsmcad and remove MANAGEDSERVICES option from the option file.

------------------------------------------------------------------------
ANS0302I

Successfully done.



Explanation:

The operation successfully completed.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS0304E

The password is too short.



Explanation:

The new password does not have enough characters.

System action:

The password is not updated on the server.

User response:

Choose a different password. Contact your IBM Spectrum Protect
administrator to lean the password requirements.

------------------------------------------------------------------------
ANS0305E

It is too soon after the previous update to change the password.



Explanation:

The password cannot be changed since not enough time has elapsed since
the last password update.

System action:

The password is not updated on the server.

User response:

Try to change your password again later.

------------------------------------------------------------------------
ANS0306E

The password was previously used.



Explanation:

The new password that you entered was previously used.

System action:

The password is not updated on the server.

User response:

Choose a different password.

------------------------------------------------------------------------
ANS0307E

The password does not meet the requirements.



Explanation:

The new password that you entered does not meet the requirements, such
as the number of special characters or digits.

System action:

The password is not updated on the server.

User response:

Choose a different password. Contact your IBM Spectrum Protect
administrator to learn the password requirements.

------------------------------------------------------------------------
ANS0308E

Remote operation failed to start on obj-name. Status: status reason:
reason



Explanation:

The request to start a remote operation has failed for the indicated
node and file space. The status and the reason for the failure are
shown.

System action:

Processing ends.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0309E

Remote operation failed to start on obj-name. Status: status



Explanation:

The request to start a remote operation has failed for the indicated
node and file space. The status of the failure is shown.

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0311E

The tsmBuffHandle is invalid, or the value of dataPtr is invalid.



Explanation:

An invalid value for a handle or dataPtr has been passed into the API.

System action:

The system returns to the calling procedure.

User response:

There is a problem with the calling application. Verify the values of
the tsmBuffHandle and dataptr passed to the API.

------------------------------------------------------------------------
ANS0312E

The number of bytes copied into the tsmBuffer is larger than the allowed
value.



Explanation:

An invalid number of bytes was copied to a tsmBuffer.

System action:

The system returns to the calling procedure.

User response:

There is a problem with the calling application. Verify the number of
bytes copied into the tsmBuffer.

------------------------------------------------------------------------
ANS0313E

dsmTerminate cannot finish because the application is holding on to 1 or
more tsmBuffers.



Explanation:

An application is trying to terminate a session, but is still holding
some tsmBuffers.

System action:

The system returns to the calling procedure.

User response:

The application must return all buffers for this session by calling
tsmReleaseBuffer, and then issue dsmTerminate.

------------------------------------------------------------------------
ANS0314E

An internal error occurred in the tsmBuffer array.



Explanation:

An internal API buffer array error occurred.

System action:

The system returns to the calling procedure.

User response:

Try the operation again. If the problem continues, contact your system
administrator or service representative.

------------------------------------------------------------------------
ANS0315E

Unable to open message text file.



Explanation:

The system is unable to open the message txt file (dscenu.txt or
dsmclientV3.cat for AIX). On the AS/400 platform this file is
QANSAPI/QAANSENU(TXT).

System action:

The system returns to the calling procedure.

User response:

Verify that the dscenu.txt file is in the directory pointed to by
DSMI_DIR. For AIX, verify that the dsmclientV3.cat file has a symbolic
link to /usr/lib/nls/msg/<locale>/dsmclientV3.cat .

------------------------------------------------------------------------
ANS0316E

Unable to use message text file.



Explanation:

The system is unable to use the message text file (dscenu.txt or
dsmclientV3.cat for AIX) because of an invalid header. On the AS/400
platform this file is QANSAPI/QAANSENU(TXT).

System action:

The system returns to the calling procedure.

User response:

Install the message text file again.

------------------------------------------------------------------------
ANS0317E

Unable to use message text file.



Explanation:

The system is unable to use the message txt file (dscenu.txt or
dsmclientV3.cat for AIX) because of an invalid control record. On the
AS/400 platform this file is QANSAPI/QAANSENU(TXT).

System action:

The system returns to the calling procedure.

User response:

Install the message text file again.

------------------------------------------------------------------------
ANS0318E

Invalid value for DATEFORMAT specified.



Explanation:

An invalid value is specified for DATEFORMAT.

System action:

The system returns to the calling procedure.

User response:

Specify a valid value.

------------------------------------------------------------------------
ANS0319E

Invalid value for TIMEFORMAT specified.



Explanation:

An invalid value is specified for TIMEFORMAT.

System action:

The system returns to the calling procedure.

User response:

Specify a valid value.

------------------------------------------------------------------------
ANS0320E

Invalid value for NUMBERFORMAT specified.



Explanation:

An invalid value is specified for NUMBERFORMAT.

System action:

The system returns to the calling procedure.

User response:

Specify a valid value.

------------------------------------------------------------------------
ANS0321E

msg parameter for dsmRCMsg is a NULL pointer.



Explanation:

The message parameter for dsmRCMsg is a NULL pointer.

System action:

The system returns to the calling procedure.

User response:

Allocate enough space for the message parameter.

------------------------------------------------------------------------
ANS0322E

no text available for this return code.



Explanation:

The dsmRC parameter for dsmRCMsg is an unsupported return code.

System action:

The system returns to the calling procedure.

User response:

Specify a valid value.

------------------------------------------------------------------------
ANS0323E

partialObjOffset value for partial object retrieve is invalid.



Explanation:

The partialObjOffset value for partial object retrieve is invalid.

System action:

The system returns to the calling procedure.

User response:

Specify a valid value.

------------------------------------------------------------------------
ANS0324E

partialObjLength value for partial object retrieve is invalid.



Explanation:

partialObjLength value for partial object retrieve is invalid.

System action:

The system returns to the calling procedure.

User response:

Specify a valid value.

------------------------------------------------------------------------
ANS0325E

Partial Object Retrieve is not supported on this server.



Explanation:

The IBM Spectrum Protect server specified by the user does not support
partial object retrieve.

System action:

The system returns to the calling procedure.

User response:

Specify a IBM Spectrum Protect server which supports the partial object
retrieve function.

------------------------------------------------------------------------
ANS0326E

This node has exceeded its maximum number of mount points.



Explanation:

Either no tape or sequential disk mount points are permitted for this
operation, or the maximum number of mount points allowed are already in
use. The operation can not be completed. The IBM Spectrum Protect
administrator defines the maximum number of mount points with the
MAXNUMMP property of your node definition.

System action:

The object is skipped

User response:

If you are performing any other operations that might be using mount
points, wait until those operations are complete, then try the failed
operation again. Otherwise contact your IBM Spectrum Protect
administrator for further assistance

------------------------------------------------------------------------
ANS0327E

A duplicate object was found, operation cannot complete.



Explanation:

A duplicate object was found, operation cannot complete.

System action:

The requested operation failed.

User response:

Try the operation with a different file specification.

------------------------------------------------------------------------
ANS0328E

The specified objects failed the merge test.



Explanation:

The specified objects failed the merge test, operation cannot complete.

System action:

The requested operation failed.

User response:

See documentation for the merge test parameters.

------------------------------------------------------------------------
ANS0330E

The dsmSetAccess access Type is invalid.



Explanation:

The dsmSetAccess accessType is invalid.

System action:

The system returns to the calling procedure.

User response:

The accessType must be one of the following:

   atBackup
   atArchive

------------------------------------------------------------------------
ANS0331E

No files have been previously backed up for this filename/filespace.



Explanation:

You tried to set access to files when no files for the specified
filename, drive or file system were previously backed up.

System action:

Processing stopped.

User response:

Ensure that the correct drive or file system was specified and that
files are backed up for you to set access.

------------------------------------------------------------------------
ANS0332E

No files have been previously archived for this filename/filespace.



Explanation:

You tried to set access to files when no files for the specified
filename, drive or file system were previously archived.

System action:

Processing stopped.

User response:

Ensure that the correct drive or file system was specified and that
files are archived for you to set access.

------------------------------------------------------------------------
ANS0333E

Unknown Remote Mover type



Explanation:

The specified Remote Mover type is unknown.

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0334E

An Operation for the requested node and file space is already in
progress.



Explanation:

A request has been made to use a data mover to perform an operation for
the indicated node and file space. Since an operation for this node and
file space is already in progress, the new operation cannot be
performed.

System action:

Current operation has ended.

User response:

Retry the operation at a later time.

------------------------------------------------------------------------
ANS0335E

System resource in use



Explanation:

A required resource is in use by another command or process.

System action:

Current operation has ended.

User response:

Retry the operation at a later time.

------------------------------------------------------------------------
ANS0336E

Server plugin communication error



Explanation:

Communication between a server plugin module and a NAS filer failed.

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0337E

Server plugin detected unsupported NAS filer operating system.



Explanation:

A plugin module detected that a NAS filer is running an unsupported
operating system or operating system level.

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0338E

An invalid operation was attempted on a node



Explanation:

The operation is not valid.

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0339E

The specified target storage pool is not defined.



Explanation:

The storage pool is not defined.

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0340E

A target storage pool does not have the correct data format for the
given node type.



Explanation:

none

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0341E

No associated data mover is defined for the given node.



Explanation:

none

System action:

Current operation has ended.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS0342E

The CRC received from the Server does not match the CRC calculated by
the client.



Explanation:

The server sent a CRC for a buffer. The client calculated a CRC for the
same buffer. These did not match. The mismatch indicates a communication
failure.

System action:

In some cases, the client can indicate the failure to the server and
retry the operation.

User response:

Check the trace log for additional information and retry the operation.
If the problem persists, contact your system administrator.

------------------------------------------------------------------------
ANS0343E

An invalid operation was attempted on a group leader or group member.



Explanation:

An invalid operation was attempted on a logical group.

System action:

The current operation stops.

User response:

Retry a valid operation.

------------------------------------------------------------------------
ANS0344E

Cannot Send data with a zero byte sizeEstimate.



Explanation:

You cannot send data for an object with size estimate = 0.

System action:

The system returns to the calling procedure.

User response:

Set size estimate greater than 0 in dsmSendObj.

------------------------------------------------------------------------
ANS0345E

Remote disk not defined.



Explanation:

An operation was attempted on a remote disk that is not defined.

System action:

The current operation stops.

User response:

Define the proper remote disk.

------------------------------------------------------------------------
ANS0346E

Input destination does not match expected destination.



Explanation:

Input destination does not match expected destination.

System action:

The current operation stops.

User response:

Retry operation with proper destination.

------------------------------------------------------------------------
ANS0347E

Data mover is not available.



Explanation:

Data mover is not available.

System action:

The current operation stops.

User response:

Retry operation with a proper Data mover.

------------------------------------------------------------------------
ANS0348E

Operation failed because the copy continue option was set to NO.



Explanation:

Operation failed because the copy continue option was set to NO.

System action:

The current operation stops.

User response:

This abort code indicates that a store operation, like backup or archive
failed because the copy continue option was set to NO. The sysadmin will
need to resolve the problem on the server end.

------------------------------------------------------------------------
ANS0349E

Transaction failed because of a problem during a store operation.



Explanation:

Transaction failed because of a problem during a store operation. This
error is typical when the next storage pool has a different copy storage
pool list and we switch to this pool in the middle of a transaction.

System action:

Transaction is aborted.

User response:

Resend objects in separate transactions.

------------------------------------------------------------------------
ANS0350E

The current client configuration does not comply with the value of the
DATAWRITEPATH or DATAREADPATH server option for this node.



Explanation:

The values of the DATAWRITEPATH and DATAREADPATH server options specify
where the client is allowed to send data, and where data is read from.
The values for the specified node name should correspond with the client
configuration. For example, you will get this error message if
DATAWRITEPATH contains a LAN value and the client is configured to use
LAN-free protocol, or vice versa.

System action:

Processing stopped.

User response:

Check the client, server, and storage agent logs to determine why the
client was not able to send data LAN-free. Make sure the client
configuration and server options are compatible.

------------------------------------------------------------------------
ANS0351E

The node or user does not have proper authority to perform this
operation



Explanation:

The node or user does not have proper authority to perform this
operation.

System action:

The transaction is ended.

User response:

Check the authority for the specified object.

------------------------------------------------------------------------
ANS0352E

The operation is not permitted due to server licenses values.



Explanation:

The node or user is trying to perform an operation that either exceeds
license values, or is not licensed.

System action:

The session is rejected or the transaction is cancelled, ending the
current operation.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS0353E

When using useTsmBuffers, dataBlk must be NULL in calls to dsmSendObj
and dsmGetObj.



Explanation:

The value for dataBlk must be NULL when using useTsmBuffers.

System action:

The system returns to the calling procedure.

User response:

There is a problem with the calling application. Contact your
application provider

------------------------------------------------------------------------
ANS0354E

Encryption is not allowed when using useTsmBuffers.



Explanation:

useTsmBuffers does not support encryption.

System action:

The system returns to the calling procedure.

User response:

Try the operation again, without using useTsmBuffers, or disable
encryption for this operation.

------------------------------------------------------------------------
ANS0355E

This object cannot be restored/retrieved using useTsmBuffers, because it
is compressed.



Explanation:

useTsmBuffers does not support compression.

System action:

The system returns to the calling procedure.

User response:

Try the operation again, without using useTsmBuffers.

------------------------------------------------------------------------
ANS0356E

This object cannot be restored/retrieved using useTsmBuffers, because it
is encrypted.



Explanation:

useTsmBuffers does not support encryption.

System action:

The system returns to the calling procedure.

User response:

Try the operation again, without using useTsmBuffers.

------------------------------------------------------------------------
ANS0357E

When using useTsmBuffers, a restore/retrieve with partial object restore
is not allowed.



Explanation:

useTsmBuffers does not support partial object restore.

System action:

The system returns to the calling procedure.

User response:

Make sure the calling application is either using Partial object restore
or useTsmBuffers.

------------------------------------------------------------------------
ANS0358E

No encryption key was found. If you are using -encryptkey=prompt make
sure there is a value in the encryptionPasswordP field and that
bEncryptKeyEnabled is set to true.



Explanation:

There was no encryption key found in the password file, or no key was
provided by the application.

System action:

The system returns to the calling procedure.

User response:

If you are using -encryptkey=prompt, make sure there is a value in
encryptionPasswordP and that bEncryptKeyEnabled is set to true.

------------------------------------------------------------------------
ANS0359E

Conflicting encryption key options have been specified.



Explanation:

When using the ENABLEENCRYPTKEY option, the parameter bEncryptKeyEnabled
for the IBM Spectrum Protect API dsmInitExIn_t and tsmInitExIn_t
structures cannot be set to bTrue.

System action:

The system returns to the calling procedure.

User response:

Either remove the ENABLEENCRYPTKEY option from the options file, or set
the parameter bEncryptKeyEnabled to bFalse in the program using the IBM
Spectrum Protect API.

------------------------------------------------------------------------
ANS0360E

The client acceptor cannot start because the value of the
MANAGEDSERVICES option is NONE.



Explanation:

The client acceptor will not start if MANAGEDSERVICES NONE is set in the
option file. The client acceptor is designed to manage the web client or
IBM Spectrum Protect schedules. By specifying NONE, the client acceptor
will not manage any services.

System action:

The client acceptor will stop processing.

User response:

Specify either WEBCLIENT or SCHEDULER for the MANAGEDSERVICES option in
the option file then restart the client acceptor.

------------------------------------------------------------------------
ANS0361I

DIAG:



Explanation:

The message text is provided for diagnostic purposes and is meant to
provide information to IBM support in problem determination.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS0362E

There are insufficient Windows system resources to process this command.



Explanation:

This problem can occur during backup of a shared directory. The most
likely reason is the 'IRPStackSize' setting on the computer that hosts
the shared directory is too small.

System action:

The file is skipped.

User response:

Check the Windows event viewer for event ID 2011 on the computer that
hosts the shared directory. This event indicates that the configuration
parameter IRPStackSize is too small. IRPStackSize is a setting of type
DWORD located in Windows registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters.
If the IRPStackSize value is less than 20, or IRPStackSize is not
specified, then set the value to 20, restart the system, and try the
operation again. The default IRPStackSize value is 15. Attention:
Consult with your Windows system administrator before making changes to
the Windows registry or the problem persists after changing the
IRPStackSize value to 20.

------------------------------------------------------------------------
ANS0363E

The signature check of the content.spsig file failed. The retrieved
files will be removed.



Explanation:

The IBM Spectrum Protect signature file, content.spsig, was not
retrieved correctly. The file was manipulated or damaged.

System action:

Processing stops.

User response:

The content.spsig file was not found. Make sure that the data in the
Operations Center, such as the client package or Update Manager package,
is correct or download the correct version in the Operations Center.

------------------------------------------------------------------------
ANS0364W

The signature check of the content.spsig file failed.



Explanation:

The IBM Spectrum Protect signature file, content.spsig, was not
retrieved correctly. The file was changed or damaged.

System action:

Processing continues.

User response:

The content.spsig file is damaged or changed. Ensure that the data that
was retrieved is not corrupted. The data was probably damaged or
changed.

------------------------------------------------------------------------
ANS0365E

The signature check of one or more files failed. The retrieved files
will be removed.



Explanation:

One or more files were not retrieved correctly. The files might be
changed or damaged.

System action:

Processing stops.

User response:

One or more files were changed or damaged. Make sure that the data in
the Operations Center, such as the client package or Update Manager
package, is correct or download the correct version in the Operations
Center.

------------------------------------------------------------------------
ANS0366W

The signature check of one or more files failed.



Explanation:

One or more files were not retrieved correctly. The files might be
changed or damaged.

System action:

Processing continues.

User response:

One or more files were changed or damaged. Ensure that the files that
were retrieved are not corrupted.

------------------------------------------------------------------------
ANS0367E

One or more files were not found during the signature check. The
retrieved files will be removed.



Explanation:

One or more files were not retrieved.

System action:

Processing stops.

User response:

One or more files were not retrieved. Make sure that the data in the
Operations Center, such as the client package or Update Manager package,
is correct or download the correct version in the Operations Center.

------------------------------------------------------------------------
ANS0368W

One or more files were not found during the signature check.



Explanation:

One or more files were not retrieved. Important files might be missing.

System action:

Processing continues.

User response:

One or more files were damaged or changed. Ensure that the files that
were retrieved are not corrupted. The missing files could be important
or not retrieved on purpose. For example, a file might not be retrieved
because it was removed on the server.

------------------------------------------------------------------------
ANS0369E

The content.spsig file is not a IBM Spectrum Protect signature file. The
retrieved files will be removed.



Explanation:

A content.spsig file was found, but it is not a IBM Spectrum Protect
signature file. The content of the retrieve could not be verified.

System action:

Processing stops.

User response:

If a content.spsig file is found during retrieve, the client will try to
identify this file as a signature file. If the file is not a IBM
Spectrum Protect signature file, the client is not able to verify the
files. Make sure that the data in the Operations Center, such as the
client package or Update Manager package, is correct or download the
correct version in the Operations Center.

------------------------------------------------------------------------
ANS0370W

The content.spsig file is not a IBM Spectrum Protect signature file.



Explanation:

A content.spsig file was found, but it is not a IBM Spectrum Protect
signature file. The content of the retrieve could not be verified. If a
content.spsig file is found during retrieve the client will try to
identify this file as signature file. If the file is not a IBM Spectrum
Protect signature file, the client is not able to verify the data.

System action:

Processing continues.

User response:

No user action is required.

------------------------------------------------------------------------
ANS0371E

The content.spsig file was not found. A signature check cannot be
completed. All retrieved files will be removed.



Explanation:

The IBM Spectrum Protect signature file, content.spsig, was not found. A
signature check is not possible. It is not possible to check whether the
files that were retrieved are damaged or changed.

System action:

Processing stops.

User response:

The content.spsig file was not found. Make sure that the data in the
Operations Center, such as the client package or Update Manager package,
is correct or download the correct version in the Operations Center.

------------------------------------------------------------------------
ANS0372E

More than one content.spsig file was found. A signature check cannot be
completed. All retrieved files will be removed.



Explanation:

More than one IBM Spectrum Protect signature file, content.spsig, was
found. A signature check is not possible. It is not possible to check
whether the files that were retrieved are damaged or changed.

System action:

Processing stops.

User response:

More than one content.spsig file was found. Make sure that the data in
the Operations Center, such as the client package or Update Manager
package, is correct or download the correct version in the Operations
Center.

------------------------------------------------------------------------
ANS373I

The SAN Policy of the system is set to 'san_policy_value'.



Explanation:

The VMware Virtual Disk Development Kit used to open, close, read, and
write VMware VMDKs requires the specified Windows SAN Policy setting for
the datamover hardware and transport type in use.

System action:

The Windows SAN Policy of the system is configured and the current
operation continues.

User response:

When a system is set to Offline All, you need to manually set new disks
to Online.

------------------------------------------------------------------------
ANS0374E

The CAD service is not running on the local node.



Explanation:

The CAD service is not running.

System action:

The operation cannot continue without a connection to the CAD service.

User response:

Make sure that the CAD service is running and configured correctly.

------------------------------------------------------------------------
ANS0375E

The fileSpace parameter is either not defined or too long.



Explanation:

The fileSpace parameter cannot be empty and cannot be longer than 1024
characters.

System action:

The operation cannot continue.

User response:

Make sure that the fileSpace parameter is used correctly.

------------------------------------------------------------------------
ANS0376E

The value for the codePage parameter is incorrect.



Explanation:

The codePage parameter can only be "MBCS" or "UCS2".

System action:

The operation cannot continue.

User response:

Make sure that the codePage parameter is used correctly.

------------------------------------------------------------------------
ANS0377E

The value for the path parameter is incorrect.



Explanation:

The path parameter cannot be longer than 6000 characters.

System action:

The operation cannot continue.

User response:

Make sure that the path parameter is used correctly.

------------------------------------------------------------------------
ANS0378E

The value for the name parameter is incorrect.



Explanation:

The name parameter cannot be longer than 512 characters and cannot start
with the directory delimiter.

System action:

The operation cannot continue.

User response:

Make sure that the name parameter is used correctly.

------------------------------------------------------------------------
ANS0379E

The value for the status parameter is incorrect.



Explanation:

The status parameter can only be "ALL", "ACTIVE" or "INACTIVE".

System action:

The operation cannot continue.

User response:

Make sure that the status parameter is used correctly.

------------------------------------------------------------------------
ANS0380E

The value for the type parameter is incorrect.



Explanation:

The type parameter can only be "FILE" or "DIR".

System action:

The operation cannot continue.

User response:

Make sure that the type parameter is used correctly.

------------------------------------------------------------------------
ANS0381E

The value for either the startDateTime or endDateTime parameter is
incorrect.



Explanation:

The startDateTime and endDateTime parameters can only be a valid JSON
date time format.

System action:

The operation cannot continue.

User response:

Make sure that the startDateTime and endDateTime parameters are used
correctly.

------------------------------------------------------------------------
ANS0382E

The rest call JSON data is missing values.



Explanation:

The JSON data for the rest call are incorrect and cannot be processed.

System action:

The operation cannot continue.

User response:

Make sure that the JSON for the rest call is correct and has all needed
values.

------------------------------------------------------------------------
ANS0400E

License file could not be opened.



Explanation:

The license file was not found, or could not be opened because of
permissions or the file is corrupted.

System action:

The system returns to the calling procedure.

User response:

Check permissions on file. See if the license file is in the correct
place.

------------------------------------------------------------------------
ANS0401E

Read failure on the license file.



Explanation:

The license file was not found, or could not be opened because of
permissions, or the file is corrupted.

System action:

The system returns to the calling procedure.

User response:

Check permissions on file. See if the license file is in the correct
place.

------------------------------------------------------------------------
ANS0402E

Write failure on the license file.



Explanation:

The license file was not found, or could not be opened because of
permissions or the file is corrupted.

System action:

The system returns to the calling procedure.

User response:

Check permissions on file. See if license file is in the correct place.

------------------------------------------------------------------------
ANS0403E

Data in the license file is not in a valid format.



Explanation:

The license file is not valid.

System action:

The system returns to the calling procedure.

User response:

User needs to obtain a new license.

------------------------------------------------------------------------
ANS0404E

The checksum in the license file does not match the licenseregistration
string.



Explanation:

The registration string is not valid.

System action:

The system returns to the calling procedure.

User response:

User needs to obtain a new license.

------------------------------------------------------------------------
ANS0405E

This is an expired try and buy license.



Explanation:

The registration string is not valid.

System action:

The system returns to the calling procedure.

User response:

User needs to obtain a new license.

------------------------------------------------------------------------
ANS0420W

Warning! Restoring inactive system state objects is not recommended.Do
you wish to continue?



Explanation:

Restoring inactive system state objects may cause system instability.
Examples of possible problems include:

*  Applications that were installed after the time the system state was
   backed up cannot function properly after restoring the inactive
   system state

*  Critical operating system updates installed after the inactive system
   state backup was made can no longer be available, or may not function
   correctly.

Restoring inactive system state objects is not recommended unless you
are certain that this is what you need to do.

System action:

If user responds with yes, the client will restore the object. If user
responds with no, the client will cancel the operation.

User response:

Reply to the prompt. If you are unsure, reply no, and consult your
system administrator or operating system vendor before proceeding
further.

------------------------------------------------------------------------
ANS0421W

Unable to synchronize the node password with the user id password
provided.



Explanation:

The node password was not updated due to the reason described in the
error message preceding this one.

System action:

The node password is not updated on the server. Next time you run the
client you will be prompted for the password again.

User response:

See the preceding error message.

------------------------------------------------------------------------
ANS0422W

The selected journal location is a network drive and might not be
accessible from the journal service. Select a location on a local drive.



Explanation:

It is not recommended to use a network device as the location where
journal databases are stored. Placing journal databases on a network
device can prevent the journal service from running.

System action:

Processing continues.

User response:

Choose a local drive where journal databases will be stored.

------------------------------------------------------------------------
ANS0423E

Directory 'filespace namepath-namefile-name' cannot be created. Path
does not exist.



Explanation:

The operating system returned a "path not found" status when IBM
Spectrum Protect attempted to create the directory needed for Automated
System Recovery (ASR). One possible reason is that a multi disk system
is restored to a single disk system.

System action:

Processing stopped.

User response:

Please verify that you are restoring to identical hardware and try
again.

------------------------------------------------------------------------
ANS0649E

Disk provider for volume volume-name does not support the snap of a snap
feature.



Explanation:

You can use the snap of a snap feature only on SVC, XIV and Storwize
systems.

System action:

Processing ends.

User response:

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

------------------------------------------------------------------------
ANS0990W

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



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
   Spectrum Protect client, and

*  the environment variable DSM_CONFIG was not set.

System action:

IBM Spectrum Protect client assumes default values for all client
options and continues processing, using the default server name and
associated options found in the dsm.sys file.

User response:

If the default system action is acceptable, you can eliminate this
message by creating an empty dsm.opt file in the installation directory.

If you have a client user options file (dsm.opt), either place it in the
installation directory or set the DSM_CONFIG environment variable to the
fully-qualified path and file name of your options file.

Review the information on configuring IBM Spectrum Protect in the IBM
Spectrum Protect client manual specific to your operating system. If the
problem persists, ask your IBM Spectrum Protect administrator for
further assistance.

------------------------------------------------------------------------
ANS0991I

IBM Spectrum Protect scheduler is listening for server requests on port
port number



Explanation:

This message indicates the port number on which the clients is listens
for server requests. If the port number in the message differs from the
default value or what you specified with the TCPCLIENTPORT option, it is
because the port was in use by a different process.

System action:

Processing continues.

User response:

Normally no further action is required. If you require the use a
specific port number, you need to configure your system or applications
so the number is avaible. Restart the IBM Spectrum Protect client and
confirm it uses the desired port.

------------------------------------------------------------------------
ANS0992E

The destination filespace or drive letter is unavailable. For more
details please see dsmerror.log.



Explanation:

The system is trying to restore or retrieve to a destination that cannot
be reached. The specified filespace name or drive letter is not valid,
or does not exist, or you are specifying a local share name that cannot
be resolved.

System action:

Objects which are part of this filespace are not processed.

User response:

Try the command again, and specify a different destination for the
object that was not processed.

------------------------------------------------------------------------
ANS0993E

The source specification "source" has invalid format.



Explanation:

The file system must be enclosed in curly braces and wildcards cannot be
used except at the lower level.

System action:

The command processing is terminated.

User response:

Correct the specification and try the command again.

------------------------------------------------------------------------
ANS0994E

Invalid string 'string' for virtual file space name or group name
specification.



Explanation:

You entered a virtual file space name or a group name specification that
contains wildcard characters.

System action:

Processing stopped.

User response:

Enter a correct virtual file space name and a group name and try again.
Use the pick option to display a list of groups from which you can
select one group.

------------------------------------------------------------------------
ANS0995E

Volume 'volume-name' could not be locked.



Explanation:

The system call to lock the volume failed.

System action:

Processing stopped.

User response:

Please verify that no other application is accessing the volume. During
restore of an image IBM Spectrum Protect must have exclusive use of the
volume.

------------------------------------------------------------------------
ANS1000E

An unsupported communications method was specified.



Explanation:

None.

System action:

processing stops.

User response:

Specify a communications interface that is supported by the IBM Spectrum
Protect client on your operating system. See the IBM Spectrum Protect
client manual for your operating system for further information on
configuring IBM Spectrum Protect client communications.

------------------------------------------------------------------------
ANS1001E

Volume being backed up was not a system volume. Skipped.



Explanation:

User specified to back up system volume only. This volume was not backed
up since this volume is not a system volume.

System action:

Volume was not backed up.

User response:

Use All option or use image backup command to backup this volume.

------------------------------------------------------------------------
ANS1002I

MOS image is being created. It may take a while.



Explanation:

Mini Operating System image is being created. It may take a while to
create it.

System action:

Processing Continues.

User response:

None.

------------------------------------------------------------------------
ANS1004W

Node has exceeded max tape mounts allowed. Operation for
'filespace-name' will be tried again later.



Explanation:

Node has exceeded max tape mounts allowed. The operation will be tried
again later.

System action:

The operation will be retried.

User response:

Increase the number of allowed tape mounts for this node on the server
to avoid this situation again.

------------------------------------------------------------------------
ANS1005I

TCP/IP read error on socket = socket-id, errno = error-code, reason :
'error-reason'.



Explanation:

An attempt to receive data using TCP/IP connection failed. If reason :
'Connection reset by peer', it is possible that the server control
connection timed out. This can occur if the file transfer time is
greater than 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 file transfer time, you can ignore
this message. The client will reconnect with the server automatically,
finish transferring the data, and send statistics. You can also consider
increasing the IDLETIMEOUT value in the server options file.

------------------------------------------------------------------------
ANS1006I

TCP/IP write error on socket = socket-id, errno = error-code, reason :
error-reason



Explanation:

An attempt to send data using TCP/IP connection failed.

System action:

Connection to server fails.

User response:

Retry the operation. If the problem persists, contact your system
administrator.

------------------------------------------------------------------------
ANS1007E

Sending of object 'object-nameobject-nameobject-name' failed. There is
no backup copy group.



Explanation:

The management class for this file (object-name) does not have a backup
copy group. Either the default management class does not have a backup
copy group, or an INCLUDE statement is attempting to bind the file to a
management class that does not have a backup copy group.

System action:

IBM Spectrum Protect did not back up the file.

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 Spectrum Protect server, make sure you
   are connecting to the correct server.

*  If you are unable to find a suitable management class, contact your
   IBM Spectrum Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1008E

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



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.

------------------------------------------------------------------------
ANS1009W

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



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 technical support for further assistance.

------------------------------------------------------------------------
ANS1010E

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



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 Spectrum 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 Spectrum Protect administrator for
further assistance.

------------------------------------------------------------------------
ANS1015E

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



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.

------------------------------------------------------------------------
ANS1016I

No eligible files matching 'pathname' were found.



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

System action:

None

User response:

Check the path you entered.

------------------------------------------------------------------------
ANS1017E

Session rejected: TCP/IP connection failure.



Explanation:

An attempt to connect to the server using TCP/IP communications failed.
This can be a result of incorrect TCP/IP option settings in your client
options file. This error can also occur if the LAN connection went down
or if your system administrator canceled a backup operation.

System action:

Session rejected. Processing stopped.

User response:

Retry the operation, or wait until the server comes back up and retry
the operation. If the problem continues, see your system administrator
for further help.

------------------------------------------------------------------------
ANS1018E

Port port number is already in use



Explanation:

The port specified by the TCPCLIENTPORT option is in use by a different
process.

System action:

Processing stopped.

User response:

Contact the server administrator to set up a different port for
server-initiated connections. Update the TCPCLIENTPORT with this new
port number.

------------------------------------------------------------------------
ANS1019E

The volume could not be opened.



Explanation:

An error occurred when IBM Spectrum Protect tried to open the volume for
a backup or restore operation.

System action:

The requested operation does not run.

User response:

Examine the client error log for additional messages related to this
error. Verify that the volume is available, and is not locked by another
process. Try the operation again. If the problem persists, contact IBM
technical support for further assistance.

------------------------------------------------------------------------
ANS1020E

System object backup failed.



Explanation:

An error occurred while backing up Windows system object files. The
backup did not complete.

System action:

Processing stopped.

User response:

Ask your system administrator to check the error log. Restart the
Windows service associated with the system object indicated in the error
log, and retry the backup operation

------------------------------------------------------------------------
ANS1021E

System object restore failed.



Explanation:

An error occurred while restoring Windows system object files. The
restore did not complete.

System action:

Processing stopped.

User response:

Ask your system administrator to check the error log. Restart the
machine, and then restore the system object indicated in the error log
again.

------------------------------------------------------------------------
ANS1022E

Cancel failed for node: node-name filesystem: fs-name operation: op-type
error: error



Explanation:

The request to cancel a remote operation has failed. The node, file
space, operation and reason for the failure are shown.

System action:

Operation not cancelled.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS1023E

Session rejected: Node type mismatch



Explanation:

Your node name is associated with a different type of operating system
and cannot be used on this system.

System action:

Current operation has been cancelled.

User response:

If you need a new node name, see your system administrator to assign a
new one to you. Generally, you have a unique node name for each machine
and operating system pair that requires access to the server.

------------------------------------------------------------------------
ANS1024E

Failed to update backup attributes on server for 'backup_type' backup
for 'file_space_namepath_namefile_name', object id 'object_id:object_id'
return code 'return code'.



Explanation:

Failed to update attributes for the named backup object on the server.
The server may not reflect correct state of the backup.

System action:

Processing continues.

User response:

Check preceding error messages in error log for more information. Retry
the operation. If problem continues, contact your IBM Spectrum Protect
administrator.

------------------------------------------------------------------------
ANS1025E

Session rejected: Authentication failure



Explanation:

Authentication failure. You entered an incorrect user id or password.

System action:

Current operation has been cancelled.

User response:

Enter your correct user id and password. If you cannot remember the
correct user id or password, see your system administrator to have new
credentials assigned for your node name.

------------------------------------------------------------------------
ANS1026E

The session is rejected: There was a communications protocol error.



Explanation:

An unexpected network message was received by the client. This could be
caused by network problems or a programming error.

System action:

The current operation has been cancelled.

User response:

Verify that your communication path is functioning properly and try the
operation again. If the problem persists, contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1028S

An internal program error occurred.



Explanation:

An unexpected condition was encountered and the operation can not
continue. This might be a programming error.

System action:

processing stops.

User response:

Try the operation again. If the problem persists, contact your IBM
Spectrum Protect administrator or IBM technical support for further
assistance.

------------------------------------------------------------------------
ANS1029E

Communication with the IBM Spectrum Protect server is lost.



Explanation:

This message is issued after the session with the IBM Spectrum Protect
server is unexpectedly lost. The client error log might contain
additional information regarding this problem.

System action:

processing stops.

User response:

*  Restart the IBM Spectrum Protect client and retry the operation.

*  If the problem persists, review the client error log for other
   messages that might be related to this problem.

*  Verify that network connectivity exists between the IBM Spectrum
   Protect client machine and the IBM Spectrum Protect server machine.

*  Contact your IBM Spectrum Protect administrator for further
   assistance. The IBM Spectrum Protect administrator can review the IBM
   Spectrum Protect server activity log for additional information about
   the problem.

------------------------------------------------------------------------
ANS1030E

The operating system refused a request for memory allocation.



Explanation:

Access to memory is required 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:

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 Spectrum Protect task serially for each
directory. If the IBM Spectrum 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.

------------------------------------------------------------------------
ANS1031E

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



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 ANS5216E that gives details of the
connection that failed. The condition may be temporary.

System action:

processing stops.

User response:

*  Restart the IBM Spectrum 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 Spectrum Protect server.

*  Verify that network connectivity exists between the IBM Spectrum
   Protect client machine and the IBM Spectrum Protect server machine.

*  If the problem persists, see your IBM Spectrum Protect administrator
   for further assistance.

------------------------------------------------------------------------
ANS1032E

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



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.

------------------------------------------------------------------------
ANS1033E

An invalid TCP/IP address was specified.



Explanation:

The TCP/IP address specified by the IBM Spectrum 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 Spectrum Protect server".

*  The machine that hosts the IBM Spectrum Protect server is not on the
   network.

*  A network problem is preventing the IBM Spectrum Protect client from
   reaching the machine that hosts the IBM Spectrum Protect server.

System action:

processing stops.

User response:

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

------------------------------------------------------------------------
ANS1034E

The specified TCP/IP host name is unreachable



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.

------------------------------------------------------------------------
ANS1035S

Options file 'file-name' could not be found, or it cannot be read.



Explanation:

Common reasons for this error include:

*  The default options file does not exist.

*  You specified the -OPTFILE option when starting the IBM Spectrum
   Protect client, but the options file you provided does not exist.

*  The DSM_CONFIG (or DSMI_CONFIG if you are using the IBM Spectrum
   Protect API) environment variable specifies an options file that does
   not exist.

*  You specified the -OPTFILE option when starting the IBM Spectrum
   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 ANSI.

*  You specified the -OPTFILE option when starting the IBM Spectrum
   Protect client, but the options file that you provided does not have
   appropriate read permissions for the user that is running the
   operation.

System action:

IBM Spectrum Protect client processing stops.

User response:

Make sure that the options file you want to use exists, it has the read
rights set for the user that is running the operation, and it is in the
standard file encoding of the system. For example, on Windows the
expected file encoding is ANSI. Review the configuration information in
the IBM Spectrum Protect client manual specific to your operating
system. If the problem persists, ask your IBM Spectrum Protect
administrator for further assistance.

------------------------------------------------------------------------
ANS1036S

The option 'option' or the value supplied for it is not valid. It was
found in options file 'file-name' at line number: number The complete
entry: 'entry'



Explanation:

The specified option or option value is not valid. For options that
include a date or time specification, the format of the date or time
might not match the formats specified by the DATEFORMAT or TIMEFORMAT
options.

System action:

Processing stops.

User response:

Correct the option name or value. For options that specify dates or
times, ensure that the specified date or time matches the DATEFORMAT and
TIMEFORMAT settings. If -DATEFORMAT or -TIMEFORMAT are specified on the
command line, they must precede the option that specifies the date or
time. For example, use -DATEFORMAT=3 -FROMDATE=yyyy-mm-dd, instead of
-FROMDATE=yyyy-mm-dd -DATEFORMAT=3.

------------------------------------------------------------------------
ANS1037S

Invalid keyword specified



Explanation:

An incorrect keyword was found in the options file.

System action:

Processing stopped.

User response:

Correct the options file with valid entries.

------------------------------------------------------------------------
ANS1038S

Invalid option specified.



Explanation:

An incorrect option was specified to IBM Spectrum Protect.

System action:

Processing stopped.

User response:

Correct the options used for running IBM Spectrum Protect.

------------------------------------------------------------------------
ANS1039S

The include or exclude pattern cannot be parsed.



Explanation:

The pattern is formatted incorrectly or is too complex to be
interpreted.

System action:

Processing stopped.

User response:

Verify that the include or exclude pattern is specified correctly. If
the pattern is correct, then contact IBM technical support for further
assistance.

------------------------------------------------------------------------
ANS1040S

Include/Exclude pattern is missing a closing bracket



Explanation:

The include or exclude pattern is incorrectly constructed. The closing
bracket is missing.

System action:

Processing stopped.

User response:

Correct the syntax for the pattern.

------------------------------------------------------------------------
ANS1041S

Include/Exclude pattern must start with a directory delimiter



Explanation:

The include or exclude pattern must start with a directory delimiter.

System action:

Processing stopped.

User response:

Correct the syntax for the pattern.

------------------------------------------------------------------------
ANS1042S

A beginning or ending directory delimiter is missing from the
Include/Exclude pattern.



Explanation:

1. The include/exclude pattern has a '...' without a beginning or ending
   directory delimiter.

2. For Windows, the drive seperator is not immediately followed by a
   directory delimiter.

System action:

Processing stopped.

User response:

Correct the syntax for the pattern.

------------------------------------------------------------------------
ANS1043S

Quotes are not matched



Explanation:

The quotes specified in the pattern are not the same and do not make a
set.

System action:

Processing stopped.

User response:

Correct the pattern by using matching quotes in the syntax.

------------------------------------------------------------------------
ANS1044W

Image backup of disk 'option-name' with disk sector size 'block-size' is
not supported. Image backup supports only disks with 512 bytes sector.



Explanation:

The image backup operation supports disks with sector size 512 bytes.
Other sector sizes are not supported.

System action:

Use image backup only for disks with 512 bytes sector.

User response:

None.

------------------------------------------------------------------------
ANS1047E

The destination file system is unavailable. The following object was
skipped: File space:'filespace-name' Pathname:' path-name'
Filename:'file-name'



Explanation:

The client is trying to restore or retrieve the 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 a different destination.

------------------------------------------------------------------------
ANS1048E

Device 'volname' is not local



Explanation:

The selected path is not a local device and therefore is not a valid
object for image operations.

System action:

The requested logical volume operation is not performed.

User response:

Choose another object.

------------------------------------------------------------------------
ANS1049E

'filename' is not a valid destination file for image restore



Explanation:

The filename you specified is not a valid name for a file or it is a
directory.

System action:

Restore processing stopped.

User response:

Specify a correct filename for image restore.

------------------------------------------------------------------------
ANS1050E

Volume 'volume-name' could not be locked for the VSS Instant Restore.



Explanation:

The volume cannot be locked because another application is accessing the
file systems on the volume.

System action:

Processing stops.

User response:

Stop or suspend the applications that have handles open on the volume.
For a file system restore, close applications that are accessing the
file systems that are used for the VSS Instant Restore.

If you cannot close the applications that are accessing the file system,
unmount the file system. After the unmount process is complete, mount
the file system and perform the VSS Instant Restore.

For more information, see the error log file DSMERROR.LOG.

------------------------------------------------------------------------
ANS1051I

Invalid user id or password



Explanation:

You entered an invalid user id or password.

System action:

IBM Spectrum Protect cannot connect to the server without the correct
credentials.

User response:

Contact your system administrator for the correct credentials.

------------------------------------------------------------------------
ANS1052E

Direct connection to the Storage Agent is not allowed.



Explanation:

You cannot connect directly to the Storage Agent.

System action:

Processing stopped.

User response:

To perform Lanfree operations using the Storage Agent, specify the
ENABLELANFREE option in your options file, and restart the process.

------------------------------------------------------------------------
ANS1053I

Existing file space file_space_name has been renamed to file_space_name



Explanation:

If the file space is for Windows system state, this message is issued
when the IBM Spectrum Protect backup-archive client detects multiple
system state file spaces where the names differ only in case. The
existence of multiple system state file spaces can occur if, at some
earlier time, your IBM Spectrum Protect administrator renamed the system
state file space to the same name but with a different case or the
computer's name was changed from all upper case characters to lower case
or mixed case characters. If the file space name represents a drive
volume label, then this file space was created by an older IBM Spectrum
Protect backup-archive client.

System action:

If the file space is for Windows system state, IBM Spectrum Protect will
back up system state to the file space containing the most recent
backup. The older file space is renamed as specified in this message.
Subsequent system state backups will continue to back up system state to
the same (most recently used) file space. If the file space name
represents a drive volume label, it will be renamed to the corresponding
UNC name and continues to back up 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 determined
you no longer need the older renamed system state file space, you can
ask your IBM Spectrum Protect administrator to delete the older file
space from IBM Spectrum Protect storage.

------------------------------------------------------------------------
ANS1054E

Existing filespace filespace-name cannot be renamed to new filespace
filespace-name. IBM Spectrum Protect return code = retcode.



Explanation:

The client was unable to migrate a file space name from the volume label
naming convention to the UNC naming convention.

System action:

Processing stopped.

User response:

Check the client error log and the IBM Spectrum Protect server activity
log for any other messages that might help identify the problem. If the
problem cannot be resolved, contact IBM technical support for additional
assistance.

------------------------------------------------------------------------
ANS1055I

Trying to rename existing filespace filespace-name to new filespace
filespace-name, but drive letters do not match, old=drive-letter,
new=drive-letter. Ignore the old filespace and backup to the new
filespace.



Explanation:

Trying to rename the existing filespace name using the volume label to
the UNC format naming convention but the drive letters do not match.
Leave the existing filespace alone and create a new filespace.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1056E

Share/network path share cannot be resolved. Path does not exist.



Explanation:

For backup: Trying to backup share/network, which either does not exist
or does not have the correct privilege to access the share. For restore
: Trying to restore to a share/network path that cannot be resolved. The
directory path does not exist.

System action:

Processing stopped.

User response:

Retry the command and specify a destination, or restore the directory
tree first before trying to restore the share point.

------------------------------------------------------------------------
ANS1057I

File space file_space_name cannot be renamed to new file space
file_space_name, because the new file space already exists.



Explanation:

The client was unable to migrate a file space name from the volume label
naming convention to the UNC naming convention because the new file
space already exists on the IBM Spectrum Protect server.

System action:

The operation proceeds using the new file space. The old file space is
ignored.

User response:

No action is necessary, but if the data in the old file space is no
longer needed, it can be deleted from the IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS1058E

The restore destination cannot be reached.



Explanation:

Either the destination file system is invalid or it cannot be reached.

System action:

Processing stopped.

User response:

Try the command again using a different destination.

------------------------------------------------------------------------
ANS1059E

Two inactive objects with the same image name were selected. Process
terminates



Explanation:

You selected more than one inactive version of the same image object
(logical volume). The system has no way to decide which you want to
restore.

System action:

The requested logical volume restore is not performed.

User response:

Retry the operation, selecting an active version or only one inactive
version of the volume you wish to restore.

------------------------------------------------------------------------
ANS1060E

The specified path is not a mounted filesystem



Explanation:

You entered a file system name that does not correspond to a mounted
file system for this system. It is possible the file system name is
misspelled, or simply that the file system is not currently mounted.

System action:

The requested logical volume operation is not performed.

User response:

Retry the operation, using name of a mounted file system.

------------------------------------------------------------------------
ANS1061E

The specified device corresponds to a mounted file system; you must
specify the file system by name.



Explanation:

You entered a logical device name that is mapped to a mounted file
system. This volume must only be referenced by its file system name.

System action:

The requested logical volume operation is not performed.

User response:

Try the operation again, using the file system name instead of the
device name.

------------------------------------------------------------------------
ANS1062E

Only a single image may be selected when a destination is entered.



Explanation:

You selected more than one image object (logical volume) to be restored.
You also specified a destination. The system cannot place more than one
image into a single destination volume. When more than one object is
selected, each must be restored to its original location.

System action:

The requested logical volume restore is not performed.

User response:

Retry the operation, selecting one object to be restored to the given
destination, or retry the operation without entering the destination.

------------------------------------------------------------------------
ANS1063E

The specified path is not a valid file system or logical volume name.



Explanation:

None.

System action:

The logical volume operation is not performed.

User response:

Try the operation again using a valid path.

------------------------------------------------------------------------
ANS1064E

An unexpected error occurred while processing the image operation.



Explanation:

None.

System action:

The requested operation does not run.

User response:

Examine the client error log for any additional messages that may have
been issued before or after this message. Correct any problems, if
possible. If the cause of this message can not be determined or
resolved, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1065E

Library version of the image utility does not match that of the IBM
Spectrum Protect API



Explanation:

The current system has a mix of installed components.

System action:

The requested logical volume operation is not performed.

User response:

Re-install all IBM Spectrum Protect components

------------------------------------------------------------------------
ANS1066E

The restore operation completed successfully, but the file system could
not be remounted.



Explanation:

None.

System action:

The file system is left unmounted.

User response:

Use the mount command to mount the file system. On AIX, run fsck if
requested by the operating system.

------------------------------------------------------------------------
ANS1067E

A call to a system function returned an unexpected error.



Explanation:

If you are performing a JFS2 snapshot based operation, it is possible
that the snapshot was not large enough to contain all the changes made
to the filesystem after the snapshot was created. This could cause the
snapshot to become invalid thereby preventing IBM Spectrum Protect
client from reading the snapshot.

System action:

The requested operation does not run.

User response:

Examine the client error log for additional messages related to this
error. Try the operation again. If the problem persists, contact IBM
technical support for further assistance.

If you are performing a JFS2 snapshot based operation, please use the
default snapshotcachesize of 100% and ensure that the volume group has
sufficient disk space to allocate snapshots at least as large as the
file system and retry the operation.

------------------------------------------------------------------------
ANS1068E

The device is not local.



Explanation:

The selected path is not a valid object for image operations. The
selected path is either a remote device or a partition that resides on a
multipath device.

System action:

The requested logical volume operation is not performed.

User response:

Choose another object.

------------------------------------------------------------------------
ANS1069E

An error occurred while reading data from the device



Explanation:

An error occurred while reading data from the device. Windows Only: This
could be due to bad sectors on the drive.

System action:

The requested logical volume operation is not performed.

User response:

Retry the operation, then check the error log for more information.
Windows Only: Please run chkdsk /r and retry the operation. If the
problem persists, a possible workaround is to back up the entire drive
using a regular (non-image) backup. Please ensure that all your data is
backed up. Then format the drive using a full format (without the /q
quick format option). Then restore the data and retry the image backup
operation.

------------------------------------------------------------------------
ANS1070E

Write error



Explanation:

An error occurred while writing data to the device.

System action:

The requested logical volume operation is not performed.

User response:

Re-try the operation, check error log for more information.

------------------------------------------------------------------------
ANS1071E

Invalid domain name entered: 'domain-name'



Explanation:

You entered an invalid domain name. Verify whether the domain name is a
file system and the file system is mounted. A directory cannot be
specified in the domain option, unless it is a virtual mount point.

System action:

Processing continues if there are other file systems in the domain
option to back up.

User response:

Enter a valid drive or file system name (domain).

------------------------------------------------------------------------
ANS1072E

Unable to continue operation; Drive 'drive-name' has no volume label.



Explanation:

The specified drive-name in the domain list does not have a volume
label.

System action:

Processing stopped.

User response:

Use the system format utility to place a unique volume label on all
drives on which you intend to run IBM Spectrum Protect.

------------------------------------------------------------------------
ANS1073E

The file space for domain 'domain-name' could not be found on the IBM
Spectrum Protect server.



Explanation:

The specified file space was expected to be found on the server, but it
no longer exists. It is possible that a command was issued to delete the
file space from the server while the current operation was in progress.

System action:

IBM Spectrum Protect processing stops.

User response:

Try the operation again. If the problem recurs, check the error log for
any other messages that might indicate a reason for the failure. Try to
correct any indicated problems, then try the operation again. If the
problem persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1074W

The operation was stopped by the user.



Explanation:

The operation was stopped at the request of the user. This usually
occurs when the 'Q' key is pressed two times.

System action:

Processing stopped.

User response:

None.

------------------------------------------------------------------------
ANS1075E

file name(line number)The operating system refused a IBM Spectrum
Protect request for memory allocation.



Explanation:

IBM Spectrum 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.

System action:

IBM Spectrum Protect cannot complete the requested operation.

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 Spectrum Protect task serially for each
directory. If the IBM Spectrum Protect task is an incremental backup,
use the option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, you can check 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 the resource limit above the current default limit. The UNIX
system root user has the authority to increase resource limits.

------------------------------------------------------------------------
ANS1076E

The specified directory path 'pathname' could not be found.



Explanation:

An invalid or unreachable directory path was specified.

System action:

Processing stopped.

User response:

Try the operation again using a valid directory path.

------------------------------------------------------------------------
ANS1078S

Unknown system error error-code occurred.



Explanation:

An unknown error error-code occurred within the client program.

System action:

The client stops.

User response:

Check the error log for any other messages that might indicate a reason
for the failure. Try to correct any indicated problems, then try the
operation again. If the problem persists, contact IBM technical support
for further assistance.

------------------------------------------------------------------------
ANS1079E

No file specification entered



Explanation:

You did not enter a file specification as prompted.

System action:

The process did not continue with the requested operation.

User response:

Enter a file specification to continue.

------------------------------------------------------------------------
ANS1081E

Invalid search file specification 'string' entered.



Explanation:

You entered a file specification or search string that contains
incorrect characters or contains wildcard characters in the drive
specification or file system name.

System action:

Processing stopped.

User response:

Enter a correct file specification as described in the appropriate Using
the Backup-Archive Client book for the particular operating system.

------------------------------------------------------------------------
ANS1082E

Invalid destination file specification 'file-name' entered



Explanation:

You entered a destination file-name specification that contains
incorrect characters or has wildcard characters in the specification.

System action:

Processing stopped.

User response:

Enter a correct file specification as described in the appropriate Using
the Backup-Archive Client book for the particular operating system.

------------------------------------------------------------------------
ANS1083E

No files have previously been archived for 'filespace-name'



Explanation:

You tried to retrieve files when no files for the specified drive or
file system (filespace-name) were previously archived.

System action:

Processing stopped.

User response:

Ensure that the correct drive or file system was specified and that
files are archived for you to retrieve.

------------------------------------------------------------------------
ANS1084E

No files have previously been backed up for ' filespace-name' or the
specified file space is invalid for the current operating system.



Explanation:

You cannot restore files. Either the file space or drive is invalid, or
no backup copies exist.

System action:

Processing stops.

User response:

Specify a valid drive or file space. Verify that backup copies exist.

------------------------------------------------------------------------
ANS1085E

The VMware vStorage API reported an invalid snapshot configuration.



Explanation:

A VMware vStorage API error occurred due to an invalid snapshot
configuration.

System action:

A VMware vStorage API error occurred, and the virtual machine backup
failed.

User response:

Check the VMware logs for possible causes of the error, and retry the
operation.

------------------------------------------------------------------------
ANS1086E

File not found during Backup, Archive or 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 be
backed up, archived or migrated by IBM Spectrum Protect.

System action:

File skipped.

User response:

None.

------------------------------------------------------------------------
ANS1087E

Access to the specified file or directory is denied



Explanation:

Access to the specified file or directory is denied. You tried to read
from or write to a file and you do not have access permission for either
the file or the directory.

System action:

Processing stopped.

User response:

Ensure that you specified the correct file or directory name, correct
the permissions, or specify a new location.

------------------------------------------------------------------------
ANS1088E

File space 'filespace-name' does not exist



Explanation:

The specified file space (domain) is incorrect or does not exist on the
machine.

System action:

Processing stopped.

User response:

Retry the operation specifying an existing domain (drive letter or file
system name).

------------------------------------------------------------------------
ANS1089E

Destination directory path length exceeds system maximum



Explanation:

The path name specified plus the path name in the restored file name
combine to create a name whose length exceeds the system maximum.

System action:

Processing stopped.

User response:

Specify a destination path that, when combined, is less than the system
maximum.

------------------------------------------------------------------------
ANS1090E

The LVM1 device is no longer supported by this client.



Explanation:

The selected path refers to a volume device managed by LVM version 1.
LVM 1 is no longer supported by this version of client and therefore is
not a valid object for image operations.

System action:

The requested logical volume operation is not performed.

User response:

Use earlier versions of the client that support LVM1 to perform the
logical volume operation. Alternatively, you can upgrade to LVM2 and
migrate the volume to LVM2. LVM2 is supported by this client for logical
volume operations.

------------------------------------------------------------------------
ANS1091E

Communications error with server during object query



Explanation:

An unexpected communications error occurred during an object query to
the server.

System action:

Processing stopped.

User response:

Verify that communications are active between the client and server
machines. Server outages, processor outages, and communication
controller outages can cause this error.

------------------------------------------------------------------------
ANS1092W

No files matching search criteria were found



Explanation:

You entered a search pattern or file name that cannot be found in the
server database.

System action:

Processing stopped.

User response:

Ensure that your search pattern is correct, or specify a new search
string.

------------------------------------------------------------------------
ANS1093E

Your IBM Spectrum Protect server does not support point-in-time
processing.



Explanation:

The client has requested a point-in-time query or restore operation, but
the IBM Spectrum Protect server to which the client is connected does
not support point-in-time operations.

System action:

Processing stopped.

User response:

Make sure that you are connected to the correct IBM Spectrum Protect
server. If you are connected to the correct server, then try the command
again without specifying any point-in-time options.

------------------------------------------------------------------------
ANS1094E

An error occured trying to connect to the restore location on the
virtual machine. Verify that the restore location exists on the virtual
machine and that your account has access to it.



Explanation:

During restore processing, the system creates a share to access the
restore location on the virtual machine. In this situation, the system
was unable to create a share. This error typically occurs if the restore
location does not exist or the user account does not have access to the
location.

System action:

The system was unable to create a share.

User response:

Verify that the restore location exists on the virtual machine and that
your account has access to it.

------------------------------------------------------------------------
ANS1096S

Either the node does not exist on the server or there is no active
policy set for the node.



Explanation:

This error occurs when you try to access another node's data. Either the
node is not registered with the IBM Spectrum Protect server, or there is
no active policy set for the node.

System action:

Processing stops.

User response:

Verify that the node whose data you are trying to access is registered
with the IBM Spectrum Protect server. If you have more than one IBM
Spectrum Protect server, make sure you are connecting to the correct
server, then try the operation again. If the problem persists, contact
your IBM Spectrum Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1097E

The client help text cannot be read from the help file.



Explanation:

The help file was opened successfully and its table of contents are
available, but there is a problem reading the text from the help file.

System action:

Processing stopped.

User response:

If the DSM_DIR environment variable is set, verify that it points to the
directory containing the current level of IBM Spectrum Protect program
files, then try the operation again. If the problem recurs, re-install
the client software. If the problem persists, IBM technical support for
further assistance.

------------------------------------------------------------------------
ANS1098E

Process terminated; Program memory exhausted.



Explanation:

The program used all available storage.

System action:

Processing stopped.

User response:

Free any unnecessary programs (TSRs) that are running, and retry the
operation. Reducing the scope of queries and the amount of data returned
can also solve the problem.

------------------------------------------------------------------------
ANS1099E

File 'filename' not previously archived



Explanation:

You tried to give access to a file, which is not stored on the server.

System action:

Processing stopped.

User response:

Ensure that the correct filename is specified.

------------------------------------------------------------------------
ANS1100E

File 'filename' not previously backed up



Explanation:

You tried to give access to a file, which is not stored on the server.

System action:

Processing stopped.

User response:

Ensure that the correct filename is specified.

------------------------------------------------------------------------
ANS1101E

User is not authorized to encrypt file-space
namedirectory_pathfile_name.



Explanation:

The user is not authorized to encrypt the file. Normally, only a IBM
Spectrum Protect authorized user or a root user can use IBM Spectrum
Protect encryption. However, a certain combination of PASSWORDACCESS and
ENCRYPTKEY options may allow encryption operations by a non-authorized
user.

System action:

The file is not backed up or restored.

User response:

Log in as a root or IBM Spectrum Protect authorized user and try the
operation again. See IBM Spectrum Protect Backup-Archive Client
Installation and User's Guide for the correct usage of the ENCRYPTKEY
option.

------------------------------------------------------------------------
ANS1102E

An excessive number of command line arguments are passed to the program.



Explanation:

This command processing routine received more operands than it can use.
The rules are:

*  Query can contain only one file specification.

*  Restore and Retrieve can contain two file specifications.

*  Archive, Incremental, and Selective can contain a maximum of 20 file
   specifications. To bypass the 20-operand limit, use the
   -REMOVEOPERANDLIMIT option on the failing archive, incremental, or
   selective command.

Note: The Client operates much more efficiently if it expands wild cards
internally, rather than accepting the expanded list from the shell.

System action:

Processing stopped.

User response:

Reduce the number of arguments and retry the operation. For UNIX-based
systems, ensure that you have surrounded the specification containing
pattern matching characters with quotes. As an alternative, use the
-REMOVEOPERANDLIMIT option on the failing archive, incremental, or
selective command.

------------------------------------------------------------------------
ANS1103E

Invalid management class entered



Explanation:

You entered an invalid management class.

System action:

Requested operation is not possible.

User response:

Retry the operation using a valid management class.

------------------------------------------------------------------------
ANS1104E

The management class for this file does not have a valid archive copy
group. This file will not be archived.



Explanation:

The management class for this file does not have an archive copy group
specified. This file will not be archived.

System action:

Processing stopped.

User response:

Add a valid archive copy group to the management class, and then retry
the operation.

------------------------------------------------------------------------
ANS1105E

The management class for this file does not have a valid backup copy
group. This file will not be backed up.



Explanation:

The management class for this file does not have a backup copy group
specified. This file will not be backed up.

System action:

Processing stopped.

User response:

Add a valid backup copy group to the management class, and then retry
the operation.

------------------------------------------------------------------------
ANS1106E

ENCRYPTKEY SAVE not configured correctly. Encryption not used.



Explanation:

This message is issued for IBM Spectrum Protect Authorized Users and
root users when ENCRYPTKEY SAVE and PASSWORDACCESS PROMPT options are
set. Please note that these are the default values. These values do not
allow encryption.

System action:

The file is not encrypted.

User response:

To save encryption keys, you must change configuration values. Add
PASSWORDACCESS GENERATE to your system option file.

------------------------------------------------------------------------
ANS1107E

Invalid option/value: 'option'



Explanation:

You specified an incorrect IBM Spectrum 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 Spectrum Protect option as defined in the
appropriate Using the Backup-Archive Client book for the particular
operating system.

------------------------------------------------------------------------
ANS1108E

Invalid option (option) for the function command.



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.

------------------------------------------------------------------------
ANS1110E

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



Explanation:

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

System action:

Processing stopped.

User response:

If the DSM_DIR environment variable is set, verify that it points to the
directory containing the current level of IBM Spectrum Protect program
files, then try the operation again. If the problem recurs, re-install
the client software. If the problem persists, IBM technical support for
further assistance.

------------------------------------------------------------------------
ANS1111E

The requested operation is not possible using the management class that
was entered.



Explanation:

The management class is not valid because the Data Version Exists value
is greater than 30. For local backups on a VVOL datastore, this value
must be 1 - 30.

System action:

Processing stopped.

User response:

Retry the operation using a valid management class.

------------------------------------------------------------------------
ANS1113E

The snapshot cache location is not valid.



Explanation:

The snapshot cache location must point to a local volume that is
formatted with NTFS. The default cache location is on the same volume
where the snapshot is being performed. The operation will continue
without snapshot support.

System action:

The client does not execute the snapshot backup operation.

User response:

Specify a different snapshot cache location using the
SNAPSHOTCACHELOCATION option.

------------------------------------------------------------------------
ANS1114I

Waiting for mount of offline media.



Explanation:

The server is waiting for the requested media to become available before
the operation can continue.

System action:

Waiting for requested data.

User response:

None.

------------------------------------------------------------------------
ANS1115W

File 'file-namefile-namefile-name' excluded by Include/Exclude list



Explanation:

You can not back up, archive, or migrate files that are excluded.

System action:

The file can not be processed.

User response:

If the file is intentionally excluded, then this message can be ignored.
Otherwise modify the include/exclude list, restart the client, and try
the operation again. Contact your IBM Spectrum Protect administrator for
further assistance.

------------------------------------------------------------------------
ANS1116E

The process is running in a non-interactive mode, but requires user
input.



Explanation:

This process requires keyboard input, but non-interactive processes are
unable to read input from keyboard.

System action:

processing stops.

User response:

Perform the following actions to resolve this error:

*  Run the product in interactive mode.

*  Ensure your password is set correctly.

------------------------------------------------------------------------
ANS1117E

The PICK and LATEST options are not valid together



Explanation:

During a restore, PICK and LATEST options cannot be used together.

System action:

Processing stopped.

User response:

Try again using either the PICK or the LATEST option.

------------------------------------------------------------------------
ANS1118I

Invalid file space number entered. Try again.



Explanation:

The number that represents a file space was incorrect while you were
using the PICK option.

System action:

The process waits for your specification.

User response:

Enter a correct file space number.

------------------------------------------------------------------------
ANS1119I

Initiating the removal of 'filespace-name' file space.



Explanation:

Indicates that file space deletion has started on the specified
filespace-name.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS1120E

Removal of file space 'filespace-name' failed



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 ANS1126E.

*  The named filespace does not exist on the server. Look for message
   ANS1122W.

*  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 Spectrum Protect administrator has the authority to
delete the file space for you.

------------------------------------------------------------------------
ANS1121I

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



Explanation:

IBM Spectrum Protect has requested deletion of the specified
filespace-name. The deletion process may not have actually been
completed when this message is displayed. To verify successful deletion,
consult the server logs.

It is possible for errors to occur on the server during the deletion
process, or the file space might contain archive objects in
deletion-hold status. In either case, the file space will not be
deleted.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS1122W

File space 'filespace-name' does not exist on the server. The file space
might have been deleted by another client using your client's node name
or an administrator.



Explanation:

The specified filespace-name does not exist on the server. Your system
administrator deleted the file space or another client using your
client's node name might have deleted it.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS1123E

The vertical screen dimension is too small to display the Help
directory. Increase your window height.



Explanation:

Execution of the HELP command requires space for both the user prompts
and at least one 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 display window to allow more rows of text to
be displayed.

------------------------------------------------------------------------
ANS1125E

Unmatched Quotes: 'string'



Explanation:

The quotes specified in the pattern are not the same and do not make a
set.

System action:

Processing stopped.

User response:

Correct the pattern using matching quotes in the syntax.

------------------------------------------------------------------------
ANS1126E

The file space cannot be deleted because this node does not have
permission to delete archived or backed up data.



Explanation:

You cannot delete the file space data unless your IBM Spectrum Protect
administrator has authorized your node to do so. Authorization permits
you to delete backup data, archive data, or both.

System action:

Delete processing fails.

User response:

Use the DSMC QUERY SESSION command to verify your authorization. Ask
your IBM Spectrum Protect administrator to provide the necessary
authorization or to delete the file space for you.

------------------------------------------------------------------------
ANS1127E

Your node does not have permission to delete archived files.



Explanation:

You cannot delete archived files unless your IBM Spectrum Protect
administrator has authorized your node to do so.

System action:

IBM Spectrum Protect does not delete the archived files.

User response:

Use the DSMC QUERY SESSION command to verify your authorization. Ask
your IBM Spectrum Protect administrator to provide the necessary
authorization.

------------------------------------------------------------------------
ANS1128S

The management class assigned to directories does not exist.



Explanation:

The management class named on the DIRMC option does not exist in your
assigned policy set on the server. The error log contains an entry
showing the invalid management class name.

System action:

processing stops.

User response:

Remove the current DIRMC option from the client options file, then run
DSMC QUERY MGMTCLASS -DETAIL to view information about available
management classes. Make sure the management class you select has a
backup copy group. If you have more than one IBM Spectrum Protect
server, make sure you are connecting to the correct server. If you are
unable to find a suitable management class, contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1129S

There is no backup copy group in the management class used for
directories.



Explanation:

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

System action:

processing stops.

User response:

Remove the current DIRMC option from the client options file, then run
DSMC QUERY MGMTCLASS -DETAIL to view information about available
management classes. Make sure the management class you select has a
backup copy group. If you have more than one IBM Spectrum Protect
server, make sure you are connecting to the correct server. If you are
unable to find a suitable management class, contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1130E

The drive has no label. The operation cannot continue.



Explanation:

Backup or archive of removable media requires that the media have a
volume label. An attempt was made to back up or archive data on a
removable volume that has no label.

System action:

The requested operation does not run.

User response:

Create a volume label on the removable media, then try the operation
again.

------------------------------------------------------------------------
ANS1131E

A duplicate volume label exists. The operation cannot continue.



Explanation:

For removable media, IBM Spectrum Protect uses the volume label as the
file space name. To prevent data from different volumes being stored in
the same file space on the IBM Spectrum Protect server, backup or
archive of removable media volumes having duplicate volume labels is not
allowed.

System action:

The requested operation does not run.

User response:

Change the volume labels on the removable media volumes so that there
are no duplicate labels. Then restart IBM Spectrum Protect and try the
operation again.

------------------------------------------------------------------------
ANS1132E

'Access rule' Access Rule already defined for node 'node'. Old rule must
be deleted before new one can be defined.



Explanation:

You are trying to define authorization for the specified node, which
already has authorization defined.

System action:

IBM Spectrum Protect did not redefine authorization for the specified
node.

User response:

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

------------------------------------------------------------------------
ANS1133W

An expression might contain a wildcard not enclosed in quotes.



Explanation:

The command cannot be processed because a UNIX shell expands a wildcard
expression, such as an asterisk (*) or a question mark (?), that has no
quotes.

If the expression contains no wildcard characters and you wish to place
more than the stated limit of operands on the Archive, Selective, or
Incremental command, add the -REMOVEOPERANDLIMIT option to the command,
and try it again.

System action:

Command dependent.

User response:

Enclose the wildcard expression in quotes, or add the
-REMOVEOPERANDLIMIT option and enter the command again.

------------------------------------------------------------------------
ANS1134E

Drive drive-name is an invalid drive specification



Explanation:

The specified drive name is not valid; the drive probably has not been
defined.

System action:

Process skips the invalid drive and continues to the next drive.

User response:

Check the invalid drive.

------------------------------------------------------------------------
ANS1135E

Drive drive-name1 is a virtual drive of drive-name2. It cannot be backed
up or archived.



Explanation:

One drive is a substitute (SUBST) of the other drive. The SUBST drive
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 specifications for a drive that is a substitute
of another drive. Remove any explicit substitute drives from the DOMAIN
statement or use the -<drive:> notation to remove a substitute drive if
ALL-LOCAL is specified.

------------------------------------------------------------------------
ANS1136E

Not file owner



Explanation:

The file cannot be backed up because the client is not the file owner.

System action:

The file is skipped.

User response:

None.

------------------------------------------------------------------------
ANS1137W

Invalid Index 'number' skipped.



Explanation:

An incorrect number was entered for the Index.

System action:

Processing stopped.

User response:

Correct the Index entry and retry the operation.

------------------------------------------------------------------------
ANS1138E

The 'command-name' command must be followed by a subcommand



Explanation:

You entered an incomplete command-name.

System action:

Processing stopped.

User response:

Enter the correct syntax of the command and continue.

------------------------------------------------------------------------
ANS1139W

'object-nameobject-nameobject-name' was restored as 'temp-name'. A
reboot is required to complete the restore.



Explanation:

The file being restored was in use by another application, so it could
not be immediately replaced. The file will be replaced during the next
reboot of the operating system. It is important to note that until the
reboot occurs, the system or its applications might be unstable. The
degree of instability depends on the criticality of the file to the
operating system or applications.

System action:

The file was restored with a temporary name, and instructed the
operating system to replace the original file with the restored file
during the next boot of the operating system.

User response:

Reboot the machine as soon as possible after the restore operation ends.

------------------------------------------------------------------------
ANS1140E

Invalid format for Set Access command.



Explanation:

The SET ACCESS command must have at least three operands, the first of
which must be either BACKUP or ARCHIVE. A validly formed file
specification must follow.

System action:

Processing stopped, the command is not executed.

User response:

Use the HELP SET ACCESS command for complete details of usage, then
enter the SET ACCESS command using the correct syntax.

------------------------------------------------------------------------
ANS1141W

Unknown command - command-name



Explanation:

You entered an incorrect command-name.

System action:

None.

User response:

Enter the correct command.

------------------------------------------------------------------------
ANS1143E

The DIRSONLY and FILESONLY options are not valid together



Explanation:

The DIRSONLY and FILESONLY options cannot be used together.

System action:

Processing stopped.

User response:

Try again using either the DIRSONLY or the FILESONLY option.

------------------------------------------------------------------------
ANS1144W

Password authentication not active on server



Explanation:

None.

System action:

Processing stopped.

User response:

Because password authentication is turned off on the server, you do not
need to update the password.

------------------------------------------------------------------------
ANS1145E

The maximum macro nesting level has been exceeded. Macros may be nested
up to 10 levels.



Explanation:

IBM Spectrum Protect allows macros to invoke other macros, for example,
macro 'A' invokes macro 'B' which, in turn, invokes macro 'C'. This is
nesting to 3 levels. The limit is 10 levels (the inital macro plus nine
levels of calls within macros currently executng). There is no limit to
the number of different macro calls that may be made within a macro as
long as the calls are not nested.

System action:

The macro is ignored and an error is returned.

User response:

Reduce the level of macro nesting.

------------------------------------------------------------------------
ANS1146E

Macro file 'file spec' cannot be opened.



Explanation:

A macro command has been entered that specifies the macro file name
shown. However, that file cannot be opened for reading.

System action:

The macro is ignored and an error is returned.

User response:

Enter the command with the proper macro name.

------------------------------------------------------------------------
ANS1147E

File is temporarily unavailable.



Explanation:

File is temporarily unavailable.

System action:

File skipped.

User response:

Check and see if file is locked by other process. If not, retry the
command.

------------------------------------------------------------------------
ANS1148I

'Command-name' command successfully completed



Explanation:

The specified command-name was successfully completed.

System action:

Command completed.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS1149E

No domain is available for incremental backup. The domain may be empty
or all file systems in the domain are excluded.



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
Spectrum 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.

------------------------------------------------------------------------
ANS1150E

Unable to restore current user profile because you are running as a
local system account.



Explanation:

The local system account does not have a profile. Therefore you cannot
restore its profile.

System action:

Processing stops.

User response:

Log on to the user whose profile you want to restore.

------------------------------------------------------------------------
ANS1151E

'drive-name1' is not a cluster disk.



Explanation:

The indicated file system is not a cluster disk. Because the CLUSTERNODE
option is set to YES, the file system cannot be backed up or archived.

System action:

Processing stops.

User response:

If the CLUSTERNODE option is incorrectly set to YES, then change the
option to NO and try the operation again. Otherwise see the client
manual for further information about configuring the client to run in a
cluster environment.

------------------------------------------------------------------------
ANS1152E

The VMware vStorage API reported a failure to quiesce the virtual
machine.



Explanation:

A VDDK error occurred while quiescing the virtual machine.

System action:

A VMware vStorage API error occurred, and the virtual machine backup
failed.

User response:

This error can occur if there is a lot of activity on the virtual
machine at the time the snapshot is occurring. Try setting the
INCLUDE.VMSNAPSHOTATTEMPTS option to resolve this issue. Also, check the
VMware logs for possible causes of the error, and try the operation
again.

------------------------------------------------------------------------
ANS1153E

'drive-name1' is a cluster disk.



Explanation:

The indicated file system is a cluster disk. Because the CLUSTERNODE
option is set to NO, the file system cannot be backed up or archived.

System action:

Processing stops.

User response:

If the CLUSTERNODE option is incorrectly set to NO, then change the
option to YES and try the operation again. Otherwise see the client
manual for further information about configuring the client to run in a
cluster environment.

------------------------------------------------------------------------
ANS1154E

Object name 'filespace namepath-namefile-name' contains an invalid
multibyte sequence for the current locale.



Explanation:

An illegal multibyte sequence for the current locale was found in the
object name. Either the path or file name has been corrupted or is coded
in a language other than that of the current locale.

System action:

Object skipped.

User response:

If the file name and path are not corrupted, process the file in the
locale for which it is valid. In case of snapdiff backup, please contact
administrator to check environment and run full incremental backup after
the error is fixed.

------------------------------------------------------------------------
ANS1155E

No domain is available for image backup.



Explanation:

An image backup was started, but no domain was specified.

System action:

Processing stopped.

User response:

Choose a domain and restart the image backup. Set the image domain using
the domain.image option in your dsm.opt file, either manually, or by
using the GUI preferences editor.

------------------------------------------------------------------------
ANS1156E

NODENAME cannot be the local machine name when CLUSTERNODE is set to YES



Explanation:

When IBM Spectrum Protect is running as a cluster node, the node name
cannot be the local machine name.

System action:

Processing stops.

User response:

Change the node name either to the cluster name or to any other name,
and restart IBM Spectrum Protect.

------------------------------------------------------------------------
ANS1157E

The registry cannot be backed up or restored when the client is running
as a cluster node.



Explanation:

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

System action:

The registry is not backed up or restored.

User response:

If the CLUSTERNODE option is incorrectly set to YES, then change the
option to NO and try the operation again. Otherwise see the client
manual for further information about configuring the client to run in a
cluster environment.

------------------------------------------------------------------------
ANS1158E

The event logs cannot be backed up or restored when the client is
running as a cluster node.



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.

User response:

If the CLUSTERNODE option is incorrectly set to YES, then change the
option to NO and try the operation again. Otherwise see the client
manual for further information about configuring the client to run in a
cluster environment.

------------------------------------------------------------------------
ANS1159E

The specified file is being used by another process



Explanation:

The specified file is being used by another process. You tried to read
from or write to a file that is currently being used by another process.

System action:

Processing stopped.

User response:

Ensure that you specified the correct file or directory name, correct
the permissions, or specify a new location.

------------------------------------------------------------------------
ANS1162E

Filesystem could not be mounted



Explanation:

The system call to mount the file system failed.

System action:

The file system remains unmounted.

User response:

Use the mount command to mount the file system. On AIX, run fsck if
requested by the operating system.

------------------------------------------------------------------------
ANS1163E

Filesystem could not be unmounted.



Explanation:

The system call to unmount the file system failed.

System action:

The logical volume operation is not performed.

User response:

Make sure the device or file system is not being accessed, then retry
the operation.

------------------------------------------------------------------------
ANS1164E

Filesystem is not mounted



Explanation:

The named file system is not currently mounted. It must be mounted for
IBM Spectrum Protect to perform an image backup.

System action:

The logical volume operation is not performed.

User response:

Mount the file system.

------------------------------------------------------------------------
ANS1165E

Destination is smaller than source



Explanation:

The space allocation for the selected destination is smaller than the
source.

System action:

The restore operation is not performed.

User response:

Choose a different, bigger destination or increase the size of the
destination file space.

------------------------------------------------------------------------
ANS1166E

Source and destination are not the same file system type.



Explanation:

The source and destination file system types do not match.

System action:

The requested logical volume operation is not performed.

User response:

Choose a destination that has the same file system type as the source.

------------------------------------------------------------------------
ANS1168E

ERROR: could not create image object.



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.

System action:

The requested logical volume function is not performed.

User response:

Retry the operation after correcting the cause for failure.

------------------------------------------------------------------------
ANS1169W

There is no table of contents for image-name.



Explanation:

The image item for which a table of contents was requested is either a
RAW logical volume or it was backed up without the -TOC option.

System action:

No table of contents is displayed.

User response:

Select another image object for TOC display.

------------------------------------------------------------------------
ANS1170I

Invalid selection number entered. Try again.



Explanation:

A number not shown in the list of images was selected. It is either less
than one or greater than the highest item number displayed.

System action:

Client prompts for you to enter a valid selection.

User response:

Enter a number from the list or 'Q' to quit.

------------------------------------------------------------------------
ANS1177E

Must specify a path for this operation.



Explanation:

A path must be specified for this operation to execute successfully.

System action:

Processing stops.

User response:

Specify a valid path and execute the command again.

------------------------------------------------------------------------
ANS1181E

There was a communication failure with the journal service.



Explanation:

An error occurred using named pipe communication with the journal
service.

System action:

Processing stops.

User response:

Restart the journal service, then try the operation again. If the
problem persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1183E

An unknown error occurred while processing system object
'sys-obj-name':MS API function 'func-name' failed with error error
(error)



Explanation:

An unknown error occurred while processing a system object. The error
information captured indicates the reason for the failure. This
information can be used to diagnose the problem.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS1184W

The command subcommand command is not supported on this client.



Explanation:

The command subcommand command is not supported for the client running
on this operating system on this computer.

System action:

The command is not processed.

User response:

None.

------------------------------------------------------------------------
ANS1185E

The help search argument you supplied "string" is either too long or
contains unmatched quotes.



Explanation:

Valid arguments are the names of things like section numbers, command
names, option names and message numbers. All of these search arguments
are short and none requires quoting.

System action:

The help request is not executed and you are given another chance to
enter a valid argument, display the table of contents, or exit help.

User response:

Respond to the subsequent prompt as directed.

------------------------------------------------------------------------
ANS1186I

The named file does not have the content to support the help section.
Requests for message help will all result in topic not found. Enter a
section number, option name, command name, or a command and subcommand.
Otherwise press enter or 't' to display the table of contents or 'q' to
exit help:



Explanation:

Reinstall the product to correct the help file.

System action:

The help command pauses and allows you to make another selection.

User response:

During installation a proper help file was created. Your system
administrator can assist you with retrieving the original help file to
replace the named invalid file.

------------------------------------------------------------------------
ANS1187E

The named helpfile "filename" has invalid content.



Explanation:

Reinstall the product to correct the help file.

System action:

The help command is terminated.

User response:

During installation a proper help file was created. Your system
administrator can assist you with retrieving the original help file to
replace the named invalid file.

------------------------------------------------------------------------
ANS1188E

The selected filesystem is managed by HSM, and therefore is not a valid
object for image operations



Explanation:

Due to the nature of HSM, image backup is not allowed on managed
filesystems.

System action:

The requested logical volume operation is not performed.

User response:

None.

------------------------------------------------------------------------
ANS1189E

The DIRSONLY and V2ARCHIVE options are not valid together



Explanation:

The DIRSONLY and V2ARCHIVE options cannot be used together.

System action:

Processing stopped.

User response:

Try again using either the DIRSONLY or the V2ARCHIVE option.

------------------------------------------------------------------------
ANS1190E

Symbolic link 'linkname' to 'target' was successfully 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. To specify the location of log
files, refer to the user's manual for the 'errorlogname' option, the
'schedlogname' option, and the 'DSM_LOG' environmental variable.

------------------------------------------------------------------------
ANS1191E

Unable to delete symbolic link 'link'.



Explanation:

Log 'linkname' cannot be a symbolic link.

System action:

Processing stops.

User response:

Delete the symbolic link 'linkname'.

------------------------------------------------------------------------
ANS1192E

Specifying the error log 'link' as a symbolic link is not allowed.



Explanation:

Error log 'linkname' cannot be a symbolic link.

System action:

The symbolic link 'linkname' is deleted, the error log is recreated, and
processing stops.

User response:

Check the location of the new error log. To specify the location of the
error logs, refer to the user's manual for the 'errorlogname' option and
'DSM_LOG' environmental variable.

------------------------------------------------------------------------
ANS1193E

Specifying the trace file 'link' as a symbolic link is not allowed.



Explanation:

For reasons of security and system integrity, the trace file 'linkname'
cannot be a symbolic link.

System action:

The symbolic link 'linkname' is deleted, the trace file is recreated,
and processing stops.

User response:

Use the TRACEFILE option to specify the actual trace file location
without the use of symbolic links.

------------------------------------------------------------------------
ANS1194E

The VMware vStorage API reported another task was in progress for the
virtual machine.



Explanation:

A VMware vStorage API error occurred due to another task in progress for
the virtual machine.

System action:

A VMware vStorage API error occurred, and the virtual machine backup
failed.

User response:

Wait for the other task to complete and try the operation again.

------------------------------------------------------------------------
ANS1197E

A VMware Virtual Disk Kit (VDDK) API read failure occurred while reading
data for backup.



Explanation:

There was a VMware Virtual Disk Kit (VDDK) API read error while reading
data to backup.

System action:

A VMware Virtual Disk Kit (VDDK) API read error occurred, and the
virtual machine backup failed.

User response:

Check the VMware logs for possible causes of the read error, and try the
operation again.

------------------------------------------------------------------------
ANS1198E

The VMware Virtual Disk Kit (VDDK) API reported an out-of-memory
condition while reading data for backup.



Explanation:

A VMware Virtual Disk Kit (VDDK) API read error occurred due to
out-of-memory condition while reading data to backup.

System action:

A VMware Virtual Disk Kit (VDDK) API read error occurred. The virtual
machine backup failed.

User response:

Check the VMware logs for possible causes of the read error, and try the
operation again.

------------------------------------------------------------------------
ANS1199E

The PRESNAPSHOTCMD command failed. The image snapshot backup will not be
executed.



Explanation:

The command specified by the PRESNAPSHOTCMD option must complete
successfully in order to execute the image snapshot backup. If the
command completed with a return code of 0 (zero), it is considered to
have completed successfully. If the command completed with any other
return code, it is considered to have failed. If the command failed then
the image snapshot backup is not executed.

System action:

The client does not execute the image snapshot backup operation.

User response:

Identify and repair the problem that caused the command to fail. If a
non-zero return code is normal for this command, then consider wrapping
the command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS1200W

The POSTSNAPSHOTCMD command completed with a non-zero return code.



Explanation:

If the command specified by the POSTSNAPSHOTCMD option completed with a
non-zero return code, then the image snapshot backup operation will
continue, but with a warning-level result. Note that the result of the
POSTSNAPSHOTCMD command will not supercede a higher result from the
image snapshot backup command. For example, if the image snapshot backup
command completed with a return code of 12, the image snapshot backup
will be considered to have completed with a return code of 12,
regardless of the outcome 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 code is normal for this command, then consider wrapping
the command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS1201E

IBM Spectrum Protect cannot build a directory path because a file exists
with the same name as the directory.



Explanation:

None

System action:

Processing stopped.

User response:

Remove or rename the file that has the same name as the directory.
Alternatively, you can restore the directory to a different location.

------------------------------------------------------------------------
ANS1202E

TOC backup for the image failed. Check log files.



Explanation:

An error occurred during backup of the table of contents. Check the
error log for more information.

System action:

The requested logical volume operation is not performed.

User response:

Check error log.

------------------------------------------------------------------------
ANS1203E

Table of Contents not available for selected backup set. Please contact
server administrator.



Explanation:

There is no TOC for selected backup set

System action:

Expansion of selected backup set will not be possible. Will only be able
to restore the whole backup set.

User response:

Please contact server administrator to regenerate TOC for backup set
before backup set can be expanded.

------------------------------------------------------------------------
ANS1204E

This client is not supported by the IBM Spectrum Protect express server



Explanation:

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

1. the client is configured as an IBM Spectrum Protect express client
   using the CLIENTVIEW option

2. the client is trying to connect to an IBM Spectrum Protect express
   server.

System action:

Processing stops.

User response:

Log in using a supported IBM Spectrum Protect express client.

------------------------------------------------------------------------
ANS1205E

This is not a supported IBM Spectrum Protect express platform



Explanation:

This is not a supported IBM Spectrum Protect express platform.

System action:

Processing stops.

User response:

Log in using a supported IBM Spectrum Protect express client.

------------------------------------------------------------------------
ANS1206E

TOC backup of a raw device is not supported. But the raw device is
backed up.



Explanation:

TOC backup of a raw device is not supported. But the raw device is
backed up.

System action:

Raw device is backed up with no TOC object.

User response:

NONE.

------------------------------------------------------------------------
ANS1207E

No TOC has been previously backed up for this file system.



Explanation:

The user is trying to query the TOC of a file system. TOC backup for
that file system has not been previously done.

System action:

Query stopped.

User response:

Backup the file system again with -TOC option.

------------------------------------------------------------------------
ANS1209E

The option_name option is not supported with the command_name command
using the -FILELIST option.



Explanation:

The specified option is not supported with the specified command when
the -FILELIST option is also specified.

System action:

The command is not processed.

User response:

>Do not specify the offending option when the -FILELIST option is
specified with this command.

------------------------------------------------------------------------
ANS1212I

Invalid Process number entered. Try again.



Explanation:

A number not shown in the list of processes was selected. It is either
less than one or greater than the highest item number displayed.

System action:

Client prompts for a valid selection.

User response:

Enter a number from the list or 'Q' to quit.

------------------------------------------------------------------------
ANS1213W

Snapshot image backup is not possible for device device-name. starting
static image backup.



Explanation:

On Linux platforms, snapshot image backup is only possible for logical
volumes created by the Linux logical volume manager (LVM). Since the
default image backup type is snapshot, backing up a partition which is
not created using LVM automatically leads to a static image backup.

System action:

Snapshot image backup will failover to static image backup

User response:

To avoid this message, use the imagetype option to specify static or
dynamic image backup.

------------------------------------------------------------------------
ANS1214E

The logical volume group does not have enough free space to contain the
volume snapshot.



Explanation:

The snapshot is created in the volume group that contains the logical
volume being backed up. There is insufficient free space in the volume
group to contain the snapshot.

System action:

The operation ends.

User response:

Decrease the SNAPSHOTCACHESIZE value or make additional space available
in the logical volume group. Then try the operation again.

------------------------------------------------------------------------
ANS1215E

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



Explanation:

When the snapshot cache location is located on the same volume that is
being backed up the volume must be formatted with NTFS. The default
cache location is on the same volume where the snapshot is being
performed.

System action:

The client does not execute the image snapshot backup operation.

User response:

Specify a different snapshot cache location using the
SNAPSHOTCACHELOCATION option.

------------------------------------------------------------------------
ANS1216E

Not authorized to run IBM Spectrum Protect. See the administrator for
your system.



Explanation:

The system options file for the server that you are attempting to
connect to contains a user entry, a group entry, or both a user and
group entry. Your user ID, or group ID, was not found in any of the
entries. You are currently not authorized to run IBM Spectrum Protect to
this server.

System action:

IBM Spectrum Protect initialization fails and the program ends.

User response:

See the IBM Spectrum Protect administrator for your system, and ask to
be added to the user or group list for this server.

------------------------------------------------------------------------
ANS1217E

Server name not found in System Options File



Explanation:

The system options file does not contain the SERVERNAME option.

System action:

IBM Spectrum Protect initialization fails and the program ends.

User response:

See the IBM Spectrum Protect administrator for your system, and make
sure that the system options file contains the server name.

------------------------------------------------------------------------
ANS1218E

TCPSERVERADDRESS not defined for this server in the System Options File



Explanation:

The TCPSERVERADDRESS for this server is not defined in the server name
stanza in the system options file.

System action:

IBM Spectrum Protect initialization fails and the program ends.

User response:

See the IBM Spectrum Protect administrator for your system, and make
sure that the server to which you are trying to connect, has a valid
TCPSERVERADDRESS defined in the system options file.

------------------------------------------------------------------------
ANS1219E

A virtual node name must not equal either a node name or the system host
name.



Explanation:

A VIRTUALNODENAME option was entered with a name the same as either a
NODENAME option or the system host name.

System action:

Initialization fails and the program ends.

User response:

If the virtual node name entered was the same as the host name, remove
the virtual node name option. If it was the same as the node name
option, you can remove either one, depending upon the intended usage.
Node name is used to assign an alternate name to your system. Virtual
node name is used to access another system's server data.

------------------------------------------------------------------------
ANS1220E

The IBM Spectrum Protect server is out of resources.



Explanation:

A lack of a storage resource or a maximum value condition does not allow
any new activity.

System action:

Current operation has been cancelled.

User response:

Try the operation again at a later time. If the problem continues,
contact your IBM Spectrum Protect administrator to isolate what resource
is unavailable. The IBM Spectrum Protect administrator can check the IBM
Spectrum Protect server activity log for messages that might explain the
problem.

------------------------------------------------------------------------
ANS1221E

Transaction aborted



Explanation:

The current transaction between the server and the client stopped. A
server, client, or communication failure cannot be recovered.

System action:

Current operation has been cancelled.

User response:

Retry the operation. If the problem continues, see your system
administrator to isolate the problem.

------------------------------------------------------------------------
ANS1222E

Disk space limit for this process reached



Explanation:

The disk space allocated for the client owner is full.

System action:

Processing stopped.

User response:

Free up disk space and retry the restore or retrieve operation.

------------------------------------------------------------------------
ANS1223E

File is not compressed; System failure.



Explanation:

A file that was flagged as compressed was not compressed, and the system
failed.

System action:

Processing stopped.

User response:

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

------------------------------------------------------------------------
ANS1224E

File compressed on a different client machine that has more memory



Explanation:

You are trying to restore a file that was backed up and compressed on
another client workstation that had more memory than your client
workstation. You cannot restore this file. When the file is restored, it
is expanded and your workstation does not have enough memory.

System action:

Current operation has been cancelled.

User response:

Obtain a machine with more memory and retry the operation.

------------------------------------------------------------------------
ANS1225E

Insufficient memory for file compression/expansion



Explanation:

Not enough memory is available to do data compression or expansion. For
a restore or retrieve, the file cannot be recalled from the server until
more storage is made available. For a backup or archive, try running
without compression if storage cannot be made available.

System action:

Processing stopped.

User response:

Free up extra storage for the operation to continue, or run the backup
or archive process without compression enabled.

------------------------------------------------------------------------
ANS1226E

Destination file or directory is write locked



Explanation:

The file or directory being restored or retrieved from the server cannot
be written to because the destination is write locked. Another operation
might have the file open and will not allow it to be updated.

System action:

File skipped.

User response:

Either determine which operation has the file write locked, or restore
the file to another name or location.

------------------------------------------------------------------------
ANS1227E

Processing stopped; Disk full condition



Explanation:

No more files can be restored or retrieved because the destination disk
is full.

System action:

Processing stopped.

User response:

Free up disk space, or restore or retrieve the file to another disk.

------------------------------------------------------------------------
ANS1228E

Sending of object 'object-nameobject-nameobject-name' failed.



Explanation:

The specified file (object-name) cannot be sent to the server. This
message is accompanied by at least one other message that has more
specific information about why the file could not be processed.

System action:

File skipped.

User response:

Check previous messages pertaining to this file that indicate the reason
for the failure. Where applicable, correct the conditions that prevented
the file from being sent to the server. The specific corrective actions
will depend on the reason for the failure.

------------------------------------------------------------------------
ANS1229E

MODE=INCREMENTAL is not valid on file-space. Image backup not processed.



Explanation:

Because the file space has been the subject of at least one progressive
incremental backup, the MODE=INCREMENTAL option (incremental by image
date) cannot be used with the backup image command.

System action:

File system skipped.

User response:

If an image backup of the named file space is desired, retry the command
without the MODE=INCREMENTAL option. To prevent this behavior in the
future, delete the file space from the server and do only BACKUP IMAGE
-mode=selective and BACKUP IMAGE -mode=incremental from that point on.

------------------------------------------------------------------------
ANS1230E

Stale NFS File Handle



Explanation:

An NFS file system becomes stale.

System action:

File system skipped.

User response:

Check the NFS mounted filesystem.

------------------------------------------------------------------------
ANS1231E

No file handles available



Explanation:

All file handles for your system are currently in use. No more are
available.

System action:

Processing stopped.

User response:

Either free some file handles by ending other processes, or modify your
system setup to allow for more files to be open at the same time.

------------------------------------------------------------------------
ANS1232E

The file exists and cannot be overwritten.



Explanation:

The file being restored or retrieved exists and cannot be overwritten
due to lack of authority or access permissions.

System action:

The file is skipped.

User response:

Verify that you have sufficient access permissions to overwrite the
file, then try the operation again. If the problem persists, contact
your system administrator or IBM Spectrum Protect administrator for
further assistance.

------------------------------------------------------------------------
ANS1233E

An invalid file handle was passed; system error.



Explanation:

An internal system error occurred: A file operation failed because of an
invalid file handle.

System action:

processing stops.

User response:

Try the operation again. If the failure persists, obtain a service trace
that captures the problem and contact IBM technical support for
additional assistance. Your IBM Spectrum Protect administrator can help
you configure the trace.

------------------------------------------------------------------------
ANS1234E

Protocol violation



Explanation:

A communications protocol error occurred. The communication subsystem is
not properly defined or is itself in error.

System action:

Processing Ends.

User response:

Verify that the communication processes are operating properly, and then
retry the operation.

------------------------------------------------------------------------
ANS1235E

An unknown system error has occurred from which IBM Spectrum Protect
cannot recover.



Explanation:

An unknown error occurred. This might be a low-level system or
communication error from which IBM Spectrum Protect cannot recover.

System action:

Processing stops.

User response:

Try the operation again. If the problem persists, review the IBM
Spectrum Protect error log for any related messages. Obtain a service
trace that captures the problem and contact IBM technical support for
additional assistance. Your IBM Spectrum Protect administrator can help
you configure the trace.

------------------------------------------------------------------------
ANS1236E

An unexpected error occurred.



Explanation:

This is usually caused by a low-level system error or communication
error from which IBM Spectrum Protect cannot recover.

System action:

Processing stopped.

User response:

Examine the client error log for any additional messages that might be
related to this problem. Try the operation again. If the problem
persists, contact IBM Spectrum Protect technical support for further
assistance.

------------------------------------------------------------------------
ANS1237E

A problem has occurred on the IBM Spectrum Protect server.



Explanation:

The client error log and the IBM Spectrum Protect server activity log
might contain additional information about this error.

System action:

Processing stops.

User response:

Try the operation again. If the problem persists, examine the client
error log and IBM Spectrum Protect server activity log for additional
information about this error. If the problem cannot be resolved, then
obtain a SERVICE trace that captures the problem and contact IBM
technical support for additional assistance. Your IBM Spectrum Protect
administrator can help you configure the trace.

------------------------------------------------------------------------
ANS1238S

A policy management problem has occurred on the IBM Spectrum Protect
server.



Explanation:

The client error log and IBM Spectrum Protect server activity log may
contain additional information about this error.

System action:

Processing is stops.

User response:

Try the operation again. If the problem persists, examine the client
error log and IBM Spectrum Protect server activity log for additional
information about this error. If the problem cannot be resolved, then
obtain a SERVICE trace that captures the problem and contact IBM
technical support for additional assistance. Your IBM Spectrum Protect
administrator can help you configure the trace.

------------------------------------------------------------------------
ANS1241E

File is in use; Write permission denied.



Explanation:

The current file cannot be opened to write to because it is currently
being run by another operation.

System action:

File skipped.

User response:

Stop the operation that is running the file and retry the operation, or
restore or retrieve the file to a different name or directory.

------------------------------------------------------------------------
ANS1242E

Too many symbolic links were detected while resolving name



Explanation:

While trying to resolve the file name, too many symbolic links were
found.

System action:

File skipped.

User response:

Ensure that you do not have a looping symbolic link for the file.

------------------------------------------------------------------------
ANS1243E

The file name is too long and can not be processed by IBM Spectrum
Protect



Explanation:

The size limit for file names may vary by operating system. The most
common limit is 256 characters. The file name being processed exceeds
the limit supported by IBM Spectrum Protect on this system.

System action:

The file is skipped.

User response:

Enter HELP FILE SPEC or see the client manual for the operating system
on which you are receiving this error. The "File specification syntax"
section of the manual explains file name lengths supported by IBM
Spectrum Protect.

------------------------------------------------------------------------
ANS1244E

File system is locked by system



Explanation:

File system cannot be accessed because it is locked by the system.

System action:

The operation cannot be completed.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1245E

The file has an unknown format.



Explanation:

The process tried to restore or retrieve a file, but it had an unknown
format.

System action:

The file is skipped.

User response:

The file was either backed up by another application, or the data is
invalid. If the file belongs to this system, try the operation again. If
the problem persists, contact IBM technical support for further
assistance.

------------------------------------------------------------------------
ANS1246E

A command-line argument exceeded the maximum length (maximum length) for
a single token.



Explanation:

Command-line arguments may not exceed maximum length characters.

System action:

The command is not processed.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1247I

Waiting for files from the server...



Explanation:

Restore request has been sent to the server. The wait time depends on
how many files you are restoring.

System action:

IBM Spectrum Protect waits for files to restore from the server.

User response:

None.

------------------------------------------------------------------------
ANS1248E

An active restore for the same source file specification exists. Unable
to continue with this request.



Explanation:

Currently, there is an active restore for the same source file
specification. Another restore of the same source file specification
cannot be started.

System action:

The requested restore fails.

User response:

Start another restore with a different source file specification.

------------------------------------------------------------------------
ANS1249W

Server cannot restart the last restore request. Do you want to restore
without restart or abort the request?



Explanation:

The restart restore token has expired. The server cannot restart the
restore from where it last ended.

System action:

Processing stopped; waiting for user intervention.

User response:

Retry the request without restart or abort the request.

------------------------------------------------------------------------
ANS1251E

File system/drive not ready



Explanation:

The file system/drive was not ready for access.

System action:

Processing stopped.

User response:

Ensure that the drive is available , and then retry the operation.

------------------------------------------------------------------------
ANS1252W

The server that you are connected to does not support this function.



Explanation:

You attempted to run a backup-archive client operation when connected to
the virtual server. Backup-archive client operations are not supported
when connected to the virtual server.

System action:

The operation fails.

User response:

Connect to a valid server before attempting this function.

------------------------------------------------------------------------
ANS1253E

File input/output error



Explanation:

An error was found while reading from or writing to the file.

System action:

File or file system is skipped.

User response:

Check your system to ensure that it is operating properly. For OS/2, run
CHKDSK /F for the failing drive which can be found in dsmerror.log.

------------------------------------------------------------------------
ANS1254E

File write error



Explanation:

An error was found while writing to the file.

System action:

File skipped.

User response:

Check your system to ensure that it is operating properly.

------------------------------------------------------------------------
ANS1255E

File exceeds system/user file limits



Explanation:

A file being restored or retrieved exceeds system set limits for this
user.

System action:

File skipped.

User response:

Ensure that the system limits are set properly.

------------------------------------------------------------------------
ANS1256E

Cannot make file/directory



Explanation:

The directory path for files being restored or retrieved cannot be
created.

System action:

File skipped.

User response:

Ensure that you have the proper authorization to create the directory
for file being restored or retrieved. Make sure that you have write
access.

------------------------------------------------------------------------
ANS1257E

An error occurred while preparing the system object for restore.



Explanation:

This message is typically issued when the client is unable to delete the
ADSM.SYS staging directory 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 operation
again. If the problem occurs again, manually delete the ADSM.SYS
directory, then try the operation again. If the problem cannot be
resolved, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1258E

The image snapshot operation failed.



Explanation:

The process was not able to take a snapshot of the specified volume.

System action:

Processing stopped.

User response:

Check the error log for any other messages that might indicate a reason
for the failure. Try to correct any indicated problems, then try the
operation again. If the problem persists, contact IBM technical support
for further assistance.

------------------------------------------------------------------------
ANS1259E

The image snapshot operation failed. Diagnostic text: diag_text.



Explanation:

An error was encountered during image backup snapshot processing. The
diagnostic text can vary, depending on the error.

System action:

The operation ends.

User response:

Examine the client error log for additional messages that might indicate
the reason for the problem. Take any corrective action suggested by the
messages, then try the operation again. If the problem persists, contact
IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1260E

File is being recalled or has been recalled.



Explanation:

The file is being recalled by another process or has been recalled.

System action:

File skipped.

User response:

None

------------------------------------------------------------------------
ANS1261W

The archive description you specified is the empty string. The process
will use the default description (Archive Date: current date).



Explanation:

The description option on the archive command may not specify a null
string.

System action:

Processing continues, and the description option is ignored.

User response:

None. Specify at least one character in the description

------------------------------------------------------------------------
ANS1262E

The password is not updated. Either an invalid current password was
supplied or the new password does not fulfill the server password
requirements.



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.

System action:

The password is not updated on the server.

User response:

Enter another password.

------------------------------------------------------------------------
ANS1263E

The active policy set does not contain any backup copy groups. The
backup operation can not continue.



Explanation:

In order to back up files, the policy set must contain at last one
backup copy group.

System action:

IBM Spectrum Protect did not backup the file.

User response:

The IBM Spectrum Protect administrator needs to update or define at
least one management class in your policy set that contains a backup
copy group, or else assign you to a different policy domain that
contains at least one backup copy group. Contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1264E

The active policy set does not contain any archive copy group. The
archive operation cannot continue.



Explanation:

In order to archive files, the policy set must contain at least one
archive copy group.

System action:

IBM Spectrum Protect did not archive the file.

User response:

The IBM Spectrum Protect administrator needs to update or define at
least one management class in your policy set that contains an archive
copy group, or else assign you to a different policy domain that
contains at least one archive copy group. Contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1265E

Encountered bad mount or filesystem, processing stopped.



Explanation:

The getmnt system call returned an error indication. Error was
encountered trying to determine what the mounted file systems are.

System action:

Processing stopped. Cannot recover.

User response:

There is a bad file system or mount point on your system. Look at file
systems and mounts, and correct any errors. If unsuccessful, see your
system administrator for more information.

------------------------------------------------------------------------
ANS1266E

Encountered bad mount or filesystem, processing stopped.



Explanation:

An error was encountered trying to determine what the mounted file
systems are.

System action:

Processing stopped. Cannot recover.

User response:

Please, see your system administrator for more information.

------------------------------------------------------------------------
ANS1267E

The management class for file file-name does not allow migration. This
file will not be migrated.



Explanation:

The management class for this file does not allow migration

System action:

File is skipped.

User response:

Either have the IBM Spectrum Protect administrator change the Space
Management Technique within the management class to a value other than
NONE or change the include/exclude list to specify a management class
with the appropriate Space Management Technique value.

------------------------------------------------------------------------
ANS1268E

This file has been migrated.



Explanation:

The error can result from migrating a file with hard links. After a file
with hard links is migrated, attempts to migrate the alias files yield
an error.

System action:

The file is skipped.

User response:

If this error is not a result of a hard linked file migration, then this
error might be due to the previous cancelled migration or recall
operation. In this case, restart the dsmrecalld daemon and try the
operation again.

------------------------------------------------------------------------
ANS1269I

File is implicitly excluded.



Explanation:

You tried to back up or migrate a file that is implicitly excluded.

System action:

IBM Spectrum Protect will not back up or migrate an implicitly excluded
file.

User response:

None.

------------------------------------------------------------------------
ANS1270E

Running this command requires a valid NetApp Snapshot Differential
c-mode license file.



Explanation:

A NetApp Snapshot Differential c-mode license file either does not exist
or is not valid.

System action:

Processing stops.

User response:

Contact IBM support.

------------------------------------------------------------------------
ANS1271E

The compressed file is corrupted and cannot be expanded correctly.



Explanation:

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 Spectrum Protect Server.

System action:

File skipped.

User response:

1) The compressed file is corrupted because there is a problem on the
tape. To know if this is the problem, please issue the following command
on the IBM Spectrum Protect Server: audit volume <volume_name> fix=no If
there is any problem reported, you could move the data from that volume
to a new one (see command MOVE DATA) and try again the restore. 2) There
are communications problems between the IBM Spectrum Protect Server and
the IBM Spectrum Protect Client and the results is that the file is
corrupted during the transmission. If you use a gigabit Ethernet adapter
on the Server please upgrade the card driver (AIX platform) or add
provided by SUN suggested changes to some system network options which
have resolved this problem (SUN platform). 3) Please verify with your
network support if during the restore there are no any problems between
the IBM Spectrum Protect Client/Server that is originating the file
corruption.

------------------------------------------------------------------------
ANS1272W

Adaptive subfile backup has been configured on the client but the server
doesn't allow this type of backup. Adaptive subfile backup will not be
used for this operation.



Explanation:

Adaptive subfile backup forced off by the server.

System action:

Processing continues.

User response:

Set up the server to allow clients to back up subfiles.

------------------------------------------------------------------------
ANS1273I

Microsoft Windows hotfix 'hotfix-number' is not installed.



Explanation:

This message is issued On Windows 7, Windows Server 2008 R2, Windows
Vista, and Windows Server 2008. This hotfix is known to release new API
enhancements for Windows to help correctly and securely load external
libraries. Visit the Microsoft support page http://support.microsoft.com
for more information about the hotfix.

System action:

Processing continues.

User response:

On Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server
2008 you must apply the package KB2533623 prior to performing the
Snapshot dirrerential backup. If backup-archive client operations that
use OpenSSL do not complete successfully due to OpenSSL related errors,
install the hotfix, then try the operation again.

------------------------------------------------------------------------
ANS1274E

Error Loading WINSOCK.DLL



Explanation:

Error loading the Windows socket support file into memory. This error
only applies when using TCP/IP communications.

System action:

Connection to server fails.

User response:

Because this error is caused by insufficient memory, shut down running
applications and retry. If the problem persists, see your system
administrator.

------------------------------------------------------------------------
ANS1275E

Error Loading Function(s) from WINSOCK.DLL



Explanation:

Error loading one or more functions from the Windows socket support
file.

System action:

Connection to server fails.

User response:

Since this might possibly be caused by insufficient memory, shut down
running applications and retry. If the problem persists, see your system
administrator.

------------------------------------------------------------------------
ANS1276E

Virtual Machine backup corruption detected. The filespace on the IBM
Spectrum Protect server must be deleted.



Explanation:

Due to APAR IT22660, the backup on the IBM Spectrum Protect server is
corrupt.

System action:

The backup of the virtual machine is skipped.

User response:

Request the IBM Spectrum Protect administrator delete or rename the
virtual machine on the IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS1277E

The VMware vStorage API reported that a file was not found for the
virtual machine.



Explanation:

A VMware vStorage API error occurred due to a file not found on the
virtual machine.

System action:

A VMware vStorage API error occurred, and the virtual machine backup
failed.

User response:

Check the VMware logs for possible causes of the error, and try the
operation again.

------------------------------------------------------------------------
ANS1278W

Virtual mount point 'filespace-name' is a file system. It will be backed
up as a file system.



Explanation:

A virtual mount point that is a file system is invalid and should be
deleted.

System action:

The virtual mount point is ignored.

User response:

Delete the virtual mount point.

------------------------------------------------------------------------
ANS1279W

Virtual mount point 'filespace-name' cannot be used in a file system
handled by automounter and is ignored.



Explanation:

Virtual mount points cannot be used in a file system handled by
automounter. If virtual mount points reside in a file system that is
processed from an automounter, the backed up files underneath the
virtual mount points will be expired when the file system is unmounted.

System action:

The virtual mount point is ignored.

User response:

Delete the virtual mount point.

------------------------------------------------------------------------
ANS1286E

-nasnodename option required for this operation.



Explanation:

User issued a NAS related command and NASNodename option is missing.

System action:

Operation aborted.

User response:

Use -nasnodename option with the command or place nasnodename option in
the option file.

------------------------------------------------------------------------
ANS1287E

Volume could not be locked.



Explanation:

The system call to lock the volume failed.

System action:

Processing stopped.

User response:

Please verify that no other application is accessing the volume. If this
volume is being accessed by applications that can not be shutdown during
backup then perform an online image backup (snapshot) instead. During
restore of an image IBM Spectrum Protect must have exclusive use of the
volume.

------------------------------------------------------------------------
ANS1288E

The (-TYPE) option is required with the SET EVENT command.



Explanation:

There is no default value for the -TYPE option. It must be explicitly
entered with the command.

System action:

The current command ends.

User response:

Enter the SET EVENT command again with the TYPE option and a value of
HOLD, RELEASE, or ACTIVATERETENTION.

------------------------------------------------------------------------
ANS1289W

Bad areas on 'volume' between sectors hi:lo and hi:lo



Explanation:

Some bad sectors within the specified range were detected on the volume
during image operation.

System action:

Processing continues.

User response:

Make sure the volume data is not corrupt by using system tools like
chkdsk (Windows) or fsck (UNIX).

------------------------------------------------------------------------
ANS1299E

Unable to generate an encryption key for storing password



Explanation:

You tried to start an operation that led to storing password on the IBM
Spectrum Protect client side but the client was unable to generate an
encryption key very likely due to a configured FIPS-enabled operating
system environment.

System action:

Processing stops.

User response:

The IBM Spectrum Protect client doesn't support the Federal Information
Processing Standard (FIPS) enabled operating system environmnet for
locally stored passwords. See your system administrator for assistance
in reconfiguring the FIPS-enabled operating system environment. For more
details on FIPS support, see the following techdoc:
http://www-01.ibm.com/support/docview.wss?uid=swg22007756

------------------------------------------------------------------------
ANS1300E

File 'file_name' cannot be reconstructed because a necessary component
was not restored.



Explanation:

The subfile backup technique was used to back up this file. During the
restore, a portion of the file was not be obtained from the server.

System action:

The file indicated in the message is not restored. Restore for all other
files continues.

User response:

Try to restore the file again by selecting the file for restore from the
user interface. You can also check the client error log and the server
activity log for any messages related to the file indicated in the
message.

------------------------------------------------------------------------
ANS1301E

This operation cannot continue due to an error on the IBM Spectrum
Protect server. See your IBM Spectrum Protect server administrator for
assistance.



Explanation:

The IBM Spectrum Protect server encountered an error condition that
prevents the IBM Spectrum Protect client operation from continuing. Your
IBM Spectrum Protect server administrator can review the IBM Spectrum
Protect server activity log for more details about the error.

System action:

Processing stopped.

User response:

Contact your IBM Spectrum Protect server administrator for assistance.
The administrator can review the IBM Spectrum Protect server activity
log for further information about the conditions that lead to this
error.

------------------------------------------------------------------------
ANS1302E

No objects on server match query



Explanation:

No objects on the server match the query operation being performed. If
this object is part of a backupset generated on a node, and the node
name is changed on the server, any backup set objects that were
generated prior to the name change will not match the new node name.

System action:

Processing stopped.

User response:

Ensure the names are properly entered. If the object is part of a
backupset generated prior to a node name change, ensure that the node
name is the same as the node for which the backup set was generated.

------------------------------------------------------------------------
ANS1303E

Client ended transaction



Explanation:

The client system ended the operation with the server and ended the
current transaction.

System action:

Processing stopped.

User response:

Restart the session.

------------------------------------------------------------------------
ANS1304W

An active backup version could not be found.



Explanation:

An attempt was made to expire an object, but the IBM Spectrum Protect
server was unable to find an active backup version of the object. This
message is preceded by message ANS1228E which specifies the object name.
For instance, this message could be issued if two separate client
processes are backing up the same file system at the same time. If one
of the processes expires a file, then the IBM Spectrum Protect server
will make that file inactive. If the second process subsequently
attempts to expire that same file, the IBM Spectrum Protect server will
not find an active version of the file, so the second process will issue
this message for that file.

System action:

The object is not expired. Processing continues with the next object.

User response:

*  Review the console output, schedule log, or error log and locate the
   ANS1228E message that immediately precedes this message. ANS1228E
   will identify the object that could not be expired.

*  Examine the conditions under which the problem occurred and assess
   whether those conditions explain the occurrence of this message. For
   example, this message could appear if multiple instances of the
   client were attempting to back up the file system concurrently.

*  If the reason this message occurred can not be determined and the
   message occurs when the operation is tried again, then contact IBM
   support for further assistance. Also try searching for this message
   number on http://www.ibm.com for possible solutions.

------------------------------------------------------------------------
ANS1305E

The IBM Spectrum Protect server has no data for the object.



Explanation:

IBM Spectrum Protect tried to do a restore or retrieve on an object that
has no data associated with it. If a corrective action is possible, it
is with the IBM Spectrum Protect server.

System action:

IBM Spectrum Protect ends the current operation.

User response:

Ask the IBM Spectrum Protect administrator to check the IBM Spectrum
Protect activity log for any messages related to this error that might
help identify the problem.

------------------------------------------------------------------------
ANS1306E

You entered an incorrect password.



Explanation:

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

System action:

Processing stops.

User response:

Retry the session with the correct password. If this fails or you have
forgotten your password, ask the IBM Spectrum Protect administrator to
assign a new password.

------------------------------------------------------------------------
ANS1307E

Node in use



Explanation:

The node you are running on is in use by another operation on the
server. This might be from another client or from some activity on the
server.

System action:

Processing stopped.

User response:

Retry the operation, or see your system administrator to see what other
operations are running for your node.

------------------------------------------------------------------------
ANS1308E

Expiration date must be greater than today's date



Explanation:

Archive expiration date is too low, the date must be greater than
today's date.

System action:

IBM Spectrum Protect canceled the current operation.

User response:

Retry archiving the file with an expiration date that is higher than
today's date.

------------------------------------------------------------------------
ANS1309I

The requested data is offline.



Explanation:

For the restore or retrieve operation, one or more of the requested
files must be recalled from offline storage media (generally tape). The
wait time depends on your site's offline storage management policies.

System action:

IBM Spectrum Protect waits for offline storage media to become available
and then continues.

User response:

None.

------------------------------------------------------------------------
ANS1310E

Object too large for server limits



Explanation:

The object is too large. The configuration of the server does not have
any data storage space that accepts the object.

System action:

File skipped.

User response:

See your system administrator to determine the maximum file (object)
size for which your site's server is configured.

------------------------------------------------------------------------
ANS1311E

Server out of data storage space



Explanation:

The server does not have any space available to store the object.

System action:

Processing Ends.

User response:

You can take any of the following actions:

*  Request the system administrator to add space to the storage pool.

*  For IBM Spectrum 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.

------------------------------------------------------------------------
ANS1312E

Server media mount not possible



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.

------------------------------------------------------------------------
ANS1313E

Size estimate exceeded



Explanation:

The total amount of data for a backup or archive operation exceeds the
estimated size originally sent to the server for allocating data storage
space. This happens when many files are growing by large amounts while
the backup or archive operation is in session.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, check what other
processes are running on the client machine that are generating large
amounts of data. Disable those operations while the backup or archive
operation is taking place.

------------------------------------------------------------------------
ANS1314E

File data currently unavailable on server



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:

Processing stopped.

User response:

Retry the operation. If the problem continues, see your system
administrator to determine the problem from the server console or the
activity log. Check whether any requests were made for a tape volume
that was unavailable. A tape volume may be marked unavailable if prior
read errors were encountered or the volume is checked out of the tape
library.

------------------------------------------------------------------------
ANS1315W

Unexpected retry request. The IBM Spectrum Protect server found an error
while writing the data.



Explanation:

None.

System action:

If the current operation supports another attempt, the client tries the
operation again. Otherwise, processing stops.

User response:

None.

------------------------------------------------------------------------
ANS1316E

The server does not have enough recovery log space to continue the
current operation



Explanation:

The server ran out of recovery log space.

System action:

Processing ends.

User response:

This error is a temporary problem. Retry later or see your system
administrator.

------------------------------------------------------------------------
ANS1317E

The server does not have enough database space to continue the current
operation



Explanation:

The server ran out of database space.

System action:

Processing ends.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1318E

The server does not have enough memory to continue the current
operation.



Explanation:

The server ran out of memory.

System action:

Processing ends.

User response:

This is a temporary problem. Retry later or see your system
administrator.

------------------------------------------------------------------------
ANS1319E

An error occurred on the IBM Spectrum Protect server while trying to
rename file space file_space_name



Explanation:

None.

System action:

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

User response:

Check the client error log and the IBM Spectrum Protect server activity
log for any other messages that might help identify the problem. If the
problem cannot be resolved, contact IBM technical support for additional
assistance.

------------------------------------------------------------------------
ANS1320E

The specified file space does not exist on the server. The file space
might have been deleted by another client or an administrator.



Explanation:

The specified file space does not exist on the server. Your system
administrator deleted the file space or another client using your
client's node name deleted it.

System action:

Current operation has been cancelled.

User response:

Check the file space name to see if it is correct, and retry the
operation.

------------------------------------------------------------------------
ANS1321S

Open Registration failed because the specified node name is defined in
the server



Explanation:

Open registration failed because a node is defined in the server with
the same name.

System action:

Current operation has been cancelled.

User response:

Retry with another node name.

------------------------------------------------------------------------
ANS1322S

Open Registration failed because no default domain exists



Explanation:

Open registration failed because a default policy domain does not exist
for you to place your node.

System action:

Current operation has been cancelled.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1323S

Open Registration failed because an invalid node name was specified



Explanation:

Open registration failed because the specified node name contains
invalid characters.

System action:

Current operation has been cancelled.

User response:

Retry with another node name that does not have any invalid characters.

------------------------------------------------------------------------
ANS1326S

The IBM Spectrum Protect server does not currently have space in the
storage pool for this file. This may be a temporary condition.



Explanation:

This message is typically issued when the storage pool in which the data
is being placed does not have sufficient space to store the data, but
the space will be available soon. For example, a storage pool migration
might free up sufficient space to store the data.

System action:

Current operation has been cancelled.

User response:

Try the operation at a later time. If this fails, contact the IBM
Spectrum Protect administrator and request more storage pool space.

------------------------------------------------------------------------
ANS1327W

The snapshot operation for 'volname' failed with error code: retcode.



Explanation:

A snapshot could not be taken of the specified volume.

System action:

Snapshot processing stopped.

User response:

Check the client error log for any other messages that might help
identify the problem. If the problem cannot be resolved, contact IBM
technical support for additional assistance.

------------------------------------------------------------------------
ANS1328W

An error occurred generating delta file for 'file-name'. The return code
is retcode.



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

System action:

A full backup of the file is made, and a new version of the reference
file is stored in the subfile cache.

User response:

If the message indicates return code 4504, check the delta subfile cache
directory for any residual delta files. The delta subfile cache
directory is specified by the client option SUBFILECACHEPATH. Search the
directory for files named \".dXXXXXXXX\" where \"XXXXXXXX"\ is an
eight-digit number. If there are no backup operations in progress, there
should not be any files in the SUBFILECACHEPATH with this name. If there
are no backup operations in progress and these files exist, they can
safely be removed. If you continue to receive this message but there are
no residual delta files in the subfile cache directory and the file has
not grown to a size larger than 2 GB, then contact IBM technical support
for further assistance.

------------------------------------------------------------------------
ANS1329S

Server out of data storage space



Explanation:

The server does not have space available to store the object.

System action:

Processing Ends.

User response:

Report to your system administrator that a storage pool on the server is
full.

------------------------------------------------------------------------
ANS1330S

This node currently has a pending restartable restore session. The
requested operation cannot complete until this session either completes
or is canceled.



Explanation:

This operation can not be completed because a restartable restore
session is pending. The operation is not allowed because the restartable
session and the current operation affect the same file space.

System action:

Processing Ends.

User response:

Issue a query restore to see the conflict. Issue the cancel restore
command to delete any unneeded restartable restore sessions.

------------------------------------------------------------------------
ANS1331E

Only a IBM Spectrum Protect authorized user can perform this Action.



Explanation:

User must be a IBM Spectrum Protect authorized user to perform this
action. User is not password authorized and this action requires
authorization.

System action:

Processing stopped.

User response:

User must be root user, or user must be the owner of the executable and
the set effective user id bit is set to 'on' ('s' bit).

------------------------------------------------------------------------
ANS1332E

Run the '... for Administrators' version of the application.



Explanation:

The user must be root or a system administrator and use the provided
authorization tools to start IBM Spectrum Protect

System action:

IBM Spectrum Protect terminates.

User response:

The user must login as the root user or be a system administrator and
use one of the following authorization tools to start IBM Spectrum
Protect:

*  "IBM Spectrum Protect Backup for Administrators"

*  "IBM Spectrum Protect Scheduler for Administrators"

*  "IBM Spectrum Protect Scheduler Daemon for Administrators"

------------------------------------------------------------------------
ANS1333E

The remote node is not properly configured on the IBM Spectrum Protect
server.



Explanation:

The remote node is not properly configured on the IBM Spectrum Protect
server.

System action:

Processing stopped.

User response:

Ensure that the remote node is properly configured and connected to the
IBM Spectrum Protect server by using TLS. This validates the remote node
configuration and ensures that the information that is related to the
remote node is sent to the server.

------------------------------------------------------------------------
ANS1334W

Volume mount point 'filespace namepath-namedir-name' was not restored
because the target directory is not empty.



Explanation:

Volume mount points can only be restored if the target directory does
not already exist, or if the target directory exists but is empty. If
the target directory exists and is not empty, or already is a junction
point, then the volume mount point cannot be restored. On Windows Vista,
it is normal to see these warnings during system drive restore as there
are many junction points that point to the '%systemroot%\Users' folder.

System action:

The volume mount point is not restored. Processing continues with the
next object.

User response:

Correct the conflict with the non-empty directory, then try the
operation again. This is especially important when this message is
issued for a volume mount point that resides in the SYSVOL, since an
incomplete SYSVOL restore can result in system stability problems. See
the reference information for the RESTORE command in the client manual
for additional information about restoring volume mount points.

------------------------------------------------------------------------
ANS1335E

The RSM database files could not be restored.



Explanation:

None.

System action:

The RSM database is not restored. Otherwise, processing continues.

User response:

Check the client error log for any other messages that might help
identify the problem. Reboot the system, then try the RSM restore
operation again. If the problem cannot be resolved, contact IBM
technical support for further assistance.

------------------------------------------------------------------------
ANS1336I

RSM service must be restarted for changes to become effective.



Explanation:

RSM database files have been restored from the server and imported. The
RSM service must be restarted for the updates to become effective.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1337I

Restarting the RSM service...



Explanation:

RSM database files have been restored from the server and imported. The
process is about to stop then restart the RSM service.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1338I

Restart of the RSM service is completed.



Explanation:

RSM database files have been restored from the server and imported. The
process has restarted the RSM service on the user's behalf.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1339E

Restart of the RSM service failed. Restart the RSM service manually.



Explanation:

RSM database files have been restored from the IBM Spectrum Protect
server and imported. The process has tried to restart the RSM service on
the user's behalf but has run into a problem.

System action:

Processing stopped.

User response:

Restart the RSM service manually.

------------------------------------------------------------------------
ANS1340E

An error occurred while backing up the RSM database.



Explanation:

An error occurred while backing up the RSM database files. The database
will not be backed up.

System action:

Processing stopped.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1341E

An invalid character appears in the operand: operand.



Explanation:

The operand contains a character that is not valid in the current locale
and code page. It cannot be translated to its internal wide-character
format.

System action:

Processing stops.

User response:

Change the locale of the workstation to match the language in which the
operand is recorded, and try the command again.

------------------------------------------------------------------------
ANS1342E

Client cache is locked; unable to continue with operation.



Explanation:

The client cache is currently locked by another process.

System action:

Processing stopped.

User response:

Report the program error to your service representative.

------------------------------------------------------------------------
ANS1343E

The option 'specified-option' can only be entered when 'other-option'
has been entered.



Explanation:

The command failed because the specified 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 the specified option. Alternatively, run the
command with the other option added.

------------------------------------------------------------------------
ANS1344E

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.

System action:

Processing stopped.

User response:

Run the Job in the foreground.

------------------------------------------------------------------------
ANS1345E

No objects on the server match 'object-nameobject-nameobject-name'



Explanation:

The specified file does not have a match on the server.

System action:

The file is skipped.

User response:

Back up the file and try the operation again. If the problem continues,
see your system administrator to isolate the problem through use of the
server console.

------------------------------------------------------------------------
ANS1346E

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



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The SNAPSHOTCACHELocation points to a location which does not
contain the space necessary to manage the snapshot. This could be due to
an unexpected amount of disk activity which is generating more changes
than can be contained in the available space at this particular point in
time, or the SNAPSHOTCACHELocation needs to be changed because the
specified location is not large enough to handle the usual amount of
changes to the volume. Another reason for this failure can be that the
specified SNAPSHOTCACHESize is not set to a large enough value to handle
the usual amount of changes to the volume during snapshot image backup.

System action:

Processing stopped.

User response:

If the problem persists please increase the SNAPSHOTCACHESize and/or
change the value of the SNAPSHOTCACHELocation.

------------------------------------------------------------------------
ANS1347E

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



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The percent of space allotted via the SNAPSHOTCACHESize option
was not enough to perform this snapshot image backup. This could be due
to an unexpected amount of disk activity which is generating more
changes than can be contained in the allotted space at this particular
point in time. Another reason for this failure can be that the specified
SNAPSHOTCACHESize is not set to a large enough value to handle the usual
amount of changes to the volume during snapshot image backup.

System action:

Processing stopped.

User response:

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

------------------------------------------------------------------------
ANS1348E

Unable to satisfy the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries
options due to volume write activity.



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The Logical Volume Snapshot Agent was not able to satisfy the
SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options before starting the
snapshot of the specified volume.

System action:

Processing stopped.

User response:

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

------------------------------------------------------------------------
ANS1349E

An error occurred during Logical Volume Snapshot Agent snapshot
processing.



Explanation:

An unrecoverable error occurred during snapshot processing. This can be
caused by a variety of errors, so the error and system event logs should
be checked for additional messages.

System action:

Processing stopped.

User response:

Check the client error log and the system event log for any other
messages that might help identify the problem. Try the operation again.
If the problem persists, contact IBM technical support for further
assistance.

------------------------------------------------------------------------
ANS1350E

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



Explanation:

Another IBM Spectrum Protect process is already performing a snapshot of
this volume.

System action:

The operation is stopped.

User response:

Please wait until the other IBM Spectrum Protect process finishes with
the volume and then retry the operation.

------------------------------------------------------------------------
ANS1351E

Session rejected: All server sessions are currently in use



Explanation:

IBM Spectrum Protect has all available sessions in use and cannot accept
a new one at this time.

System action:

Current operation has been cancelled.

User response:

Retry the operation. If the problem continues, see your system
administrator to increase the number of concurrently active sessions to
the server.

------------------------------------------------------------------------
ANS1352E

The session is rejected. Your password has expired.



Explanation:

The password for IBM Spectrum Protect user ID has expired. It can be
either IBM Spectrum Protect node name password or administrative user ID
password or both.

System action:

Current operation has been cancelled. You are not allowed to connect to
the server until the password is updated.

User response:

Update your password. It may require updating the node name password or
the corespondent administrative ID password or both. You may use the SET
PASSWORD command, or have the IBM Spectrum Protect administrator update
your node or your administrative ID.

------------------------------------------------------------------------
ANS1353E

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



Explanation:

The user ID, which is either IBM Spectrum 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 Spectrum 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 Spectrum Protect user ID is entered correctly.
   Check the administrative ID associated with your IBM Spectrum Protect
   node and verify that the IBM Spectrum Protect node name has a
   matching administrative ID with client owner authority for the node.
   If it does not, your IBM Spectrum 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.

------------------------------------------------------------------------
ANS1354E

Session rejected: Duplicate ID entered



Explanation:

Another process using this node name is active with the server.

System action:

IBM Spectrum Protect cannot connect to the server. Current operation has
been cancelled.

User response:

If you are running a UNIX-based system, ensure that another process is
not active with IBM Spectrum Protect under the same name. Also, ensure
that your node name is unique to the server so that it cannot be used by
another person. See your system administrator to identify the owner of
that node name.

------------------------------------------------------------------------
ANS1355E

Session rejected: Server disabled.



Explanation:

The server is in a disabled state and cannot be accessed for normal
activity.

System action:

Current operation has been cancelled.

User response:

On the IBM Spectrum Protect server, run the ENABLE SESSIONS
administrative command. Try the operation again after the server returns
to an enabled state. If the problem continues, see your system
administrator.

------------------------------------------------------------------------
ANS1356E

The server is not configured to allow open registration



Explanation:

No authorization. Registration is required by your system administrator.
The server is not configured to allow open registration.

System action:

Session not started.

User response:

You must obtain a IBM Spectrum Protect node and password from your
system administrator.

------------------------------------------------------------------------
ANS1357S

Session rejected: Downlevel client code version



Explanation:

The server version and your client version do not match. The client code
is downlevel.

System action:

Current operation has been cancelled.

User response:

See your system administrator to see what version of IBM Spectrum
Protect to run for your location.

------------------------------------------------------------------------
ANS1358S

Session rejected: Downlevel server code version



Explanation:

The server version and your client version do not match. The server code
is downlevel.

System action:

Current operation has been cancelled.

User response:

See your system administrator to see what version of IBM Spectrum
Protect to run for your location.

------------------------------------------------------------------------
ANS1359E

Session Rejected: The specified node name is currently in use



Explanation:

The node name you specified is in use on the server.

System action:

Session was not started.

User response:

The server is probably performing a task that prevents your node from
establishing a session. Retry later or check with your system
administrator.

------------------------------------------------------------------------
ANS1360I

Compressed Data Grew



Explanation:

The size of the file after compression is greater than the size of the
file before compressed.

System action:

Even though the size of the file increased, the file is compressed.

User response:

None.

------------------------------------------------------------------------
ANS1361E

Session Rejected: The specified node name is currently locked.



Explanation:

The node name you specified is currently locked on the server.

System action:

Session was not started.

User response:

Check with your system administrator to find out why your node name is
locked.

------------------------------------------------------------------------
ANS1362S

SLM LICENSE EXCEEDED: The client licenses for IBM Spectrum Protect are
exceeded. See your system administrator.



Explanation:

Adding a new enrollment will exceed the product license count for IBM
Spectrum Protect.

System action:

Execution of the client enrollment or connection request ends.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1363E

Session Rejected: The server does not have enough memory to allow a
connection to be established.



Explanation:

The server does not have enough memory to allow your client to establish
a connection with the server.

System action:

Session was not started.

User response:

Retry later or see your system administrator.

------------------------------------------------------------------------
ANS1364E

Session Rejected: The server does not have enough recovery log space to
allow a connection to be established.



Explanation:

The server ran out of recovery log space.

System action:

Session was not started.

User response:

This error is a temporary problem. Retry later or see your system
administrator.

------------------------------------------------------------------------
ANS1365E

Session Rejected: The server does not have enough database space to
allow a connection to be established.



Explanation:

The server ran out of database space.

System action:

Session was not started.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1366E

The session is rejected. The IBM Spectrum Protect server has an internal
error.



Explanation:

The client cannot establish a connection to the IBM Spectrum Protect
server because of an internal server error.

System action:

The session was not started.

User response:

Notify your IBM Spectrum Protect administrator of this error.

------------------------------------------------------------------------
ANS1367E

The client is unable to sign on to the IBM Spectrum Protect server
because the server does not allow sign-on of Unicode clients.



Explanation:

The client is not allowed to connect to the IBM Spectrum Protect server.

System action:

The session does not start.

User response:

Contact your IBM Spectrum Protect administrator for assistance in
configuring a working IBM Spectrum Protect client for your environment.

------------------------------------------------------------------------
ANS1368S

Session Rejected: The server is not licensed for this platform type. See
your system administrator.



Explanation:

The server is not licensed for the requesting client type.

System action:

Execution of the client enrollment or connection request ends.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1369E

Session Rejected: The session was canceled by the server administrator.



Explanation:

The server administrator canceled the current client session.

System action:

Execution of the client connection request ends.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1370E

The user ID entered does not have the correct level of authority to
access the client machine.



Explanation:

The user ID entered cannot access this IBM Spectrum Protect client.

System action:

Operation ends.

User response:

Grant authority to this user ID on the IBM Spectrum Protect server so
that it can access this IBM Spectrum Protect client.

------------------------------------------------------------------------
ANS1371E

File '' cannot be reconstructed from subfile components.



Explanation:

An error occurred while reconstructing this file from its subfile
components.

System action:

The file indicated in the message is not restored. Restore for all other
files continues.

User response:

Try to restore the file again by selecting the file for restore from the
user interface. You can also check the client error log and the server
activity log for any messages related to the file indicated in the
message.

------------------------------------------------------------------------
ANS1372E

An inconsistency was detected between the client node and the node that
is registered to the IBM Spectrum Protect server.



Explanation:

The user has probably coded the node option incorrectly. For instance,
the node that is registered to the IBM Spectrum Protect server might be
a type of NAS, but the node is actually a non-NAS client.

System action:

Operation ends.

User response:

Ensure that the node name is correct in the client options file. Make
sure to use a node of type NAS only with the nasnodename option.

------------------------------------------------------------------------
ANS1373W

The PRESNAPSHOTCMD command for volume filespace completed with a
non-zero return code.



Explanation:

The command specified by the PRESNAPSHOTCMD option must complete
successfully in order to perform the snapshot backup/archive operation.
If the command completed with a return code of 0 (zero), it has
completed successfully. If the command completed with any other return
code, it has failed. If the command failed, then the backup is still
performed, but without the benefit of the snapshot technology.

System action:

The client executes the backup/archive operation, but without using a
snapshot.

User response:

Identify and fix the problem that caused the command to fail. If a
non-zero return code is normal for this command, then consider wrapping
the command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS1374W

The POSTSNAPSHOTCMD command for volume filespace completed with a
non-zero return code.



Explanation:

The command specified by the POSTSNAPSHOTCMD option completed with a
non-zero return code. The snapshot-based backup operation yields a
return code of at least 8.

System action:

The snapshot-based backup operation continues.

User response:

Identify and resolve the problem that caused the post-snapshot command
to fail. If a non-zero return code is normal for this command, then
consider wrapping the post-snapshot command in a script that always
exits with a return code of zero.

------------------------------------------------------------------------
ANS1375W

File FilesystemPathFileName skipped by user



Explanation:

You requested that this file be skipped during the current operation.

System action:

The file is skipped during the current operation

User response:

None.

------------------------------------------------------------------------
ANS1376E

Error processing 'filespace name path-namefile-name'; end-to-end digest
validation failed.



Explanation:

Cryptographic digest of the restored or retrieved data did not match the
digest generated during the backup or archive operation. Possible causes
are a transmission error, data corruption, or a hash collision.

System action:

Processing stops

User response:

Try the restore operation again. If the problem persists, contact IBM
technical support for additional assistance.

------------------------------------------------------------------------
ANS1377W

The client was unable to obtain a snapshot of 'volname'. The operation
will continue without snapshot support.



Explanation:

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

System action:

Snapshot processing stops.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1378E

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



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The SNAPSHOTCACHELocation points to a location which does not
contain the space necessary to manage the snapshot. Reasons for failure
include:

*  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.

------------------------------------------------------------------------
ANS1379E

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



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The percent of space allotted via the SNAPSHOTCACHESize option
was not enough to perform this snapshot backup/archive operation.
Reasons for failure include:

*  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.

------------------------------------------------------------------------
ANS1380W

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



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The Logical Volume Snapshot Agent was not able to satisfy the
SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options before starting the
snapshot of the specified volume.

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.

------------------------------------------------------------------------
ANS1381W

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



Explanation:

When the snapshot cache location is located on the same volume that is
being backed up the volume must be formatted with NTFS. The default
cache location is on the same volume where the snapshot is being
performed. The operation will continue without snapshot support.

System action:

The client does not execute the snapshot operation.

User response:

Specify a different snapshot cache location, using the
SNAPSHOTCACHELOCATION option.

------------------------------------------------------------------------
ANS1382E

Server does not allow client-initiated connections for this node.



Explanation:

The node is not allowed to initiate connections due to the configuration
parameters for this node on the server. Server is able to initiate
connections to the client scheduler running in prompted mode.

System action:

The IBM Spectrum Protect operation ends.

User response:

Contact your systems administrator to enable client-initiated sessions
for your node or update the SESSIONINITIATION option and run the client
scheduler.

------------------------------------------------------------------------
ANS1383E

Wrong server port.



Explanation:

You were trying to open a backup/archive client session on the server
port set up for administrative sessions only.

System action:

The IBM Spectrum Protect operation ends.

User response:

Contact your systems administrator and/or use the correct values for TCP
port and TCP Admin Port.

------------------------------------------------------------------------
ANS1384E

An object in the transaction has been bound to an invalid management
class.



Explanation:

One of the objects in the transaction is bound to a management class
that is not part of this node's policy, or the management class type is
not supported for this client level.

System action:

The current operation ends.

User response:

Make sure all objects are bound to a valid management class, or upgrade
the client to the proper level.

------------------------------------------------------------------------
ANS1385E

This server does not support backup operations.



Explanation:

This server only supports archive operations, backup is not allowed.

System action:

The current operation ends.

User response:

Use only archive operations with this server.

------------------------------------------------------------------------
ANS1386E

Deleting this object: "fshlll" is not allowed.



Explanation:

The object is either under a hold and cannot be deleted, or it is on a
retention-protection enabled server and has not expired.

System action:

The object is skipped and processing continues.

User response:

Check the status of the object through a query to see if it is held, or
when it expires.

------------------------------------------------------------------------
ANS1387E

The number of objects in this transaction exceed TXNGROUPMAX values.



Explanation:

There are too many objects in this transaction.

System action:

The current operation ends.

User response:

Try the operation again with fewer objects in the transaction, or
increase the TXNGROUPMAX value on the server.

------------------------------------------------------------------------
ANS1388E

fshlll is already under hold.



Explanation:

The specified object is already under hold, and it cannot be placed
under a new hold.

System action:

This object is skipped and processing continues.

User response:

Issue a query to see the status of the objects, and try the operation
again, without the object that is already held.

------------------------------------------------------------------------
ANS1389W

Invalid option (option) for the scheduled function command



Explanation:

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.

------------------------------------------------------------------------
ANS1395E

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



Explanation:

The system is trying to restore or retrieve to a destination that cannot
be reached. The specified filespace name or drive letter is not valid,
or does not exist, or you are specifying a local share name that cannot
be resolved.

System action:

Objects which are part of this filespace are not processed.

User response:

Try the command again, and specify a different destination for the
object that was not processed.

------------------------------------------------------------------------
ANS1396E

Access to the specified log or trace file (filename) is denied.



Explanation:

Access to the specified file is denied. You specified a log or trace
file name that cannot be written by the current user.

System action:

Processing stops.

User response:

Ensure that you specified the correct file or directory name, correct
the permissions, or specify a new location.

------------------------------------------------------------------------
ANS1397W

The snapshot cannot be taken because the SNAPSHOTCACHELocation does not
have enough space for this snapshot operation.



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume. The SNAPSHOTCACHELocation points to a location which does not
contain the space necessary to create the snapshot; the disk is probably
full. The operation continues without snapshot support.

System action:

The client does not execute the snapshot operation.

User response:

Change the value of the SNAPSHOTCACHELocation, or clean the disk to
which the SNAPSHOTCACHELocation points.

------------------------------------------------------------------------
ANS1398E

Initialization functions cannot open one of the IBM Spectrum Protect
logs or a related file: log-name. errno = errno-value, reason



Explanation:

The file "log-name" could not be opened during initialization. The
system set the error code errno-value. If the reason given is "access
denied," the 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.

------------------------------------------------------------------------
ANS1399W

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



Explanation:

IBM Spectrum 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 Spectrum Protect process finishes with the
volume and then try the operation again.

------------------------------------------------------------------------
ANS1400W

The snapshot cache location is not valid.



Explanation:

The snapshot cache location must point to a local volume that is
formatted with NTFS. The default cache location is on the same volume
where the snapshot is being performed. The operation will continue
without snapshot support.

System action:

Snapshot processing stops.

User response:

Specify a different snapshot cache location using the
SNAPSHOTCACHELOCATION option.

------------------------------------------------------------------------
ANS1401W

The snapshot virtual volume is not accessible.



Explanation:

The logical volume snapshot agent (LVSA) cannot access the virtual
volume during OFS-enabled backup/archive operation because IBM Spectrum
Protect was probably started via terminal services. The operation
continues without snapshot support.

System action:

Snapshot processing stops.

User response:

Do not use terminal services for the snapshot. Try the operation again
on the local machine.

------------------------------------------------------------------------
ANS1402W

The snapshot is not supported on a remote, removable, or SAN drive.



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume because open file support is only supported on local fixed
volumes, including volume mountpoints. The operation continues without
snapshot support.

System action:

The client does not execute the snapshot operation.

User response:

To take advantage of the open file support, you may try the operation
again on the local machine.

------------------------------------------------------------------------
ANS1403E

Error loading a required filename DLL



Explanation:

An error occurred while loading a dynamic link library. The DLL load
failed.

System action:

Processing stopped.

User response:

Verify that your system software is up to date and that all DLLs
required by the IBM Spectrum Protect client are present.

------------------------------------------------------------------------
ANS1404E

Error loading one or more functions from a required filename DLL



Explanation:

An error occurred while loading a function from a dynamic link library.
The DLL load failed.

System action:

Processing stopped.

User response:

Verify that your system software is up to date.

------------------------------------------------------------------------
ANS1405I

'service-name' service needs to be restarted.



Explanation:

The service must be restarted for the restored changes to take effect.

System action:

Changes are not effected.

User response:

Restart the service.

------------------------------------------------------------------------
ANS1407W

The value of option DiskBuffSize is ignored since Lan-Free is enabled.



Explanation:

Since Lan-Free is enabled the value of option DiskBuffSize will be reset
to the default value

System action:

Processing continues.

User response:

None

------------------------------------------------------------------------
ANS1408W

Previous changes have not been commited. The machine must be restarted
before the snapshot can be taken



Explanation:

IBM Spectrum Protect was not able to take a snapshot of the specified
volume because a previous operation required the machine to be restarted
for the changes to take effect, but the machine has not been restarted.
The operation will continue without snapshot support.

System action:

The client does not execute the snapshot operation.

User response:

Restart the machine and then try the operation again.

------------------------------------------------------------------------
ANS1409I

A full backup for the vm name virtual machine will be performed because
an include.resetcbt option was specified for the virtual machine.



Explanation:

The VM was specified in an include.resetcbt statement. A full backup and
a Changed Block Tracking (CBT) reset will be performed.

System action:

Changed Block Tracking (CBT) will be reset and the a full backup
operation will be performed for this virtual machine.

User response:

No action is required.

------------------------------------------------------------------------
ANS1410E

Unable to access the network path.



Explanation:

The network path cannot be accessed due to a possible network problem.

System action:

The client terminates.

User response:

Ensure that the network is up and the path can be accessed using a
system command, and retry the operation.

------------------------------------------------------------------------
ANS1411E

A communication session was dropped.



Explanation:

A communication session was dropped due to a possible network problem.

System action:

The client terminates.

User response:

Ensure that the network is up and retry the operation.

------------------------------------------------------------------------
ANS1412E

Directory or file has bad EA data or inconsistent data.



Explanation:

Directory or file has bad EA data or inconsistent data.

System action:

The client terminates.

User response:

Check failing directory or file for bad EA data. Copy the directory to a
new location and retry the operation.

------------------------------------------------------------------------
ANS1413W

File 'filespace namepath-namefile-name' is not recognized by the system
as a disk file and cannot be processed. The file is skipped.



Explanation:

The client is unable to process file types that are not 'disk', such as
'character' and 'pipe'. This message is typically, but not always,
issued for file names that are normally reserved for the operating
system. In the Windows environment, reserved names include AUX, CON,
NUL, PRN, COMx or LPTx, where 'x' is any digit from 1 to 9 (for example,
COM1, LPT3, etc.).

System action:

The file is skipped.

User response:

Either delete the file if you do not need it, or else use an EXCLUDE
statement in the client options to prevent the client from trying to
process the file. In the Windows environment, normal delete commands
will most likely not work. You will need to prefix the file name with
the characters '\\.\'. For example, "del c:\mydir\lpt4" will not work,
but "del \\.\c:\mydir\lpt4" will work.

------------------------------------------------------------------------
ANS1414W

Don't have sufficient authority to delete open group on server.



Explanation:

An open image group exists on the IBM Spectrum Protect server and cannot
be deleted due to missing backup delete rights for this node.

System action:

Processing continues.

User response:

Ask your IBM Spectrum Protect administrator to grant backup delete
rights for your node.

------------------------------------------------------------------------
ANS1417W

Protected system state file 'filename' is backed up to the drive file
space, not system state file space.



Explanation:

Files protected by Microsoft Windows File Protection (WFP) or Microsoft
Windows Resource Protection (WRP) are part of the Microsoft Volume
ShadowCopy Services (VSS) System Writer which is part of the system
state. These files are normally backed up as part of the system state,
not the file system on which the files reside. A problem in the
operating system environment prevented the protected file named in the
message text from being enumerated as a system state file and thus
backed up as part of the system state. The conditions that lead to this
message are not normal. In order to ensure that the file is protected,
it is backed up as part of the file system on which it resides.

System action:

The file is backed up as part of the file system on which it resides.

User response:

It is possible to restore the system using the file system and system
state backups. However the conditions that prevent the system state
files from being correctly enumerated should be addressed. On Microsoft
Windows 2008 and Microsoft Windows 2008 R2 you can use the DiskShadow
utility sub-command LIST WRITERS DETAILED to enumerate the system state
files. On other versions of Microsoft Windows you can use the vshadow
utility with the -wm2 option to enumerate the system state files. Verify
that the file indicated in this message is not listed. Note: vshadow is
a utility that you can obtain from Microsoft. After confirming that the
files are not enumerated, contact your operating system technical
support for help to diagnose and resolve the issue that prevents the
file from being correctly enumerated as part of the system state.

------------------------------------------------------------------------
ANS1418E

Authentication error. The Admin and/or Node password for nodename has
expired.



Explanation:

Session authentication failed with the server because either the admin
or node password for the node has expired.

System action:

Processing of the current operation is stopped.

User response:

Update your admin and/or node password for the node identified.

------------------------------------------------------------------------
ANS1420E

Volume map document (tsmvolmap.txt) not found.



Explanation:

An error occurred while performing VSS Automated System Recovery (ASR).
Check dsmerror.log for more information.

System action:

Processing stops.

User response:

Ask your system administrator to check the error log.

------------------------------------------------------------------------
ANS1421E

The image object 'object-type' was not found on server.



Explanation:

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.

User response:

Examine the client error log for additional messages that might indicate
the reason for the problem. Take any corrective action suggested by the
messages, then try the operation again. If the problem persists, contact
IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1423W

'filesystem' is a virtual mount point. Migration is not supported on
virtual mount points.



Explanation:

IBM Spectrum Protect HSM does not support virtual mount points within
managed file systems. Files in the virtual mount point folder can not be
migrated.

System action:

IBM Spectrum Protect attempts to continue the current operation.

User response:

Do not use virtual mount points within file systems that are managed by
HSM. Use include/exclude rules instead.

------------------------------------------------------------------------
ANS1424W

Retrying failed image operation for volume filespace-name.



Explanation:

The transaction for image operation for volume filespace-name failed due
to reason described by earlier message(s).

System action:

The requested image operation will be retried again.

User response:

None.

------------------------------------------------------------------------
ANS1425E

The image operation for volume filespace-name cannot be retried because
of a severe error.



Explanation:

None.

System action:

The image operation fails for the indicated volume.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1426E

An error occurred creating the Registry backup directory structure



Explanation:

The IBM Spectrum Protect client uses an intermediate directory structure
on the client machine as part of the Windows Registry backup process.
The client was unable to create this intermediate directory structure,
so the Windows Registry could not be backed up. This problem can occur
if you do not have sufficient privileges to perform the backup
operations, if the client is unable to allocate more memory from the
system, or if a component within the directory structure already exists
as a file.

System action:

The Windows Registry is not backed up.

User response:

Check the client error log for any other messages that might have been
logged when this message was written, and take the corrective action (if
any) suggested by those messages. Make sure that account under which the
operation runs has sufficient privileges. Ensure that the system has
sufficient memory to run the process. Remove the ADSM.SYS directory from
the root of your system drive, then try the operation again. If the
problem persists, contact IBM support for further assistance.

------------------------------------------------------------------------
ANS1427I

Registry Backup function completed successfully.



Explanation:

Registry backup was successful.

System action:

None.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS1428E

Backup of the registry failed.



Explanation:

None.

System action:

The registry is not backed up.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1429I

Registry Restore function completed successfully.



Explanation:

Registry Restore was successful.

System action:

None.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS1430W

The machine must be rebooted for the changes to take effect.



Explanation:

The restore operation made changes that will not be in effect until the
machine is rebooted. It is important to note that until the reboot
occurs, the system or its applications might be unstable.

System action:

None

User response:

Reboot the machine as soon as possible after the restore operation ends.

------------------------------------------------------------------------
ANS1431E

Restore of the registry failed.



Explanation:

None.

System action:

The registry is not restored.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1432E

Keyword Expected after keyword 'keyword'.



Explanation:

A registry command was incorrectly entered.

System action:

Registry function is not invoked.

User response:

Refer to the command reference for this command.

------------------------------------------------------------------------
ANS1433E

Extraneous argument 'input' after keyword 'keyword'



Explanation:

A registry command was incorrectly entered.

System action:

Registry function not invoked.

User response:

Refer to the command reference for this command.

------------------------------------------------------------------------
ANS1434E

Invalid argument 'input' after keyword 'keyword'



Explanation:

A registry command was incorrectly entered.

System action:

Registry function not invoked.

User response:

Refer to the command reference for this command.

------------------------------------------------------------------------
ANS1435E

An error occurred saving a registry key.



Explanation:

None.

System action:

The registry is not backed up.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1436E

An error occurred replacing a registry key.



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:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1437I

Event Log Backup function completed successfully.



Explanation:

Event Log backup was successful.

System action:

None.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS1438E

Backup of the event logs failed.



Explanation:

None.

System action:

The event logs are not backed up.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1439I

Event Log Restore function completed successfully.



Explanation:

Event Log Restore was successful.

System action:

None.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS1440E

Restore of the event logs failed.



Explanation:

None.

System action:

The event logs are not restored.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1441E

Keyword Expected after keyword 'keyword'.



Explanation:

A event log command was incorrectly entered.

System action:

Event Log function is not invoked.

User response:

Refer to the command reference for this command.

------------------------------------------------------------------------
ANS1442E

Extraneous argument 'input' after keyword 'keyword'



Explanation:

A event log command was incorrectly entered.

System action:

Event Log function not invoked.

User response:

Refer to the command reference for this command.

------------------------------------------------------------------------
ANS1443E

Invalid argument 'input' after keyword 'keyword'



Explanation:

A event log command was incorrectly entered.

System action:

Event Log function not invoked.

User response:

Refer to the command reference for this command.

------------------------------------------------------------------------
ANS1444E

An error occurred creating the Event Log backup directory structure



Explanation:

The IBM Spectrum Protect client uses an intermediate directory structure
on the client machine as part of the Windows Event Log backup process.
The client was unable to create this intermediate directory structure,
so the Windows Event Logs could not be backed up. This problem can occur
if you do not have sufficient privileges to perform the backup
operations, if the client is unable to allocate more memory from the
system, or if a component within the directory structure already exists
as a file.

System action:

The Windows Event Logs are not backed up.

User response:

Check the client error log for any other messages that might have been
logged when this message was written, and take the corrective action (if
any) suggested by those messages. Make sure that account under which the
operation runs has sufficient privileges. Ensure that the system has
sufficient memory to run IBM Spectrum Protect. Remove the ADSM.SYS
directory from the root of your system drive, then try the operation
again. If the problem persists, contact IBM support for further
assistance.

------------------------------------------------------------------------
ANS1445E

ERROR: could not create NAS image object.



Explanation:

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.

------------------------------------------------------------------------
ANS1446E

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



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.

------------------------------------------------------------------------
ANS1447W

The file containing the stored password for the specified server-name
stanza cannot be opened due to an internal error.



Explanation:

An internal error occurred in the IBM Spectrum Protect for Space
Management client. The file storing the IBM Spectrum Protect credentials
cannot be opened.

System action:

Processing continues.

User response:

Retry the operation. If the problem continues, contact your system
administrator or service representative.

------------------------------------------------------------------------
ANS1448E

The command command is not supported by the current server.



Explanation:

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

1. 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 Spectrum
   Protect Server levels 5.2.2 and above.

2. 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.

User response:

Log in to an appropriate server and run the command again.

------------------------------------------------------------------------
ANS1449W

A non-critical, unexpected error was encountered. Deletion of a
snapshot(Set/Volume) failed. Probable cause, snapshot does not exists
anymore. Continuing Process... IBM Spectrum Protect snapShot ID :
snapshot-id IBM Spectrum Protect function name : function-name IBM
Spectrum Protect function : function-desc IBM Spectrum Protect return
code : TSM-rc IBM Spectrum Protect file : file-name (line-number)



Explanation:

None.

System action:

Processing continues.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS1450W

The -FILENAME option was specified without a file name. Output will be
written to filename.



Explanation:

The -FILENAME option was specified, but the file name was omitted.

System action:

The output is written to the default file.

User response:

Reissue the command and specify a valid file name, or use the
information that was written to the default file.

------------------------------------------------------------------------
ANS1453W

The IMAGEGAPSIZE option is not supported 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 for additional information regarding the
IMAGEGAPSIZE option.

------------------------------------------------------------------------
ANS1454W

Used blocks information could not be obtained for name. The entire
volume will be backed up.



Explanation:

None.

System action:

The entire volume is backed up.

User response:

Check the client error log for any other messages that might help
identify the problem. Try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1455E

The value of the -vmname option 'vmname-option-value' would result in
the restoration of multiple virtual machines with the same name. Use the
keywords '*', <time>, or <timestamp> to differentiate the restored
virtual machine names.



Explanation:

The virtual machine restore command specified two or more virtual
machines. The value of the -vmname option would result in the restored
virtual machines having the same name.

System action:

The restore was stopped.

User response:

Use the keywords '*', '<time>', or '<timestamp>' in the -vmname option
so that each virtual machine is restored with a different name. If the
-vmname option is not specified, each virtual machine is restored with
the original name.

------------------------------------------------------------------------
ANS1458I

OBF file for volume name is too small for server-free data transfer.



Explanation:

The OBF file for volume is very small to initiate a server-free data
transfer. Hence this file will not be transferred via a server-free data
path.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1459E

VSS Automated System Recovery (ASR) failed.



Explanation:

An error occurred while performing VSS Automated System Recovery (ASR).
Check dsmerror.log for more information.

System action:

Processing stops.

User response:

Ask your system administrator to check the error log.

------------------------------------------------------------------------
ANS1461E

Error processing 'filespace namepath-namefile-name': unsupported
encryption type.



Explanation:

The files you are trying to restore or retrieve have been backed up or
archived by a later version of the IBM Spectrum Protect client. The file
encryption method is not supported by the current client.

System action:

Object skipped.

User response:

Restore or retrieve the file with the most recent version of the IBM
Spectrum Protect client.

------------------------------------------------------------------------
ANS1463E

Unexpected error in cryptography library.



Explanation:

There was an unexpected error in the cryptography library. See the error
log for more information.

System action:

processing stops.

User response:

Check the error log for ANS1467E to determine the cause of failure.
Verify you IBM Spectrum Protect client is installed properly. If needed,
reinstall client and/or API. If the problem still exists, contact IBM
Spectrum Protect technical support.

------------------------------------------------------------------------
ANS1464S

Cannot load ICC encryption library.



Explanation:

The process is using a cryptography library which is installed
automatically with the client and is being loaded at runtime. The client
cannot proceed if the library is not loaded.

System action:

Client exits.

User response:

Check the error log for ANS1467E to determine the cause of failure.
Verify your IBM Spectrum Protect client is installed properly. If
needed, reinstall the client and/or API. If the problem still exists,
contact IBM Spectrum Protect technical support.

------------------------------------------------------------------------
ANS1465E

Conflicting options ERRORLOGMAX and ERRORLOGRETENTION were specified.



Explanation:

Values were specified for both the ERRORLOGMAX and the ERRORLOGRETENTION
options. These options are mutually exclusive.

System action:

Processing stops.

User response:

Specify a nonzero value for the ERRORLOGMAX option if you want the error
log to wrap when it reaches the specified maximum value. Use the
ERRORLOGRETENTION option if you want the error log limited in size on a
time-based schedule.

------------------------------------------------------------------------
ANS1466E

Conflicting options SCHEDLOGMAX and SCHEDLOGRETENTION were specified.



Explanation:

Values were specified for both the SCHEDLOGMAX and the SCHEDLOGRETENTION
options. These options are mutually exclusive.

System action:

Processing stops.

User response:

Specify a nonzero value for SCHEDLOGMAX if you wish to have the IBM
Spectrum Protect scheduler log wrap when it reaches the specified
maximum value. Use SCHEDLOGRETENTION if you wish you have the scheduler
log limited in size on a time-based schedule.

------------------------------------------------------------------------
ANS1467E

ICC routine icc-routine returned: majRC = majRC, minRC = minRC, desc =
'desc'.



Explanation:

There was an error within an ICC cryptography library. This message
reports return codes and problem description which can be used by IBM
Spectrum Protect technical support personnel to determine the cause of
the error.

System action:

Client exits.

User response:

Verify you IBM Spectrum Protect client is installed properly. If needed,
reinstall client and/or API. If the problem still exists, contact IBM
Spectrum Protect technical support.

------------------------------------------------------------------------
ANS1468E

Backing up Automated System Recovery (ASR) files failed. No files will
be backed up.



Explanation:

An error occurred while backing up the files needed for Automated System
Recovery (ASR). No files were backed up.

System action:

Processing stops.

User response:

Ask your system administrator to check the error log. Verify that the
Windows account from which you are running this command has
administrator authority and try the command again.

------------------------------------------------------------------------
ANS1469E

Error processing 'filespace namepath-namefile-name'; invalid encryption
key.



Explanation:

The key you entered does not match the key that was used to encrypt the
file during backup. The file can not be restored unless the matching key
is entered.

System action:

processing stops.

User response:

Try the restore operation again and provide the correct key.

------------------------------------------------------------------------
ANS1470E

Unable to load GPFS functions needed for ACL and extended attributes
support: skip path_name



Explanation:

The GPFS functions that handle the GPFS ACL and extended attributes were
not loaded.

System action:

The object is skipped. Processing continues with the next object.

User response:

Ensure that the GPFS software is installed on the system and try the
operation again. On Linux, iensure that there has been an appropriate
symbolic link created in /usr/lib/ directory for the GPFS libgpfs.so
shared library.

------------------------------------------------------------------------
ANS1471E

ASR system information file creation failed. ASR backup is unsuccessful.



Explanation:

An error occurred while creating the system information file (asr.sif)
needed for Automated System Recovery (ASR). The ASR backup is
unsuccessful.

System action:

Processing stops.

User response:

Ask your system administrator to check the error log. Verify that the
Windows account from which you are running this command has
administrator authority and that you have access to the system object
staging directory <system drive> :\adsm.sys. Try the command again.

------------------------------------------------------------------------
ANS1472E

Could not add entry to the ASR system information file. ASR backup is
unsuccessful.



Explanation:

An error occurred while adding an entry to the system information file
(asr.sif) needed for Automated System Recovery (ASR). The ASR backup is
unsuccessful.

System action:

Processing stops.

User response:

Ask your system administrator to check the error log. Verify that the
Windows account from which you are running this command has
administrator authority and try the command again.

------------------------------------------------------------------------
ANS1473E

Session rejected: TCP/IP connection failure for Shared Memory



Explanation:

An attempt to connect to the local server using the Shared Memory
protocol has failed during initial TCP/IP communications. This error can
occur if the server is not listening on the correct port, or if the
server is down.

System action:

Session rejected. Processing stopped.

User response:

Retry the operation, or wait until the server comes back up and retry
the operation. If the problem continues, see your system administrator
for further help.

------------------------------------------------------------------------
ANS1474E

An error occurred using the Shared Memory protocol



Explanation:

An error has occurred while reading or writing data through the Shared
Memory communications protocol.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

Check the trace log for additional information and retry the operation.
If the problem continues, see your system administrator for further
help.

------------------------------------------------------------------------
ANS1475E

Insufficient authority to connect to the shared memory region



Explanation:

The user issuing the command does not have authority to connect to the
shared memory segment. When the shared memory segment is created by the
server, it will be owned by the effective uid of the server process
(dsmserv). Only processes running under this uid or root will be allowed
to connect to the segment (and thus to the server).

System action:

The session is rejected and processing stops.

User response:

Run the command under the uid of the processing running dsmserv, if
possible. Otherwise contact your system administrator for further help.

------------------------------------------------------------------------
ANS1476E

CLUSTERNODE is set to YES but the Cluster Information Daemon is
notstarted.



Explanation:

The HACMP Cluster Information Daemon must be started in order to specify
the CLUSTERNODE option.

System action:

Processing ends.

User response:

Start the HACMP Cluster Information Dameon.

------------------------------------------------------------------------
ANS1477E

CLUSTERNODE is set to YES but the cluster load library is not valid.



Explanation:

The load library that the operating system provides to obtain the
cluster name is not valid. A possible cause is an out-of-date load
library which does not contain the proper routines this product expects.

System action:

Processing ends.

User response:

Ensure that the latest cluster software is installed on the system.

------------------------------------------------------------------------
ANS1478E

CLUSTERNODE is set to YES but the cluster software is not availableon
this system.



Explanation:

The load library that the operating systems provides to obtain the
cluster name is not available on this system.

System action:

Processing ends.

User response:

Ensure that the cluster software is installed on the system.

------------------------------------------------------------------------
ANS1479E

CLUSTERNODE is set to YES but this machine is not a member of acluster.



Explanation:

This machine is not a member of a cluster node. Possible causes are that
the cluster service has not been configured correctly, or that the
cluster is in the process of initialization.

System action:

Processing ends.

User response:

Ensure that the cluster software is configured properly. If the cluster
is in the process of initialization, retry the operation at a later
time.

------------------------------------------------------------------------
ANS1480E

CLUSTERNODE is set to YES but the cluster service is not enabledon this
system.



Explanation:

The cluster service has not been enabled on this system.

System action:

Processing ends.

User response:

Enable the cluster service on the system.

------------------------------------------------------------------------
ANS1481E

The CLUSTERNODE option is not supported on this system.



Explanation:

This option is not supported on this system.

System action:

Processing ends.

User response:

Disable the CLUSTERNODE option in the local options file.

------------------------------------------------------------------------
ANS1482E

An unexpected error (retcode) occurred while the program was trying to
obtain the cluster name from the system.



Explanation:

An unknown error occurred while the program was trying to obtain the
cluster name from the cluster service. The error code is the reason code
provided directly from the cluster service being used in this operating
system environment.

System action:

Processing ends.

User response:

Consult the documentation for your clustering software for an
explanation of the reason code. Insure that your clustering service is
operational, then try the IBM Spectrum Protect operation again.

------------------------------------------------------------------------
ANS1483I

Schedule log pruning started.



Explanation:

The schedule log pruning function has begun.

System action:

The schedule log is pruned.

User response:

None.

------------------------------------------------------------------------
ANS1484I

Schedule log pruning finished successfully.



Explanation:

The schedule log pruning function completed with no errors.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS1487E

An error occurred while backing up the WMI repository. The database will
not be backed up.



Explanation:

The Windows event log and error log might contain additional information
related to this error.

System action:

processing stops.

User response:

Examine the Windows event log and error log for messages related to WMI.
Ensure that the Windows Management Instrumentation service is started.

------------------------------------------------------------------------
ANS1489E

The WMI service failed to stop. No files will be restored.



Explanation:

An error occurred while stopping the Windows Management Instrumentation
(WMI) service. The database will not be restored.

System action:

processing stops.

User response:

Examine the Windows event log and client error log for messages related
to Windows Management Instrumentation (WMI). You might need to quiesce
WMI activity or reboot the machine in order to free resources which are
preventing the WMI service from stopping.

------------------------------------------------------------------------
ANS1490W

File specification 'file-spec' ignored. A file list has already been
specified.



Explanation:

A non-option argument (file specification) was encountered after the
-FILELIST has been processed.

System action:

The argument is ignored.

User response:

You may have either a -FILELIST or explicit file specifications on this
command, but not both.

------------------------------------------------------------------------
ANS1492S

Invalid virtual mountpoint file_space_name: File not found.



Explanation:

The specified VIRTUALMOUNTPOINT option in the system options file is
invalid because it could not be found in the file system.

System action:

The process attempts to continue the current operation.

User response:

Check the virtual mountpoint in the system options file and make sure it
exists in the file system. Retry the operation.

------------------------------------------------------------------------
ANS1493S

Invalid virtual mountpoint file_space_name: Access denied.



Explanation:

The specified VIRTUALMOUNTPOINT option in the system options file is
invalid because access to it is denied.

System action:

The process attempts to continue the current operation.

User response:

Check the valule of the VIRTUALMOUNTPOINT option in the system options
file and make sure that the virtual mount point is accessible. Retry the
operation.

------------------------------------------------------------------------
ANS1494S

Invalid virtual mountpoint file_space_name: Symbolic link.



Explanation:

The specified VIRTUALMOUNTPOINT option in the system options file is
invalid because it is a symbolic link and the FOLLOWSYMBOLIC option is
not set.

System action:

The process attempts to continue the current operation.

User response:

Set the option FOLLOWSYMBOLIC to YES in the user options file. Retry the
operation.

------------------------------------------------------------------------
ANS1495S

Invalid virtual mountpoint file_space_name: Other error, rc =
return_code.



Explanation:

The specified VIRTUALMOUNTPOINT option in the system options file is
invalid.

System action:

The process attempts to continue the current operation.

User response:

Make sure the virtual mountpoint is a directory and accessible from the
shell, and retry the operation.

------------------------------------------------------------------------
ANS1496W

Duplicate include/exclude option 'option file-name' found while
processing the client options file. This might produce unexpected
results.



Explanation:

IBM Spectrum Protect found a duplicate statement while processing the
client options file, which might produce unexpected results.

System action:

Processing continues.

User response:

Verify if you obtained the desired results. If not, you need to correct
the client options file by removing the duplicate option statement.

------------------------------------------------------------------------
ANS1497W

Duplicate include/exclude option 'option file-name' found while
processing the client options passed by the server. This might produce
unexpected results.



Explanation:

IBM Spectrum Protect found a duplicate statement while processing the
client options by the server, which might produce unexpected results.

System action:

Processing continues.

User response:

Verify if you obtained the desired results. If not, you need to correct
either the client options file or the client options passed by the
server.

------------------------------------------------------------------------
ANS1498E

The IIS services failed to stop. No files will be restored.



Explanation:

An error occurred while stopping the Internet Information Services (IIS)
services. The metabase will not be restored.

System action:

processing stops.

User response:

Examine the Windows event log and client error log for messages related
to Internet Information Services (IIS). You might need to quiesce IIS
activity or reboot the machine in order to free resources which are
preventing the IIS service from stopping.

------------------------------------------------------------------------
ANS1499E

Creation of table of contents failed.



Explanation:

A failure occurred on the server during creation of the table of
contents.

System action:

The table of contents was not created.

User response:

This abort code indicates there was a problem creating a table of
contents on the server. The sysadmin will need to consult the activity
log on the server to determine the cause.

------------------------------------------------------------------------
ANS1500E

The dsmtca module is not found in the installation directory.



Explanation:

IBM Spectrum Protect cannot find the dsmtca module in the appropriate
directory.

System action:

Processing ends.

User response:

Reinstall the product.

------------------------------------------------------------------------
ANS1501E

The dsmtca execution/owner permissions are invalid



Explanation:

The dsmtca execution/owner permissions are invalid.

System action:

IBM Spectrum Protect ends.

User response:

Have your system administrator check the installation instructions for
the client to ensure that the dsmtca permissions are set correctly.

------------------------------------------------------------------------
ANS1502E

Access to run the the dsmtca or dsmenc module is denied.



Explanation:

The user of the backup-archive client does not have permission to run
the dsmtca or dsmenc module.

System action:

Processing ends.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1503E

Valid password not available for server 'server-name'. The administrator
for your system must run the backup-archive client and enter the
password to store it locally.



Explanation:

The file containing the stored password for the specified server
server-name is unavailable.

System action:

Processing ends.

User response:

The administrator for your system must set and store a new password.

------------------------------------------------------------------------
ANS1504E

Error starting the dsmtca or dsmenc process.



Explanation:

An error has occurred starting the dsmtca or dsmenc process;
specifically, the fork() function has failed.

System action:

Processing ends.

User response:

Probable system error. If the problem persists, restart the workstation.

------------------------------------------------------------------------
ANS1505W

Performing image backup of the entire volume for volume name. The
IMAGEGAPSIZE option value of image gap size is being ignored as this
level of the operating system does not support used block image backup.
Please upgrade to AIX 5.3 Maintenance Level 7 or later in order to
perform used block image backup.



Explanation:

AIX 5.3 Maintenance Level 7 or later has some necessary fixes that are
required to support used block image backup.

System action:

The entire volume is backed up.

User response:

Please upgrade to AIX 5.3 Maintenance Level 7 or later in order to
perform used block image backup.

------------------------------------------------------------------------
ANS1506E

The IBM Spectrum Protect dsmtca received an invalid request.



Explanation:

The dsmtca or dsmenc process was invoked by the backup-archive client
and received an unknown request argument in the call.

System action:

Processing ends.

User response:

It is possible that the dsmtca or dsmenc process was mistakenly invoked
by a process other than the backup-archive client. If that is not the
case, then this is an internal error. If the problem recurs, contact
your IBM service representative.

------------------------------------------------------------------------
ANS1507E

This action requires IBM Spectrum Protect administrative authority on
this system.



Explanation:

An activity has been attempted that must be performed by the IBM
Spectrum Protect administrator (for example, open registration, file
space delete or password update).

System action:

Processing ends.

User response:

If the activity is required, the administrator for this system must
perform it.

------------------------------------------------------------------------
ANS1508E

Error allocating semaphores.



Explanation:

An error has occurred because the semaphores you are attempting to
allocate have become insufficient.

System action:

Processing ends.

User response:

Ask your system administrator for assistance, and possibly increase the
number of semaphores in your system.

------------------------------------------------------------------------
ANS1509E

Error setting semaphore value or waiting on semaphore.



Explanation:

An error has occurred while attempting to set or wait on a semaphore.

System action:

Processing ends.

User response:

Probable system error. If the problem persists, restart the workstation.

------------------------------------------------------------------------
ANS1510W

The specified backupset either does not exist, or does not contain file
data.



Explanation:

The specified backupset either does not exist, or does not contain file
data for the node name specified. The restore backupset command is
limited to backupsets that contain file data. To restore an image backup
from a backupset, use the restore image command.

System action:

Processing stopped.

User response:

If an incorrect backupset name was specified, try the command again with
the correct backupset name. If you are trying to restore an image from a
backupset, refer to the restore image command for the correct syntax.

------------------------------------------------------------------------
ANS1511I

Invalid Restore session number entered. Try again.



Explanation:

You entered a number not shown in the list of restartable restores. The
number you entered is either less than one or greater than the highest
item number displayed.

System action:

Client prompts for a valid selection.

User response:

Enter a number from the list or 'Q' to quit.

------------------------------------------------------------------------
ANS1512E

Scheduled event 'event' failed. Return code = value.



Explanation:

One or more error conditions were encountered that prevented the
schedule from completing successfully. This message is preceded by other
messages that indicate the specific problems encountered during the
operation.

System action:

Scheduled event failed.

User response:

Check the schedule and error log files for the messages that specify
what problems were encountered during the operation. Correct the
conditions that caused those messages to be issued. The specific
corrective actions will depend on the specific errors encountered.

For more information about return codes, search for "client return
codes" in the product information
(www.ibm.com/support/knowledgecenter/SSGSG7/).

------------------------------------------------------------------------
ANS1513E

The object 'object_name' is skipped from rename. Error_condition.



Explanation:

IBM Spectrum Protect skips the specified object from renaming because
the object with the same long name but with different attributes exists
on the server.

System action:

The backup operation continues. The specified object will expire during
the next incremental backup.

User response:

The object is skipped if one of the following condition occurs:

   The long name object(LN) has a more recent insert date than the short
   name object(SN).
   The management classes for LN and SN do not match.
   The copy groups for LN and SN do not match.
   LN and SN have different owners.
   The creation date for LN and SN do not match.
   The short name attribute for LN does not match SN.

If you are unable to determine what is wrong, report the problem to your
service representative.

------------------------------------------------------------------------
ANS1514W

Encryption key passwords are not the same.



Explanation:

The key passwords are different.

System action:

The process allows you to try again.

User response:

Enter the correct password.

------------------------------------------------------------------------
ANS1515E

Loading a table of contents failed.



Explanation:

A failure occurred on the server during loading of the table of
contents.

System action:

The table of contents was not loaded.

User response:

This abort code indicates there was a problem loading a table of
contents on the server. The sysadmin will need to consult the activity
log on the server to determine the cause.

------------------------------------------------------------------------
ANS1519E

Your node does not have permission to delete backup files



Explanation:

The server does not allow your node to delete backup files.

System action:

The process did not delete the backup files.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS1520E

Failure writing to the IBM Spectrum Protect error log: errno =
errno-value,



Explanation:

A failure was encountered when writing to the dsmerror log or dsierror
log. The system set the error code errno-value. It is possible that no
space is available at the given log location.

System action:

Processing terminates.

User response:

Set the DSM_LOG (or DSMI_LOG) environment variable to a directory with
adequate space to write the log data.

------------------------------------------------------------------------
ANS1521E

Failure writing to a IBM Spectrum Protect log or log-related file:
file-name, errno = errno-value, reason



Explanation:

A failure was encountered when writing to one of the log files or a
related file named file-name. The system set the error code errno-value.
reason is the system explanation of that error code. Among other things,
it is possible that no space is available at the given log location.

System action:

Processing terminates.

User response:

Set the DSM_LOG (or DSMI_LOG) environment variable to a directory with
adequate space to write the log data.

------------------------------------------------------------------------
ANS1522W

The type of filespace file system is too old and only restore can be
performed



Explanation:

The file system is old only restore is supported by backup-archive
client

System action:

Only restore can be performed for this file system.

User response:

This file system is not supported anymore by Apple, so only restore
operation can be performed for this file system.

------------------------------------------------------------------------
ANS1523E

An error occurred while connecting to TSA/SMDR service.



Explanation:

An error was encountered during a call to the TSA/SMDR service. This
message usually follows previous messages that contain more specific
information about the problem.

System action:

Processing stopped.

User response:

Refer to previous messages in dsmerror.log for further information. If
those messages are not helpful in identifying the cause of the problem,
see your system administrator for further assistance.

------------------------------------------------------------------------
ANS1528I

The process is converting the log-file from continuous (pruning) mode to
wrapping mode. This process may take several minutes.



Explanation:

The log-file was previously in continuous mode where the only size
control was through the use of the ERRORLOGRETENTION or
SCHEDLOGRETENTION option. This is the first occasion where the
ERRORLOGMAX or SCHEDLOGMAX option is specified for this log, so its
format must be changed and old data saved.

System action:

Transition processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1529I

The process is converting the log-file from wrapping mode to continuous
(pruning) mode. This process may take several minutes.



Explanation:

The log-file was previously in wrapping mode where the size control was
through the use of the ERRORLOGMAX or SCHEDLOGMAX option. This is the
first occasion where the ERRORLOGMAX or SCHEDLOGMAX option is not
specified for this log, so its format must be changed and old data
saved.

System action:

Transition processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1530I

count log records processed.



Explanation:

This is just a progress report to let you know the process is still
ongoing.

System action:

Transition processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1532E

Proxy Rejected: Proxy authority has not been granted to this node.



Explanation:

The node has not been granted proxy authority to access the node named
by the ASNODENAME option. The IBM Spectrum Protect administrator must
first grant proxy authority.

System action:

The IBM Spectrum Protect operation ends.

User response:

The IBM Spectrum Protect server administrator must grant proxy authority
for this node. See the administrator command "Grant Proxynode".

------------------------------------------------------------------------
ANS1533E

Proxy Rejected: The node name you specified in the ASNODENAME option is
locked.



Explanation:

The IBM Spectrum Protect administrator has locked the node you specified
as the ASNODENAME option.

System action:

The IBM Spectrum Protect operation ends.

User response:

The IBM Spectrum Protect server administrator must unlock the node
before you can access it. Try the operation later, or check with your
IBM Spectrum Protect administrator.

------------------------------------------------------------------------
ANS1534E

Proxy Rejected: The IBM Spectrum Protect server has run out of memory.



Explanation:

There is not enough memory available to allow this operation to
continue.

System action:

Current operation has been cancelled.

User response:

Try the operation again. If the problem continues, see your system
administrator to increase the amount of memory of the server.

------------------------------------------------------------------------
ANS1535E

Proxy Rejected: The ASNODENAME and NODENAME options have the same value.



Explanation:

The ASNODENAME and NODENAME options cannot have the same value.

System action:

The current operation is cancelled.

User response:

Use the ASNODENAME option only to access another node. It is not
necessary to set the ASNODENAME option to access your own node. Remove
the ASNODENAME option from your option file unless you are actually
trying to access a node that you have been granted authority to access
with the administrative command "Grant Proxynode".

------------------------------------------------------------------------
ANS1536E

Proxy Rejected: The server has an internal error.



Explanation:

The client cannot proxy to the node named by the ASNODENAME option
because of an internal server error.

System action:

Current operation has been cancelled.

User response:

See your system administrator immediately.

------------------------------------------------------------------------
ANS1537E

The ASNODENAME option is not valid with the FROMNODE option.



Explanation:

None.

System action:

Processing stops.

User response:

Remove the ASNODENAME option from the options file or do not use the
FROMNODE option.

------------------------------------------------------------------------
ANS1538E

The operation that is being attempted cannot be invoked using the
ASNODENAME option.



Explanation:

None.

System action:

Processing stops.

User response:

Remove the ASNODENAME option and retry the operation.

------------------------------------------------------------------------
ANS1539E

The ASNODENAME option cannot be used with the CLUSTERNODE option.



Explanation:

None.

System action:

Processing stops.

User response:

Remove the ASNODENAME option and retry the operation.

------------------------------------------------------------------------
ANS1540E

The option 'option-name' requires a tag enabled data mover.



Explanation:

The client option 'VMTAGDATAMOVER' must be set to YES so that IBM
categories and tags can be applied to virtual machines. The active data
mover is not a tag enabled data mover.

System action:

The data mover operation stops.

User response:

Enable tag support on this data mover by setting the 'VMTAGDATAMOVER'
option to 'YES' then retry the operation.

------------------------------------------------------------------------
ANS1541E

The operation requires a tag enabled data mover.



Explanation:

The client option 'VMTAGDATAMOVER' must be set to YES so that IBM
categories and tags can be applied to virtual machines. The active data
mover is not a tag enabled data mover.

System action:

The data mover operation stops.

User response:

Enable tag support on this data mover by setting the 'VMTAGDATAMOVER'
option to 'YES' then retry the operation.

------------------------------------------------------------------------
ANS1544E

An error in WAS processing has occurred.



Explanation:

None.

System action:

None

User response:

Run the following command to see the nodes that can be backed up: dsmc
query was -wastype=local Make sure the results are correct for your
environment, then try the operation again. If the problem persists,
contact IBM Spectrum Protect technical support for further assistance.

------------------------------------------------------------------------
ANS1545W

IT22692: logical file sizes don't match: (migrated) migrated_file_size
!= (local) local_file_size for (file_path)



Explanation:

The dsmreconcile command is run in APAR IT22692 issue detection mode
('testflag HSM_IT22692_DETECTION' specified in the dsm.opt). In this
mode, this warning message is reported for each file that was
potentially affected by APAR IT22692 issue.

System action:

The reconciliation processing proceeds with next object.

User response:

Wait till the reconciliation processing completes, then run the
following corrective actions for each file identified by this warning: -
if there is backup copy, restore the backup copy overwriting the
affected file: root> dsmc restore /affected_file -repl=yes - if there is
no backup copy, unlink the affected file(s) and restore appropriate
stub(s) using the dsmmigundelete command: root> rm /affected_file1
/affected_file2 /affected_file_n root> dsmmigundelete /HSM_fs - to make
sure the rest of the premigrated files won't eventually contain file
data corrupted by IT22692, re-stub all existing premigrated files: root>
dsmmigrate -stubpremigrated -R /HSM_fs

------------------------------------------------------------------------
ANS1546W

IBM Spectrum Protect failed to lock the WebSphere configuration
repository.



Explanation:

None.

System action:

The lock of the WebSphere configuration repository fails.

User response:

Ensure that the WebSphere server is running. If the server is already
running, ensure that the repository is unlocked. Ensure that you are
backing up the correct node. To see a list of available nodes that can
be backed up, enter: 'dsmc q was -wastype=local'.

------------------------------------------------------------------------
ANS1547W

IBM Spectrum Protect failed to unlock the WebSphere Configuration
Repository.



Explanation:

None.

System action:

The unlock of the WebSphere Configuration Repository fails.

User response:

Make sure that the WebSphere server is running. If the repository is
locked, then unlock it and try the operation again. Ensure that the
correct node is being backed up. To see a list of available nodes that
can be backed up, run: 'dsmc q was -wastype=local'.

------------------------------------------------------------------------
ANS1548E

A supported version of WebSphere is not installed on this machine.



Explanation:

A supported version of WebSphere is not installed on this machine. The
only version of WebSphere that is supported is 5.0.x.

System action:

None

User response:

Install WebSphere 5.0 on the machine.

------------------------------------------------------------------------
ANS1549E

No application server instances were found. Unable to perform backup.



Explanation:

The application server is not installed on this machine.

System action:

Backup is not performed.

User response:

Install the application server.

------------------------------------------------------------------------
ANS1550E

No network deployment manager instances were found to back up.



Explanation:

Deployment manager is not installed on this machine.

System action:

Back up is not performed.

User response:

Install the network deployment manager.

------------------------------------------------------------------------
ANS1551E

The maximum number of search responses was exceeded.



Explanation:

The local file system search results exceeded the maximum allowed.

System action:

Processing stops.

User response:

Refine the search criteria to return fewer results or increase the
configured maximum.

------------------------------------------------------------------------
ANS1552E

The local file system search timed out.



Explanation:

The local file system search did not complete in the allotted amount of
time.

System action:

Processing stops.

User response:

Refine the search criteria or increase the configured timeout.

------------------------------------------------------------------------
ANS1553W

The user name and password that have been provided to Data Protection
for WebSphere are invalid.



Explanation:

None.

System action:

Data Protection for WebSphere cannot run.

User response:

Run the dsmc set WASPassword command to set the WebSphere security user
name and password.

------------------------------------------------------------------------
ANS1556E

Setting the WAS user and password failed.



Explanation:

Password validation for the WAS user and password failed.

System action:

WAS password validation fails.

User response:

Rerun the set WASPassword command with the correct values for user and
password.

------------------------------------------------------------------------
ANS1557W

The WAS Server was not running, and the password file was saved without
validation.



Explanation:

If the WAS server is down, then it is not possible to connect to the
server and validate the user-entered password. The password has still
been saved, but no validation has been performed.

System action:

The set WAS password command did not validate the password. The password
has still been saved, but no validation has been performed. The password
may be incorrect.

User response:

There are two options:

*  Try a backup. If the backup performs a failover, and there is a
   incorrect password message in the error log, then the password that
   was entered is incorrect.

*  Start the WAS server and rerun the set password command. Since the
   server is now up, validation will be performed as normal and the user
   notified if a good/bad password was entered.

------------------------------------------------------------------------
ANS1560W

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 the backup again.

------------------------------------------------------------------------
ANS1562E

WAS Restore failed during EAR Expansion.



Explanation:

EAR Expansion is performed for a WebSphere Application server after the
files have been restored.

System action:

WAS restore fails.

User response:

Run the restore again.

------------------------------------------------------------------------
ANS1565E

No WebSphere EARExpander was found. Copy the EARExpander tool from the
base WebSphere bin directory to the instance bin directory, then run the
restore operation again.



Explanation:

The EAR files are expanded for an instance of an Application server and
the EARExpander tool does not exist in the instance bin directory.

System action:

No WebSphere EARExpander found.

User response:

Copy the WAS EARExpander tool from the base install's bin directory to
the bin directory of the instance. Then run the WAS restore operation
again, after the EARExpander tool has been copied.

------------------------------------------------------------------------
ANS1566E

The version of WebSphere on the machine does not match the version of
WebSphere that was backed up. These versions must match for a WAS
restore operation.



Explanation:

The version of WebSphere on the machine does not match the version of
WebSphere that was backed up. These versions must match for a WAS
restore operation.

System action:

The WAS restore operation fails.

User response:

Install the correct version of WebSphere on the machine before
performing the restore operation.

------------------------------------------------------------------------
ANS1568E

The client acceptor attempted to register it's tcpport and tcpip address
without using the TCPCADADDRESS option.



Explanation:

The client acceptor sent the port and address information to the server,
however, there was a problem registering the information with the
server. The problem occurred because no default value for the tcpip
address was provided. The server was unable to determine a default value
for the tcpip address because the communication method was not tcpip.

System action:

The server cannot register the information for the client acceptor.
client acceptor processing will continue, but some functions of the
client acceptor may not be working properly.

User response:

Use TCPCADADDRESS in the client option file to indicate the proper
TCP/IP address for this client acceptor.

------------------------------------------------------------------------
ANS1569E

The client acceptor attempted to register it's tcpport and tcpip address
but the TCP/IP address resolved to the loopback address and was rejected
by the server.



Explanation:

The client acceptor sent the port and address information to the server,
however, there was a problem registering the information with the
server. The problem occurred because the server detected that the
address provided resolved to the loopback address.

System action:

The server did not register the information for the client acceptor.
client acceptor processing will continue, but some functions of the
client acceptor may not be working properly.

User response:

Use TCPCADADDRESS in the client option file to indicate the proper
TCP/IP address for this client acceptor. Loopback address is not valid.

------------------------------------------------------------------------
ANS1570E

Registering this instance of the client acceptor with the server failed.
The client acceptor process continues.



Explanation:

The client acceptor failed to register address information to the server
due to an error.The message immediately preceding this message should
indicate the problem more precisely.

System action:

The server did not register the information for the client acceptor.
client acceptor processing continues, but some functions of the client
acceptor might not work properly.

User response:

Review the messages immediately preceding this message to help determine
what error occurred.

------------------------------------------------------------------------
ANS1571E

The time-option option cannot be used without specifying the date-option
option



Explanation:

If the to/from/pit time options is specified then the corresponding
to/from/pit date MUST also be specified.

System action:

Processing stopped.

User response:

Either remove the to/from/pit time option or add the corresponding
to/from/pit date option.

------------------------------------------------------------------------
ANS1572E

An unexpected error was received from the server query, RC=re tcode.



Explanation:

An unexpected error was received by the client. This could be caused by
network problems or a programming error.

System action:

Current operation has been cancelled.

User response:

Verify that your communication path is functioning properly and try the
operation again. If the problem persists, contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS1573E

FROMDATE and TODATE cannot be used with PITDATE.



Explanation:

The PITDATE option specifies different and conflicting date selection
criteria from the FROMDATE and TODATE options. Therefore these options
cannot be combined.

System action:

The restore operation is not performed.

User response:

Determine whether you require the functionality of PITDATE or FROMDATE
and TODATE, then try the operation again. If you want to restore files
as of a certain date and time, use PITDATE and PITTIME. If you want to
restore files from a given range of dates, use FROMDATE, TODATE,
FROMTIME, and TOTIME. Refer to the IBM Spectrum Protect client manual
for your operating system for additional information about these
options.

------------------------------------------------------------------------
ANS1574E

Journal Query Failed.



Explanation:

The journal daemon was unable to process the requested journal query.

System action:

Journal backup processing is interrupted.

User response:

Retry the backup, check the journal daemon errorlog for the cause of the
failure. Backup of other file systems in the domain will continue.

------------------------------------------------------------------------
ANS1575E

Journal Daemon Communications Error.



Explanation:

An error occurred communicating with the journal daemon.

System action:

Journal backup processing is interrupted.

User response:

Retry the backup, check the journal daemon and client errorlogs for the
cause of the failure.

------------------------------------------------------------------------
ANS1577I

The Windows console event handler received a 'event' console event.



Explanation:

A console event was received by one of the IBM Spectrum Protect
processes or programs. The following events can be received:

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

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS1578E

The specified path 'path' is not valid for backup or archive.



Explanation:

The specified path is a special file system or part of a special file
system. Special file systems contain dynamic information generated by
the operating system and should not be backed up or archived. Refer to
the IBM Spectrum Protect client manual for a complete list of special
file systems for your operating system.

System action:

Processing continues if there are other file systems to back up.

User response:

Do not specify special file systems for backup or archive.

------------------------------------------------------------------------
ANS1579E

GSKit function func-name failed with error-code: session



Explanation:

A GSKit function has failed with the specified error code.

System action:

Processing stopped

User response:

Make sure you have configured the key database for SSL communication as
described in the documentation. Possible issues could be failure in TLS
handshake due to client and server not agreeing on a protocol. If the
problem persists, contact IBM Spectrum Protect customer support.

------------------------------------------------------------------------
ANS1580W

An Include.Fs statement with performance algorithm set already exists
for the drive specified. Do you want to replace the statement?



Explanation:

The user tried to create a duplicate Include.Fs entry on a drive that
already has a performance algorithm associated with it. This is
applicable to the Preference Editor on the MFC GUI

System action:

The user can replace the statement with the new one or they can cancel
out of this operation

User response:

The user is prompted to replace the statement with the new one or they
can say No to cancel out of this operation.

------------------------------------------------------------------------
ANS1581W

'object-name' was restored as 'temp-name'. A reboot is required to
complete the restore.



Explanation:

This is a system file restored and could not be immediately replaced.
The file will be replaced during the next reboot of the operating
system. It is important to note that until the reboot occurs, the
changes will not be in effect.

System action:

The client restored the file with a temporary name, and instructed the
operating system to replace the original file with the restored file
during the next boot of the operating system.

User response:

Reboot the machine as soon as possible after the restore operation ends.

------------------------------------------------------------------------
ANS1582E

The web client is no longer supported when connecting to IBM Spectrum
Protect V7.1.8 or V8.1.2 and later servers.



Explanation:

The web client functionality is no longer supported and is unavailable
for connecting to IBM Spectrum Protect V7.1.8 or V8.1.2 and later
servers.

System action:

Processing stopped

User response:

Use one of the other supported client interfaces to perform your IBM
Spectrum Protect operations. Refer to IBM Spectrum Protect documentation
for information on the supported client interfaces.

------------------------------------------------------------------------
ANS1583E

The Hardware Utility plug-in module was not found or could not be
loaded.



Explanation:

Processing stops.

System action:

None.

User response:

Run the "dsmc show plugins" command at the command-line client prompt to
see the available plug-ins on the system and verify the path which is
being used to load the plug-ins. If the plug-in path is available and
the Hardware Utility plug-in, libPiHDW.a, is present, ensure that the
LIBPATH variable is set to the Hardware product's library path. For
example, LIBPTH=/usr/opt/db2_08_01/lib.

------------------------------------------------------------------------
ANS1584E

Error loading system library 'libdevmapper.so' required for image
operations for LVM2 volumes.



Explanation:

The system library libdevmapper.so required for LVM2 image operations
could not be loaded. This error can occur when the library does not
exist on the system, or the library is an earlier level than is
required. This error also occurs when the library can not be opened by
the IBM Spectrum Protect clienti process.

System action:

The image operations for LVM2 volumes are not available.

User response:

Check the installed packages and the library versions on the system. If
correct versions are installed, check for access related issues. If the
system does not have these libraries installed, contact your Linux OS
distributer. Also, refer to Technote 1452629:
https://www.ibm.com/support/docview.wss?uid=swg21452629

------------------------------------------------------------------------
ANS1587W

Unable to read extended attributes for object object-full-name due to
errno: errno-value, reason: errno-explanation



Explanation:

The extended attributes of the object could not be read. The system set
the error code errno-value and the reason errno-explanation. If the
reason errno-explanation is either "access denied" or "permission
denied", the current user does not have permission to read the extended
attributes of the object.

System action:

The object is skipped. Processing continues with the next object.

User response:

The error is expected if the operation tries to read extended attributes
of an object that you do not own or do not have access to. If the reason
indicates an input/output error, perform the file system consistency
check procedure and try the operation again. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1588W

I/O error reading file attribute: attr-name for: file-name. errno =
errno-value,



Explanation:

The attribute attr-name of the file file-name could not be retrieved.
The system set the error code errno-value. If the reason given is
"access denied," the current user does not have permission to read the
file attributes.

System action:

Processing continues without backing up the specified file attribute.

User response:

Correct the condition causing the physical error.

------------------------------------------------------------------------
ANS1589W

Unable to write extended attributes for object-full-name due to errno:
errno-value, reason: errno-explanation



Explanation:

The extended attributes of the object could not be written. The system
set the error code errno-value and the reason errno-explanation. If the
reason is either "access denied" or "permission denied", the current
user does not have permission to write the extended attributes of the
object.

System action:

Processing continues without restoring the extended attributes.

User response:

The error is expected if the operation tries to write extended
attributes to an object that you do not own or do not have access to. If
the reason indicates an input/output error, perform the file system
consistency check procedure and retry the operation. If the problem
persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1590W

I/O error writing file attribute: attr-name for: file-name. errno =
errno-value,



Explanation:

The attribute attr-name of the file file-name could not be set. The
system set the error code errno-value. If the reason given is "access
denied," the current user does not have permission to set the file
attributes.

System action:

Processing continues without restoring the specified file attribute.

User response:

Correct the condition causing the physical error.

------------------------------------------------------------------------
ANS1592E

Failed to initialize SSL protocol.



Explanation:

The process was unable to initialize the SSL protocol. This could be
because the node is in a strict 'sessionsecurity' state and the client
certificate key database could not be found.

System action:

Processing stopped

User response:

Check for GSKit related messages in the error log. Make sure you have
configured the key database for SSL communication as described in the
documentation. You must manually import the client certificate by using
the dsmcert utility. If the problem persists, contact IBM Spectrum
Protect customer support.

------------------------------------------------------------------------
ANS1593E

Cannot open the key database.



Explanation:

The process was unable to open the keyfile that is expected to contain
the server certificate for SSL communications.

System action:

Processing stopped

User response:

Make sure you have configured the key database for SSL communication as
described in the documentation. If the problem persists, contact IBM
Spectrum Protect customer support.

------------------------------------------------------------------------
ANS1594E

The key database password is incorrect or unavailable.



Explanation:

The client was unable to open the certificate key database using the
stored password, or the stored password could not be read.

System action:

Processing stops.

User response:

Make sure that you configure the key database for SSL communication as
described in the Client Installation and User's Guide. Also make sure
that the stash file, dsmcert.sth, is readable by the current user.

------------------------------------------------------------------------
ANS1595E

Bad server certificate.



Explanation:

The process was unable to open SSL connection to server because of a bad
certificate. This error usually occurs when the server certificate
cannot be verified by the client.

System action:

Processing stopped

User response:

Make sure you have configured the key database for SSL communication as
described in the documentation. Make sure to import the correct
certificate from the IBM Spectrum Protect server you are trying to
connect to.

------------------------------------------------------------------------
ANS1596E

SSL protocol is not supported.



Explanation:

SSL protocol is not supported on this platform.

System action:

Processing stopped

User response:

Refer to IBM Spectrum Protect documentation for the list of supported
platforms.

------------------------------------------------------------------------
ANS1597E

The -pick and -deltype=all options are not valid together.



Explanation:

-deltype=all is used to delete an entire directory tree. You cannot use
-pick to select individual objects from the tree. -pick is valid only
with -deltype=active or -deltype=inactive.

System action:

Processing stopped.

User response:

Try the operation again with a valid combination of options. If you want
to delete an entire tree, use -deltype=all, but do not use -pick. If you
want to select which backup versions to delete, specify -deltype=active
or -deltype=inactive, and use the -pick option. Also use -subdir=yes if
you want the file selection to include files in subdirectories of the
file specification. See the client manual or command line help for
additional information.

------------------------------------------------------------------------
ANS1598E

-deltype=all is not valid for this file specification.



Explanation:

-deltype=all is used to delete an entire directory tree. You must
specify a fully wildcard directory when using -deltype=all.

System action:

Processing stopped.

User response:

Try the operation again with a valid combination of options. If you want
to delete all backup versions of an entire directory tree, use
-deltype=all and a fully wildcarded file specification. If you want to
delete backup versions of partially qualified file names, use
-deltype=inactive or -deltype=active. Also use -subdir=yes if you want
to delete backup versions in subdirectories of the file specification.
See the client manual or command line help for additional information.

------------------------------------------------------------------------
ANS1599E

Cannot load SSL runtime library.



Explanation:

IBM Spectrum Protect failed to dynamically load SSL runtime library
necessary for SSL protocol

System action:

Processing stopped

User response:

Make sure IBM Spectrum Protect client is properly installed. Try to
reinstall the client software. If the problem persists, contact IBM
Spectrum Protect customer support.

------------------------------------------------------------------------
ANS1600E

Unable to load the Data Protection for Lotus Domino library.



Explanation:

The Datt Protection for Lotus Domino library could not be loaded.

System action:

Processing ends.

User response:

Ensure that Domino plugin is properly configured and check the error log
on the client machine for more information.

------------------------------------------------------------------------
ANS1601E

The Domino plugin operation failed because of an internal error.



Explanation:

A Domino plugin internal error has occurred.

System action:

Processing ends.

User response:

Check the error log on the client machine for more information.

------------------------------------------------------------------------
ANS1602E

The Domino plugin operation failed because the preferences file was not
found.



Explanation:

The Data Protection for Lotus Domino preference file could not be found.

System action:

Processing ends.

User response:

The Data Protection for Lotus for Domino configuration file (default
name domdsm.cfg) could not be found. Check the error log on the client
machine for more information.

------------------------------------------------------------------------
ANS1603E

The Domino plugin operation failed because of an internal TCP/IP error.



Explanation:

A TCP/IP error has occurred.

System action:

Processing ends.

User response:

Check the error log on the client machine for more information.

------------------------------------------------------------------------
ANS1604E

The Domino plugin operation failed trying to start the dsmdomp address
space.



Explanation:

The dsmdomp address space could not be started. This is probably an
installation error.

System action:

Processing ends.

User response:

Ensure that the lotus/bin directory has a symbolic link to the tools
directory for dsmdomp and the lotus/notes directory has a symbolic link
to the dsmdomp executable. If the problem persists, contact your System
Administrator for further assistance.

------------------------------------------------------------------------
ANS1605E

The Domino plugin operation failed while initializing communications
with the dsmdomp address space.



Explanation:

The Domino plugin communication initialization failed.

System action:

Processing ends.

User response:

The dsmdomp address space failed during its initialization. This is
likely to be an installation error. Ensure that the lotus/bin directory
has a symbolic link to the tools directory for dsmdomp and the
lotus/notes directory has a symbolic link to the dsmdomp executable. If
the problem persists, contact your System Administrator for further
assistance.

------------------------------------------------------------------------
ANS1606E

The Domino plugin operation failed while starting up the dsmdomp address
space.



Explanation:

The dsmdomp address space could not be started.

System action:

Data Protection for Domino processing stops.

User response:

The dsmdomp address space failed during its initialization. This is
likely to be an installation error. Ensure that the lotus/bin directory
has a symbolic link to the tools directory for dsmdomp and the
lotus/notes directory has a symbolic link to the dsmdomp executable.
Examine the file /tmp/dsmdomp* for more information. If the problem
persists, contact your System Administrator for further assistance.

------------------------------------------------------------------------
ANS1607E

A plugin found in the plugins library is not supported by the current
level of the IBM Spectrum Protect client.



Explanation:

The plugin is not loaded, and processing continues.

System action:

The plugin is not loaded, and processing continues.

User response:

This probably is an installation error. Ensure that the plugins
directory contains valid plugin libraries, and that the correct level of
the IBM Spectrum Protect client has been installed. If the problem
persists, contact your System Administrator for further assistance.

------------------------------------------------------------------------
ANS1608E

Domino plugin operation failed with the following message: messsage



Explanation:

A Domino plugin operation error occurred.

System action:

Processing ends.

User response:

Correct the error that caused the operation to fail.

------------------------------------------------------------------------
ANS1609E

Domino plugin process failed. The following messages are associated with
the error. messsage.



Explanation:

A Domino plugin operation error occurred.

System action:

Processing ends.

User response:

Correct the error that caused the operation to fail.

------------------------------------------------------------------------
ANS1611E

A plugin operation failed because of an internal error.



Explanation:

A plugin internal error has occurred.

System action:

The plugin operation stops.

User response:

If the error persists, run with tracing enabled and contact your System
Administrator and IBM for further assistance.

------------------------------------------------------------------------
ANS1612E

The Domino plugin operation failed because of a IBM Spectrum Protect API
error.



Explanation:

An IBM Spectrum Protect API error occurred .

System action:

Processing ends.

User response:

Check error log on the client machine for more information.

------------------------------------------------------------------------
ANS1613E

>Could not load the IBM Spectrum Protect API.



Explanation:

The IBM Spectrum Protect API could not be loaded.

System action:

Processing ends.

User response:

Check error log on the client machine for more information.

------------------------------------------------------------------------
ANS1614E

The Domino plugin 'Try and Buy' license has expired.



Explanation:

The 'Try and Buy' license that was detected has expired.

System action:

Processing ends.

User response:

This product is no longer valid for use. A valid license must be
obtained before running the product.

------------------------------------------------------------------------
ANS1615E

The Domino plugin operation failed due to a license error.



Explanation:

Domino plugin license verification failed.

System action:

Processing ends.

User response:

Check the error log for further information.

------------------------------------------------------------------------
ANS1616E

The Domino plugin operation failed because the Lotus Domino API could
not be loaded.



Explanation:

The Lotus Domino API could not be loaded.

System action:

Processing ends.

User response:

Ensure the Lotus Domino Server is installed correctly.

------------------------------------------------------------------------
ANS1617E

The Domino plugin operation failed because of a Data Protection for
Domino API error.



Explanation:

A Data Protection for Domino API error occurred during a Domino plugin
operation.

System action:

Processing ends.

User response:

For more details, view the following IBM Spectrum Protect error logs.

The API error log (dsierror.log) and the log of Data Protection for
Domino activity (domdsm.log). The default location of these logs is the
Data Protection for Domino installation directory.

The backup-archive client error log (dsmerror.log), the web client error
log (dsmwebcl.log), and the log of scheduler activite (dsmsched.log).
The default location of these logs is the backup-archive installation
directory.

------------------------------------------------------------------------
ANS1618E

A Domino plugin operation is already in progress. Please wait for
operation to complete.



Explanation:

A Domino plugin operation is in progress.

System action:

The Domino plugin operation stops.

User response:

Please wait for the Domino plugin operation to complete before starting
a new Domino plugin operation.

------------------------------------------------------------------------
ANS1619E

The IBM Spectrum Protect application client cannot work with the version
of the Domino plugin you have installed.



Explanation:

The version of the Domino plugin currently installed on the system is
older than the version used to build the IBM Spectrum Protect
application client.

System action:

Processing ends.

User response:

Install a version of the Domino plugin at or later than the level of the
IBM Spectrum Protect application client.

------------------------------------------------------------------------
ANS1621E

Failed to update backup attributes on server for local backup for
'file_space_namepath_namefile_name', object id - 'object_id':'object_id'
return code 'return_code'.



Explanation:

The process failed to update attributes for the named backup object on
the server. The server may not reflect correct state of the backup.

System action:

Processing continues.

User response:

Check preceding error messages in error log for more information. Retry
the operation. If problem continues, contact your IBM Spectrum Protect
administrator.

------------------------------------------------------------------------
ANS1622I

Number of backup objects cleaned up on server: 'number' number of local
snapshot resources made available :'number'.



Explanation:

While performing consistency check for server's database and the local
repository maintained on the client system, reported inconsistencies
were found. Inconsistent backups cannot be restored, therefore IBM
Spectrum Protect deletes all inconsistent backup objects and frees the
space occupied in the local repository.

System action:

Processing continues.

User response:

Check error log for further details on which objects on server were
deleted. If numbers look unusually high check your configuration and if
it continues, contact your IBM Spectrum Protect administrator.

------------------------------------------------------------------------
ANS1623W

Backup of NSF Db2 database was skipped. NSF Db2 databases not supported.



Explanation:

This version of DP for Domino plugin does not support NSF Db2 databases.

System action:

Backup of NSF Db2 databases is skipped.

User response:

Exclude NSF Db2 databases from backup.

------------------------------------------------------------------------
ANS1624E

'value' is an invalid value for option 'option' for 'command' command



Explanation:

The specified option value is not valid in this context.

System action:

The operation was stopped

User response:

Specify a valid value for the option. Consult documentation for valid
values.

------------------------------------------------------------------------
ANS1626E

An unexpected error was encountered when processing a IBM Spectrum
Protect operation using a hardware or snapshot function. IBM Spectrum
Protect function name : function-name IBM Spectrum Protect function :
function-desc IBM Spectrum Protect return code : TSM-rc IBM Spectrum
Protect file : file-name (line-number)



Explanation:

None.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS1632I

'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 default value for the option

User response:

To override the default, specify a valid value for the option. Consult
documentation for valid values.

------------------------------------------------------------------------
ANS1647E

'input spec': Invalid input specification format.



Explanation:

The specified input for this commmand is invalid.

System action:

The operation stops.

User response:

Verify that the syntax specified with the parameter is correct.

------------------------------------------------------------------------
ANS1648W

PREViewsize option value is greater than the specified stub size.



Explanation:

The PREViewsize CLI option value specified must not be greater than the
stub size for the file.

System action:

Operation stopped. File skipped.

User response:

Change the value of the PREViewsize accordingly.

------------------------------------------------------------------------
ANS1649E

The option 'specified-option' is inconsistent with the option
'other-option'.



Explanation:

The command failed because the the two options cannot be used at the
same time.

System action:

The command is stopped.

User response:

Run the command and do not specify both options.

------------------------------------------------------------------------
ANS1650I

Command: command-string



Explanation:

The command string listed in the message was issued by the
backup-archive client.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1651I

Backed Up: fshlll



Explanation:

The backup operation for the object was successful.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1652I

Archived: fshlll



Explanation:

The archive operation for the object was successful.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1653I

Updated: fshlll



Explanation:

The update operation for the object was successful.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1654E

Failed: fshlll



Explanation:

The backup, archive, restore or retrieve operation for the object
failed.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only. For information about the
failure refer to the backup-archive Client error log.

------------------------------------------------------------------------
ANS1655I

Restored: fshlll



Explanation:

The restore operation for the object was successful.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1656I

Retrieved: fshlll



Explanation:

The retrieve operation for the object was successful.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1657I

Expired: fshlll



Explanation:

The active version of the object was expired in the IBM Spectrum Protect
database.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1658I

Deleted: fshlll



Explanation:

The object was deleted from the IBM Spectrum Protect database.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1659I

Skipped: fshlll



Explanation:

The object was skipped by the user during backup or archive processing.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1660I

Excluded: fshlll



Explanation:

The object was excluded from backup or archive processing.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1661I

Unchanged: fshlll



Explanation:

The object has not changed since the last incremental backup was
performed and does not need to be resent.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1662I

Agent Node: 'agent_node' Target Node: 'target_node'



Explanation:

Proxy nodes information.

System action:

None

User response:

None

------------------------------------------------------------------------
ANS1663W

The option fractional reserve on volume vol_name was reduced to less
than 100 percent.



Explanation:

Network Appliance strongly recommends that when the fractional reserve
is set to less than 100 percent you actively monitor space consumption
and the rate of change of data in the volume to ensure you do not run
out of space reserved for overwrites. In that case, if you run out of
overwrite reserve space, writes to the active file system fail and the
host application or operating system might crash.

System action:

Process continues.

User response:

Ensure that you monitor the space consumption. Consult Network Appliance
for tools to monitor available space in your volumes.

------------------------------------------------------------------------
ANS1664E

The snap restore for volume volname with snapshot name snapname would
destroy later snapshots that are required for other applications or for
volume clones.



Explanation:

ONTAP will delete newer snapshots of a volume when a specific snapshot
is used for snap restore.

System action:

Process stops.

User response:

Prior to a snap restore, ensure that newer snapshots are not used in
other applications or in volume clones.

------------------------------------------------------------------------
ANS1665W

IBM Spectrum Protect for ACS did not find any snapshots for volume
volname on the N series filer.



Explanation:

No snapshots were found for this volume on the N series filer.

System action:

Process continues.

User response:

None.

------------------------------------------------------------------------
ANS1666W

IBM Spectrum Protect for ACS did not find any information about the N
series volume volname.



Explanation:

The query for information about this volume did not return any data.

System action:

Process continues.

User response:

None.

------------------------------------------------------------------------
ANS1667E

The snapshot name snapname for volume volname was not found in the
snapshot list on the N series filer.



Explanation:

Snapshot identified by this name does not exist.

System action:

Process stops.

User response:

None.

------------------------------------------------------------------------
ANS1668E

The 'drive-name1' is not a local disk.



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.

User response:

If the CLUSTERNODE option is incorrectly set to YES, then change the
option to NO and try the operation again. Otherwise see the client
manual for further information about configuring the IBM Spectrum
Protect client to run in a cluster environment.

------------------------------------------------------------------------
ANS1669W

The command subcommand command can only be run in Windows WinPE mode.



Explanation:

The command subcommand command is not supported on a currently running
operating system. You must reboot to Windows WinPE mode to run this
command.

System action:

The command is not processed.

User response:

None.

------------------------------------------------------------------------
ANS1670E

The file specification is not valid. Specify a valid Network Appliance
or N-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 Network
Appliance or N-Series NFS volumes on AIX and Linux, and on CIFS volumes
on Windows. Do not specify either Network Appliance or N-Series Qtrees
or a path within the Network Appliance or N-Series volume. Only full
volumes are supported.

System action:

Processing stops.

User response:

Retry the incremental backup operation using the -SNAPDIFF option.
Specify a valid Network Appliance or N-Series NFS volume on AIX or
Linux, or a CIFS volume on Windows.

------------------------------------------------------------------------
ANS1672I

Could not take the cluster resource resource name offline. MS rc
retcode. Error is ignored.



Explanation:

Microsoft recommends taking the cluster resources offline during an
authoritative cluster database restore. However, the restore can still
be done if the resources cannot be taken offline. The error is ignored.

System action:

Processing continues.

User response:

No action.

------------------------------------------------------------------------
ANS1673W

Cluster service on node node name could not be started. You must
manually start the service.



Explanation:

The cluster database has been restored. During the restore, the cluster
service was taken offline. IBM Spectrum Protect failed to restart the
cluster service.

System action:

Processing continues.

User response:

You can manually start the service for this node.

------------------------------------------------------------------------
ANS1674I

The cluster database has been restored but the cluster service on some
nodes could not be started. Use the Failover Cluster Management tool to
manually start the nodes.



Explanation:

The cluster database has been restored. During the restore, the cluster
services were taken offline except for the node being restored. IBM
Spectrum Protect failed to automatically start these cluster services.
You need to start them manually. The nodes whose services failed to
start are logged in the client error log.

System action:

Processing continues.

User response:

You can manually start the cluster services.

------------------------------------------------------------------------
ANS1675W

Unable to obtain a list of cluster nodes to restart after the cluster
database is restored. The call 'cmd' returned with MS rc retcode. You
must restart the cluster service on all the nodes after the restore is
finished.



Explanation:

Due to an error, IBM Spectrum Protect could not retrieve a list of nodes
in the cluster to restart. The cluster services on these nodes need to
be started manually. The client error log might contain additional
information depending on where the failure occured.

System action:

Processing continues.

User response:

Manually start the cluster services on all nodes.

------------------------------------------------------------------------
ANS1676W

You are doing an authoritative cluster database restore. The process may
seem to be hang before and after the file is restored. This is because
it may need to start the cluster service if it is not up and take all
the resources offline. After the cluster database is restored, the
cluster service will be restarted for changes to be in effect. The
cluster service on all other nodes also have been shutdown. They will be
restarted. This may take a few minutes.



Explanation:

The restore will seem to be paused at time because before the restore,
IBM Spectrum Protect ensures the cluster service is up on the restoring
node and all the resources are taken offline. After the cluster database
is restored, the cluster service on the restoring node is in a paused
state. The cluster service on other nodes were shutdown. All services
need to be retarted. If some of the services cannot be started
automatically, you can try to restart them.

System action:

Processing continues.

User response:

No action.

------------------------------------------------------------------------
ANS1677W

IBM Spectrum Protect failed to set the disks for quick formatting
because of an error. See the error log for more details. The disks will
be slow formatted which will cause a slower restore process.



Explanation:

By default, IBM Spectrum Protect tries to set the QuickFormat value of
the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ASR\RestoreSession key to perform quick formatted on
all the disks. Due to an error, a slow format will be performed on the
re-creation of the disks. This process will cause a slower restore
process.

System action:

None

User response:

None

------------------------------------------------------------------------
ANS1678E

ASR path 'path': not found.



Explanation:

You have specified a directory that does not exist.

System action:

Processing stops.

User response:

Recheck all spelling and punctuation, particularly the placement of
directory delimiters (for example, "\"). Correct the syntax if it is
incorrect, then retry the operation.

------------------------------------------------------------------------
ANS1679W

Updating the registry to identify which volumes have been restored has
failed. This does not affect the volumes that have already been
restored. See the error log for more details. The error is being ignored
and processing continues.



Explanation:

After restoring the critical volumes, IBM Spectrum Protect tries to
update the RestoredVolumes value of the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ASR\RestoreSession key to indicate which volumes have
been restored. Due to an error accessing the registry, the error is
logged but processing continues.

System action:

Processing continues.

User response:

None

------------------------------------------------------------------------
ANS1680E

Snapshot Differential Backup is only available for data protection
(SnapVault or SnapMirror) volumes. Volume 'NetApp-Volume' is not a
SnapVault or SnapMirror volume.



Explanation:

The NetApp License only allows using snapshot differencing for data
protection (SnapVault or SnapMirror) volumes.

System action:

The command is not processed.

User response:

None.

------------------------------------------------------------------------
ANS1681E

DSM_DIR was not set and the ASRFILESPATH option was not specified.



Explanation:

The ASR files can be in put in the DSM_DIR path by default or overriden
with the ASRFILESPATH option. Either one is being set.

System action:

Processing stops.

User response:

Set the DSM_DIR environment variable or specify the ASRFILESPATH option
on the "RESTORE MACHINEASR" command.

------------------------------------------------------------------------
ANS1682E

Volume 'NetApp-Volume' is a read only data protection (SnapMirror or
SnapVault) volume. Snapshot Differential Backup snapshots cannot be
created on a read only volume, the USEEXISTINGBASE and
DIFFSNAPSHOT=latest options must be specified to select existing
snapshots for use by the backup.



Explanation:

The specified NetApp volume is read only which prohibits snapshots used
by Snapshot Differential Backup from being created. The USEEXISTINGBASE
and DIFFSNAPSHOT=latest options specify using existing snapshots and may
be used in conjunction with the BASESNAPSHOTNAME and DIFFSNAPSHOTNAME
options.

System action:

The command is not processed.

User response:

Use appropriate options for specifying existing snapshots.

------------------------------------------------------------------------
ANS1684W

Disk Full Error Accessing Subfile Cache: exception-name



Explanation:

A disk full error occurred attempting to access or write to the
specified subfile cache file during a subfile incremental backup. See
the client error log for more detailed information.

System action:

Processing continues without subfile.

User response:

None.

------------------------------------------------------------------------
ANS1685E

Incremental backup operation using snapshot difference is only available
for N series/NetApp filer volumes, is not a NetApp volume.



Explanation:

Cannot perform NAS NFS/CIFS incremental backup operation using snapshot
difference on the mounted or mapped volume because the volume is not a N
series/NetApp filer volume.

System action:

Processing stops.

User response:

Retry the incremental backup operation by specifying an entire NAS NFS
or CIFS volume.

------------------------------------------------------------------------
ANS1686I

Single Instance Store link 'file-name' will be restored or retrieved as
a normal file.



Explanation:

IBM Spectrum Protect restores Single Instance Store (SIS) links as
normal files. If the restored version is a duplicate of of the copy in
the SIS Common Store, then the SIS Groveler will eventually recreate the
SIS link.

System action:

The process creates normal files instead of the reparse point.

User response:

None

------------------------------------------------------------------------
ANS1687E

VSS Instant Restore operation failed. Please examine the IBM Spectrum
Protect client error log file (DSMERROR.LOG), the Windows Application
Event Log, the Windows System Event Log, and the VSS provider log file
(if applicable) for more details. Consult the VSS provider documentation
for the meaning of the error return code.



Explanation:

VSS hardware provider failed while performing volume-level copy restore
operation.

System action:

Processing stopped.

User response:

Attempt to determine the source of the error by examining the
Application Client log file, the client error log file (DSMERROR.LOG),
the Windows Application Event Log, the Windows System Event Log, and the
VSS provider log file, if applicable. Additional instructions for
Windows VSS operations are located in the IBM Spectrum Protect Problem
Determination Guide. Correct the problem and retry the operation. If
this error persists, contact your service representative.

------------------------------------------------------------------------
ANS1688I

Sparse attributes for 'file-name' cannot be backed up correctly because
the volume from which the file is backed up does not support sparse
files.



Explanation:

If the volume from which a file is backed up does not support sparse
files, then the allocated ranges for the sparse file cannot be backed
up. This is true even if a file has its sparse attribute set. One
example where this can occur is if a sparse file is created on a NAS
volume, but the volume is backed up over CIFS, where CIFS does not
support sparse files.

System action:

The sparse attribute and allocated ranges for the file are not backed
up. If the file is restored, the restored file will not be sparse.

User response:

No action is required if you do not need the sparse attribute and
allocated ranges backed up. If you require backup of the file's sparse
attribute and allocated ranges, then the volume from which IBM Spectrum
Protect backs up the file must support sparse files.

------------------------------------------------------------------------
ANS1689E

The registry was not updated after VSS ASR restore.



Explanation:

An error occurred while updating the registry after VSS Automated System
Recovery (ASR). Check dsmerror.log for more information.

System action:

Processing stops.

User response:

Ask your system administrator to check the error log.

------------------------------------------------------------------------
ANS1690E

Snapshot Differential Backup is only available for data protection
(SnapVault or SnapMirror) volumes. Volume 'NetApp-Volume' is not a
SnapVault or SnapMirror volume.



Explanation:

The NetApp licensing agreement for using snapshot differencing only
allows backing up data protection (SnapVault or SnapMirror) volumes.

System action:

Processing stopped.

User response:

none

------------------------------------------------------------------------
ANS1691I

The option 'option' that was found in the options file 'file-name' at
the line number: number is not supported and will be ignored by the
client.



Explanation:

The specified option is valid but not supported on the current platform
and will be ignored by the client.

System action:

Processing continues.

User response:

You can ignore the message or remove the option from the option file.

------------------------------------------------------------------------
ANS1692E

The certificate is not trusted.



Explanation:

The client was unable to open SSL connection to the server because the
server certificate was not trusted.

System action:

Processing stopped

User response:

Make sure that you have configured the key database for SSL
communication as described in the documentation. If the IBM Spectrum
Protect server is using a self-signed certificate, make sure that you
import the correct certificate from the server you are trying to connect
to. When the server is using a certificate signed by an authority, make
sure that the root certificate of the authority is imported into the
client key database.

------------------------------------------------------------------------
ANS1693E

The certificate validity period is incorrect.



Explanation:

The client was unable to open an SSL connection to the server because
the certificate validity period is incorrect.

System action:

Processing stopped

User response:

Report this to the IBM Spectrum Protect server administrator. The server
must have the correct certificate installed.

------------------------------------------------------------------------
ANS1694E

The certificate identity could not be verified.



Explanation:

The process was unable to open an SSL connection to the server because
the certificate identity could not be verified. This happens when the
certificate ownership information does not match the IBM Spectrum
Protect domain name or IP address.

System action:

Processing stopped

User response:

Make sure that the server domain name or the IP address (the value of
the TCPSERVERADDRESS option) is correct. If the problem persists, report
it to your IBM Spectrum Protect server administrator.

------------------------------------------------------------------------
ANS1695E

The certificate is not valid.



Explanation:

The process was unable to open an SSL connection to the server because
of an invalid certificate. The client was unable to determine the exact
cause of the failure.

System action:

Processing stopped

User response:

Further analysis of the server certificate, the client key database, or
both, is needed. Refer to IBM Spectrum Protect documentation for more
information.

------------------------------------------------------------------------
ANS1696E

Only root can perform this action.



Explanation:

User must be root to perform this action.

System action:

Processing stopped.

User response:

Log in as root and try the operation again.

------------------------------------------------------------------------
ANS1698I

The option 'option_name' that was found in the command is not supported
and will be ignored by the client.



Explanation:

The specified option is valid but not supported on the current platform
and will be ignored by the client.

System action:

Processing continues.

User response:

Remove the specified option from the command line, and try again.

------------------------------------------------------------------------
ANS1700W

Database 'database' (save date=date) was successfully recovered.



Explanation:

The specified database (which was saved on the specified date) was
successfuly recovered.

System action:

The specified database was recovered with the last saved version.

User response:

none.

------------------------------------------------------------------------
ANS1704W

Option 'option-name' can not be supplied by application and is ignored.



Explanation:

An API application supplied option. The option cannot be specified by an
application. The option 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.

------------------------------------------------------------------------
ANS1705E

System Writers writersname do not exist.



Explanation:

These writers are an essential part of the operating system. When they
are not available the backup will complete successfully but the data for
those writers will not get backed up to the IBM Spectrum Protect server.
This can result in the computer not 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 operation again. If the problem persists, contact your system
administrator or IBM Spectrum Protect administrator for further help.

------------------------------------------------------------------------
ANS1706E

Error creating directory ' directory'.



Explanation:

The system was unable to create the specified directory.

System action:

Processing terminates.

User response:

Verify that the system has the appropriate permissions to create this
directory, and then restart the operation.

------------------------------------------------------------------------
ANS1707E

Hard link 'new-file-name' could not be created for existing file
'exist-file-name'. Microsoft Windows return code: 'windows-return-code'
'windows-error-text'



Explanation:

Some system state files are hard links that point to another file.
During system state restore, IBM Spectrum Protect recreates the hard
links for restored system state files. If a file with the same name as
the hard link already exists at the time of the restore, IBM Spectrum
Protect attempts to replace the file with the hard link. This message is
issued when IBM Spectrum Protect is unable to replace an existing file
with a hard link. The message includes the hard link name, the system
state file name to which the hard link points and the Microsoft Windows
return code information. The return code information indicates why the
file could not be replaced. It is possible for the operating system or
applications to behave erratically if the hard link cannot be recreated.

System action:

The hard link is skipped, system state restore continues.

User response:

Use the Microsoft Windows return code information provided in the
message to determine the underlying cause of the error. Based on the
underlying cause of the error and the reason you are restoring the
system state, you can choose to either correct the underlying cause and
perform the restore again, or you can attempt to manually create the
hard link. Because this error message represents an unusual and
unexpected condition, you should give careful consideration to the
potential consequences of either choice. The hard link can be created
manually as follows: Rename the file that has the same name as the hard
link. Then use the Microsoft Windows utility fsutil.exe as follows:
FSUTIL HARDLINK CREATE hardlinkname originalfilename

------------------------------------------------------------------------
ANS1708E

Backup operation failed. Only a root user can do this operation.



Explanation:

Backups initiated by non-root users are disabled by IBM Spectrum Protect
administrator.

System action:

The operation stops.

User response:

Request the IBM Spectrum Protect administrator to enable non-root
backups.

------------------------------------------------------------------------
ANS1710I

Rebound: fshlll



Explanation:

The active version of the object was rebound to a MC in the IBM Spectrum
Protect database.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS1711E

Unable to access disk 'disk name' of VM 'vmname' during backup.



Explanation:

The client is unable to access the VM disk. In case of an offload
backup, this might happen if an RDM disk exists in the VM and is not
accessible on the auxilary ESX host.

System action:

The virtual machine is not backed up.

User response:

Ensure that the VM disk is accessible on the ESX.

------------------------------------------------------------------------
ANS1712W

Operation on snapshot of a snapshot volume 'uncVolumePath' is not
supported for the disk provider type 'LUN-provider-name'
(LUN-provider-type).



Explanation:

Functionality is not available on this type of LUN.

System action:

Operation continues.

User response:

Delete manually the LUN on the storage device or subsystem.

------------------------------------------------------------------------
ANS1714E

A file space already exists for virtual machine (VM_name), but with a
different virtual machine UUID, than the current virtual machine UUID.



Explanation:

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 Spectrum 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:

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 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
   Spectrum Protect servers.

If the VM's UUID changed, run a BACKUP VM command with
VMBACKUPUPDATEGUID option. The VMBACKUPUPDATEGUID option updates the
UUID on the IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS1715E

A file space already exists for virtual machine (VM_name), but with a
different virtual machine UUID (VM_UUID) than the current virtual
machine UUID (VM_UUID).



Explanation:

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 Spectrum 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:

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 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
   Spectrum Protect servers.

If the VM's UUID changed, run a BACKUP VM command with
VMBACKUPUPDATEGUID option. The VMBACKUPUPDATEGUID option updates the
UUID on the IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS1716E

A VMware vStorage web service task timed-out.



Explanation:

The IBM Spectrum Protect client timed-out waiting for VMware vCenter or
ESX host to complete a requested web service task. Resources could be
low or the system could be busy.

System action:

Processing stopped

User response:

Please check the VMware vCenter or ESX host for errors.

------------------------------------------------------------------------
ANS1717E

A VMware vStorage web service task failed.



Explanation:

A VMware vCenter or ESX host web service task failed.

System action:

Processing stopped

User response:

Please check the VMware vCenter or ESX host for errors.

------------------------------------------------------------------------
ANS1729E

The passed file list 'file-list' is not a valid input file list. Pass
standard file list or collection file list to the dsmrecall command.



Explanation:

User has passed a invalid file list type to the dsmrecall command

System action:

Processing stopped

User response:

pass standard file list or collection file list to dsmrecall command.

------------------------------------------------------------------------
ANS1730E

The IBM Spectrum Protect server query for ordering information failed.



Explanation:

Tape optimized recall was not able to retrieve ordering information from
the IBM Spectrum Protect server.

System action:

Processing stopped

User response:

Check the connection to the IBM Spectrum Protect server to see if the
IBM Spectrum Protect server is available and you have the correct access
rights configured.

------------------------------------------------------------------------
ANS1731E

Tape optimized recall for file list 'file-list' failed with rc = code.



Explanation:

Tape optimized recall was not able to retrieve ordering information from
the IBM Spectrum Protect server.

System action:

Processing stops.

User response:

Check all error messages above this message to get details about the
problem.

------------------------------------------------------------------------
ANS1732W

File 'file' is from a different file system. writing file to list of
unprocessed files: 'file-list'.



Explanation:

The dsmrecall command specifies a file system to process. Files from
other file systems are skipped and written into a unprocessed list.

System action:

File is skipped and information is written to a list of unprocessed
files

User response:

Check that all files in the input file list are from the correct file
system.

------------------------------------------------------------------------
ANS1733I

A collection file was specified 'file-list' The ordering process is
skipped.



Explanation:

A collection file was passed as the input file list. Ordering is not
necessary since it the file is already ordered. Only the recall is
started.

System action:

The ordering processed is not started, only recall started.

User response:

No further action needed.

------------------------------------------------------------------------
ANS1734W

The virtual machine 'VM-name' contains one or more independent disks.
Backups are not supported in this configuration. Specify the
'-vmprocessvmwithindependent=yes' option to exclude these disks from the
backup.



Explanation:

Independent disks are not affected by snapshots so the IBM Spectrum
Protect client does not support backing them up.

System action:

The virtual machine is not backed up.

User response:

Turn off the virtual machine and change the disk independent mode or
remove them from the virtual machine. Or specify the
'-vmprocessvmwithindependent=yes' option to exclude these disks from the
backup.

------------------------------------------------------------------------
ANS1735W

The virtual machine 'VM-name' contains one or more physical Raw Device
Mappings (RDMs). Backups are not supported in this configuration.
Specify the '-vmprocessvmwithprdm=yes' option to exclude these disks
from the backup.



Explanation:

Physical RDMs are not included in snapshots so the IBM Spectrum Protect
client does not support backing them up.

System action:

The virtual machine is not backed up.

User response:

Turn off the virtual machine and change the RDMs to virtual mode or
remove them from the virtual machine. Or specify the
'-vmprocessvmwithprdm=yes' option to exclude these disks from the
backup.

------------------------------------------------------------------------
ANS1736W

The virtual machine 'VM-name' cannot be backed up because it contains
one or more disks of an unsupported type.



Explanation:

IBM Spectrum Protect does not support virtual machines with unsupported
disk types.

System action:

The virtual machine is not backed up.

User response:

Convert unsupported disks to a supported type, or remove the unsupported
disks from the virtual machine, or exclude the virtual machine from
backup.

------------------------------------------------------------------------
ANS1737E

The PRESNAPSHOTCMD command failed.



Explanation:

The command specified by the PRESNAPSHOTCMD option must complete
successfully in order to perform the VSS snapshot backup. If the command
completed with a return code of 0 (zero), it is considered to have
completed successfully. If the command completed with any other return
code, it is considered to have failed. If the command failed then the
VSS snapshot backup is not performed.

System action:

The client does not perform the VSS snapshot backup operation.

User response:

Identify and repair the problem that caused the command to fail. If a
non-zero return code is normal for this command, consider wrapping the
command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS1738W

The POSTSNAPSHOTCMD command failed.



Explanation:

If the command specified by the POSTSNAPSHOTCMD option completed with a
non-zero return code, the VSS snapshot backup operation continues. The
operation continues with a warning-level result. The result of the
POSTSNAPSHOTCMD command does not supersede a higher result from the VSS
snapshot backup command. For example, if the VSS snapshot backup command
completed with code 12, a lower return code from the POSTSNAPSHOTCMD
command does not alter the return 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 that caused the command to fail.
Consider wrapping the command in a script that always exits with a
return code of zero.

------------------------------------------------------------------------
ANS1739E

Restore of a system drive is not permitted.



Explanation:

The drive to which you are restoring contains the operating system.

System action:

Processing stops.

User response:

Try the operation again without specifying a system drive.

------------------------------------------------------------------------
ANS1740W

Unable to read ACLs for object: file_system path name. Check
dsmerror.log for more information.



Explanation:

The ACLs of the object are not read.

System action:

The object is skipped. Processing continues with the next object.

User response:

Examine the client error log for additional messages that might indicate
the reason for the problem. Try to follow the suggested corrective
actions (if any) and try the operation again.

------------------------------------------------------------------------
ANS1741W

Unable to read extended attributes for file_system path name. Check
dsmerror.log for more information.



Explanation:

The extended attributes of the object are not read.

System action:

The object is skipped. Processing continues with the next object.

User response:

Examine the client error log for additional messages that might indicate
the reason for the problem. Follow the suggested corrective actions (if
any) and try the operation again.

------------------------------------------------------------------------
ANS1742E

Expose Snapshot failed for backup 'backup-name'.



Explanation:

Expose snapshot failed.

System action:

Processing stops

User response:

See the dsmerror.log file for further details.

------------------------------------------------------------------------
ANS1743E

Unexpose snapshot failed for backup 'backup-name'.



Explanation:

Unexpose snapshot failed.

System action:

Processing stops

User response:

See the dsmerror.log file for further details.

------------------------------------------------------------------------
ANS1744E

One or more of the snapshots(volumes) needed for the restore operation
were not found. See dsmerror.log for further details.



Explanation:

One or more of the snapshots needed for restore were not found on the
system.

System action:

Processing stops

User response:

See the dsmerror.log file for further details.

------------------------------------------------------------------------
ANS1745I

The virtual machine to restore has one or more distributed port groups.
Further configuration might be necessary to select a port number after
the restore is complete.



Explanation:

The virtual machine was saved with one or more NIC cards backed by
distributed port groups. Due to conflicts on restore the port number(s)
were not saved.

System action:

The restore continues.

User response:

Edit the virtual machine settings and select a port if needed.

------------------------------------------------------------------------
ANS1746E

No available LUNs were found. Confirm that the storage adapters are
configured correctly on the host and that the LUNs are not mapped to
another virtual machine.



Explanation:

The virtual machine was stored with a Raw Device Mappings disk backed by
a LUN. The required LUN is missing or still mapped to another virtual
machine.

System action:

The virtual machine cannot be restored.

User response:

Confirm that the Storage Adapters are configured correctly on the host
and that the LUNs are not mapped to another virtual machine.

------------------------------------------------------------------------
ANS1747E

Encryption key password is not available.



Explanation:

The client is not enabled for encrypted backup/restore operations by
non-authorized users or the encryption key password is not stored by the
administrator.

System action:

Objects that cannot be encrypted or decrypted are skipped.

User response:

Contact the administrator for your system to configure encrypted
operations for non-authorized users.

------------------------------------------------------------------------
ANS1748E

The virtual machine was stored with a Raw Device Mappings disk backed by
a LUN. The required LUN is missing or still mapped to another virtual
machine: LUN UUID lun.



Explanation:

The virtual machine was stored with a Raw Device Mappings disk backed by
a LUN. The required LUN is missing or still mapped to another virtual
machine.

System action:

The virtual machine cannot be restored.

User response:

Find the required LUN and make it available to the virtual machine.

------------------------------------------------------------------------
ANS1749W

Object 'filespace-namehl-namell-name' was backed up with invalid file
system type attribute.



Explanation:

File system type is used by the client to determine if an object name is
case sensitive or not. Wrong file system type may result in incorrect
sort order of the server tree for case sensitive file systems. Finally
some unchanged files may expire and then re-backed up during full
incremental backup.

System action:

Processing continues.

User response:

It is recommended to rename the correspondent filespace on IBM Spectrum
Protect server and do the full incremental backup again.

------------------------------------------------------------------------
ANS1750I

Volume mount point 'volumemountpoint' is mounted to volume 'volume'.
Using snapshot volume for 'volume' to backup.



Explanation:

The volume mount point resolved to a volume that has been snapped. The
same snapshot volume will be used.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1751E

Error processing 'filespace name': The file system can not be accessed.



Explanation:

The client is unable to access the file system. Two common reasons for
this are the account under which the client is running does not have
access to the root of the file system, or the file system does not
exist.

System action:

The inaccessible file system is skipped. Processing continues with the
next file system.

User response:

Check the error log for additional messages that might yield additional
information about the problem that prevents access to the file system.
Correct the problem, then retry the operation. If the account does not
have access to the file system, then either the system administrator
needs to grant access, or an account that has access to the file system
must be used. If the file system does not exist, then remove or correct
the file system specification.

------------------------------------------------------------------------
ANS1752E

The file system can not be accessed.



Explanation:

The client is unable to access the file system. Two common reasons for
this are the account under which the client is running does not have
access to the root of the file system, or the file system does not
exist.

System action:

The inaccessible file system is ignored.

User response:

Check the error log for additional messages that might yield additional
information about the problem that prevents access to the file system.
Correct the problem, then retry the operation. If the account does not
have access to the file system, then either the system administrator
needs to grant access, or an account that has access to the file system
must be used. If the file system does not exist, then remove or correct
the file system specification.

------------------------------------------------------------------------
ANS1753E

File space 'filespace name' was backed up by an older client version,
and cannot be restored with this client version. The file space will be
skipped.



Explanation:

The backup set format in earlier client versions for SYSTEM STATE and
SYSTEM SERVICES is incompatible with the current client version. Those
file spaces will be skipped. The restore might appear to pause while the
client skips past the objects in those file spaces. 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:

Restore this specific file space in the backupset with a prior level
client.

------------------------------------------------------------------------
ANS1754E

File space 'filespace name' cannot be restored when ASNODENAME option is
in affect. The file space will be skipped.



Explanation:

System state data of another node should not be restored to a different
node. Those file spaces will be skipped. The restore might appear to
pause while the client skips past the objects in those file spaces.
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 before restoring this specific file space in
the backupset or use the node name that was used to backup system state
data to restore.

------------------------------------------------------------------------
ANS1755W

An error communicating with Active Directory has occurred. The
USEDIRECTORY option will be ignored and processing will continue.



Explanation:

The process attempted to query Active Directory for IBM Spectrum Protect
server parameters but an error has occurred. This could be caused by
Active Directory or the IBM Spectrum Protect server configuration.

System action:

IBM Spectrum Protect will ignore the USEDIRECTORY option and continue
with client processing.

User response:

Make sure your computer is properly set up to the domain with Active
Directory. Also, make sure your IBM Spectrum Protect Administrator has
properly configured the IBM Spectrum Protect server for your node.

------------------------------------------------------------------------
ANS1756W

The Journal for 'backup-specification' has been reset: The server
filespace was deleted since the last backup completed.



Explanation:

The client has reset the journal because the corresponding server
filespace was deleted since the last backup completed.

System action:

The journal is reset, the current backup won't use the journal, and the
journal won't be available for backup until a full incremental backup
successfully completes.

User response:

None.

------------------------------------------------------------------------
ANS1757W

The Journal for 'backup-specification' has been reset: The server
filespace was deleted since the last backup completed.



Explanation:

The client has reset the journal because the corresponding server
filespace was deleted since the last backup completed.

System action:

The journal is reset, the current backup won't use the journal, and the
journal won't be available for backup until a full incremental backup
successfully completes.

User response:

None.

------------------------------------------------------------------------
ANS1758W

The Journal for 'backup-specification' has been reset: The server
filespace was deleted since the last backup completed.



Explanation:

The client has reset the journal because the corresponding server
filespace was deleted since the last backup completed.

System action:

The journal is reset, the current backup won't use the journal, and the
journal won't be available for backup until a full incremental backup
successfully completes.

User response:

None.

------------------------------------------------------------------------
ANS1759W

The Journal for 'backup-specification' has been reset: The policy set
was updated since the last backup completed.



Explanation:

The client has reset the journal for the specified file system because
the node policy set was updated since the last backup completed.

System action:

The journal is reset, the current backup won't use the journal, and the
journal won't be available for backup until a full incremental backup
successfully completes.

User response:

None.

------------------------------------------------------------------------
ANS1760I

Journal for 'backup-specification' enabled for node 'nodename' and
server 'servername'



Explanation:

The journal for the specified file system is now valid and will be used
by the next full incremental backup by the specified IBM Spectrum
Protect node and server.

System action:

The next full incremental backup of the file system will use the
journal.

User response:

None.

------------------------------------------------------------------------
ANS1761I

Journal for 'backup-specification' will be enabled upon successful
completion of the backup.



Explanation:

An active but invalid journal is present for the file system being
backed up. Once the backup successfully completes the journal will
available for use by the next full incremental backup of the file system
with the same IBM Spectrum Protect node and server.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS1763W

Unable to unmount snapshot mount point snapshot mountpoint during
cleanup of snapshot 'snapshot' of volume 'volume'.Error is
'error'.Operation will continue. Please manually unmount, remove the
snapshot mount point directory and delete the snapshot after backup is
completed.



Explanation:

During the termination phase of IBM Spectrum Protect client operation,
it was not possible to unmount the snapshot for some reason. However,
IBM Spectrum Protect operation was completed successfully.

System action:

Processing continues, and the unmount error is ignored.

User response:

Please manually cleanup the snapshots as follows: Query the snapshot:
snapshot -q -c: <source FS>. Snapshot name will be of the format:
tsmxxxxxxxxxx. Check if it is mounted: df -k | grep tsmxxxxxxxxxx.
Unmount the snapshot: umount -f tsmxxxxxxxxxx. Remove snapshot mount
point: rmdir tsmxxxxxxxxxx. Delete the snapshot: snapshot -d
/dev/tsmxxxxxxxxxx. If snapshot delete fails with "Device Busy" or some
other error, unmount the snapshot source filesystem: umount -f <source
FS>. Retry snapshot delete: snapshot -d /dev/tsmxxxxxxxxxx. Check if any
logical volumes are remaining: ls -l /dev/tsm*. Remove any remaining
logical volumes: rmlv -f tsmxxxxxxxxxx. Remount source file system, if
previously unmounted: mount <source FS>.

------------------------------------------------------------------------
ANS1764W

Unable to remove the snapshot mount point directory snapshot mountpoint
during cleanup of snapshot 'snapshot' of volume 'volume'.Error is
'error'.Operation will continue. Please manually remove the snapshot
mount directory and delete the snapshot after backup is completed.



Explanation:

During the termination phase of IBM Spectrum Protect client operation,
it was not possible to remove the mount point directory for the snapshot
for some reason. However, IBM Spectrum Protect operation was completed
successfully.

System action:

Processing continues, and the rmdir error is ignored.

User response:

Please manually cleanup the snapshots as follows: Query the snapshot:
snapshot -q -c: <source FS>. Snapshot name will be of the format:
tsmxxxxxxxxxx. Check if it is mounted: df -k | grep tsmxxxxxxxxxx.
Unmount the snapshot: umount -f tsmxxxxxxxxxx. Remove snapshot mount
point: rmdir tsmxxxxxxxxxx. Delete the snapshot: snapshot -d
/dev/tsmxxxxxxxxxx. If snapshot delete fails with "Device Busy" or some
other error, unmount the snapshot source filesystem: umount -f <source
FS>. Retry snapshot delete: snapshot -d /dev/tsmxxxxxxxxxx. Check if any
logical volumes are remaining: ls -l /dev/tsm*. Remove any remaining
logical volumes: rmlv -f tsmxxxxxxxxxx. Remount source file system, if
previously unmounted: mount <source FS>.

------------------------------------------------------------------------
ANS1765W

Unable to delete the snapshot during cleanup of snapshot 'snapshot' of
volume 'volume'.Error is 'error'. Operation will continue. Manually
delete the snapshot after backup is completed.



Explanation:

During a backup-archive client operation, it was not possible to delete
the snapshot for some reason. However, the operation was completed
successfully. The error could be caused by an unexpected order of
snapshot commands. AIX JFS2 expects the snapshot delete requests for a
given filesystem to be issued in the order of oldest snapshot first,
next oldest snapshot second, and so on. If there are other processes
using older snapshots for the same filesystem, it fails the delete
request. Also, the backup-archive client only deletes snapshots that
were created by one of its processes. It will not delete older snapshots
created by other applications or users. In this case, the user will have
to manually delete all the older snapshots so that the next
backup-archive command can complete successfully.

System action:

Processing continues, and the snapshot delete error is ignored.

User response:

Manually clean up the snapshots as follows: Query the snapshot: snapshot
-q -c: <source_FS> The snapshot name will be of the format:
tsmxxxxxxxxxx. Check if the snapshot is mounted: df -k | grep
tsmxxxxxxxxxx Unmount the snapshot: umount -f tsmxxxxxxxxxx Remove the
snapshot mount point: rmdir tsmxxxxxxxxxx Delete the snapshot: snapshot
-d /dev/tsmxxxxxxxxxx If the snapshot delete operation fails with
"Device Busy" or some other error, unmount the snapshot source
filesystem: umount -f <source_FS> Retry snapshot delete: snapshot -d
/dev/tsmxxxxxxxxxx Check if any logical volumes are remaining: ls -l
/dev/tsm* Remove any remaining logical volumes: rmlv -f tsmxxxxxxxxxx
Remount source file system, if previously unmounted: mount <source_FS>

------------------------------------------------------------------------
ANS1766E

Failed to initialize SSH2: rc=error-code.



Explanation:

Problem occurred during SSH2 initialization.

System action:

The operation stops.

User response:

Check network, DNS and connection settings to the target host or if SSH
is working properly.

------------------------------------------------------------------------
ANS1767E

Unable to create a snapshot logical volume using command: 'cmd'.Error is
'error'.Please ensure that the volume group has sufficient free
partitions to fulfill the allocation request.



Explanation:

During the initialization phase of IBM Spectrum Protect client
operation, it was not possible to create a logical volume for the
snapshot.

System action:

Processing continues, and the create snapshot logical volume error is
ignored. IBM Spectrum Protect operation will be performed without the
snapshot.

User response:

Please ensure that the volume group has sufficient free partitions to
fulfill the mklv allocation reuest and retry the operation.

------------------------------------------------------------------------
ANS1768E

IBM Spectrum Protect was unable to find space for a new snapshot. IBM
Spectrum Protect function name : function-name IBM Spectrum Protect
function : function-desc IBM Spectrum Protect return code : TSM-rc IBM
Spectrum Protect file : file-name (line-number)



Explanation:

None.

System action:

Processing stops.

User response:

Previous backups may still be pending. If problem persists contact the
IBM Spectrum Protect administrator with the information provided in this
message.

------------------------------------------------------------------------
ANS1769E

NetApp file server 'server-name' at Data ONTAP version
'version.modification.submodification' is not supported for performing
incremental backups using snapshot difference.



Explanation:

Incremental backup using Snapshot difference requires Data ONTAP V7.3 or
later. However, if you are upgrading from Data ONTAP V7.3.3 or later to
V8.0, you will lose snapshot difference support for unicode file names.
Upgrade to Data ONTAP V8.1 or later.

System action:

Processing stops.

User response:

Upgrade the file server to a supported level of Data ONTAP, then retry
the operation.

------------------------------------------------------------------------
ANS1770E

Unable to resolve address 'tcpip address'. Error = error code, 'error
message'



Explanation:

The system was not able to get the TCP/IP v6 address.

System action:

Processing stopped

User response:

Verify the address shown is a TCP/IP v6 address and can be resolved with
ping or ping6.

------------------------------------------------------------------------
ANS1771W

The system state filespace 'filespace name' cannot be restored to a
different location.



Explanation:

The system state file space cannot be restored to a different location.
This file space is skipped.

System action:

Objects in the system state file space are skipped. Other remaining file
spaces are restored. The restore might appear to pause while the client
skips past the objects in this file space.

User response:

Restore system state to its original location.

------------------------------------------------------------------------
ANS1772E

Error loading the snapshot plugin. The plugin might not be installed.



Explanation:

The snapshot plugin could not be loaded, possibly because the plugin is
not installed.

System action:

The snapshot backup is stopped.

User response:

On Linux 86/86_64 platform, install the TIVsm-BAhdw package if it is not
already installed. Try the operation again. On AIX platform, install the
hdw and snphdw filesets if they are not already installed. Try the
operation again.

------------------------------------------------------------------------
ANS1773I

The virtual machine 'VM-name' contains one or more independent disks and
these disks are excluded from the VM backup.



Explanation:

You cannot perform a shapshot of independent disks. Specify the option
'-vmprocessvmwithindependent=yes' to skip these disks.

System action:

The virtual machine independent disks will not be backed up.

User response:

None.

------------------------------------------------------------------------
ANS1774I

The virtual machine 'VM-name' contains one or more physical Raw Device
Mappings (RDM) disks and these disks are excluded from the VM backup.



Explanation:

You cannot perform a shapshot of physical RDM disks. Specify the option
'-vmprocessvmwithprdm=yes' to skip these disks.

System action:

The virtual machine physical RDM disks are not backed up.

User response:

None.

------------------------------------------------------------------------
ANS1780E

writer-name failed to initialize and subscribe to VSS.



Explanation:

IBM Spectrum Protect encountered an error while creating writer-name
under control of the Windows Volume Shadow Copy Service (VSS). Examine
the IBM Spectrum Protect error log and Applications Event Log for
additional information about this error.

System action:

Processing ends.

User response:

Try the operation again. If the error persists, examine the IBM Spectrum
Protect error log and Windows event log for information related to this
error.

Restart the Windows Volume Shadow Copy Service (VSS), and try the
operation again.

In some cases, it is necessary to restart the machine to clear the VSS
error state.

------------------------------------------------------------------------
ANS1782E

writer-name failed to be stopped.



Explanation:

IBM Spectrum Protect encountered an error while stopping writer-name.
Examine the IBM Spectrum Protect error log and Applications Event Log
for additional information about this error.

System action:

Processing ends.

User response:

Try the operation again. If the error persists, examine the IBM Spectrum
Protect error log and Windows event log for information related to this
error.

Restart the Windows Volume Shadow Copy Service (VSS), then try the
operation again.

In some cases, it is necessary to retart the machine to clear the VSS
error state.

------------------------------------------------------------------------
ANS1784E

Incremental by snapshot difference cannot be performed on 'volume-name'
as it is a vFiler volume.



Explanation:

Snapshot difference incremental backup is not supported on vFiler
volumes.

System action:

Processing stops.

User response:

Perform snapshot difference incremental backup on normal NetApp/N-Series
volumes only.

------------------------------------------------------------------------
ANS1787I

The virtual machine NIC is backed by a distributed virtual port group
but it is missing the portgroupKey attribute, The NIC cannot be
restored.



Explanation:

The virtual machine NIC is missing the required portgroupKey attribute.

System action:

The virtual machine can be restored but the NIC cannot be restored.

User response:

After the virtual machine has been restored a new NIC card can be added.

------------------------------------------------------------------------
ANS1788I

The target ESX host is missing the required distributed virtual port
group, the virtual machine NIC cannot be restored. Use
VMDEFAULTDVPORTGROUP option to set to specify new port group. If target
ESXi server does not have any port groups, use VMDEFAULTNETWORK option.



Explanation:

The virtual machine NIC was backed by a distributed virtual port group
but the target ESX host is missing this port group.

System action:

The virtual machine can be restored but the NIC cannot be restored.

User response:

After the virtual machine has been restored a new NIC card can be added.

------------------------------------------------------------------------
ANS1789I

No Ddistributed virtual port group were found on the target ESX host.
The virtual machine NIC cannot be restored.



Explanation:

The virtual machine NIC was backed by a distributed virtual port group
but the target ESX host has no port group available.

System action:

The virtual machine can be restored but the NIC cannot be restored.

User response:

After the virtual machine has been restored a new NIC card can be added.

------------------------------------------------------------------------
ANS1790E

Volume 'volname' cannot be backed up because 'nosnapdir=on' is set on
the filer.



Explanation:

This message is issued when option 'nosnapdir=on' is in set for the
volume indicated in the message. When this option is set, the volume
snapshots are hidden and thus cannot be backed up.

System action:

The volume indicated in the message is not backed up. Processing
continues with the next volume.

User response:

To back up the volume, change the volume on the filer: Set option
'nosnapdir=off'. Then try the backup operation for this volume again. If
the volume is not backed up, remove it from the backup-archive client
DOMAIN setting.

------------------------------------------------------------------------
ANS1794I

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 NAS filer indicated in the message.

System action:

Processing continues.

User response:

Set option 'cifs.enable_share_browsing = on'. Then try the snapshot
difference backup operation again.

------------------------------------------------------------------------
ANS1795I

Operation will continue without using snapshot provider, because file
system 'volname' does not have write permissions.



Explanation:

The source file system for a snapshot should be read-write as by
definition a snapshot is a point-in-time snapshot of changing file
system. Snapshot creation updates the file system superblock which
requires the file system to be read-write

System action:

Processing continues without using snapshot provider.

User response:

If the volume needs to be backed up via snapshot provider, change its
permissions to read-write.

------------------------------------------------------------------------
ANS1796I

The short name for 'fullpath-name' could not be set to original short
name 'file-name': Windows function 'func-name' failed with return code
return-code, reason: 'error text'



Explanation:

The client cannot set the short name for the specified object. This is
usually because the short name is already in use by another object
located in the same directory. Another possible reason is that the
account under which the client is running does not have the
SE_RESTORE_NAME privilege.

System action:

The short name for the specified object is not set. The object will
retain the default short name. Otherwise processing continues.

User response:

This message is informational and can be safely ignored. If you require
that the object be restored with its original short name, you will need
to move or delete the conflicting object. From an operating system
command prompt, change to the directory that contains the object you
want to restore. Then use the \"dir /x\" command to identify the
conflicting object. Also make sure that you have the SE_RESTORE_NAME
privilege. If you need assistance, see your system administrator. After
the conflict has been resolved, try to restore the file again.

------------------------------------------------------------------------
ANS1797E

Function function-name received an unexpected error from the Microsoft
API MS-function-name: rc=error while attempting to access the object
'object-name'. Error occurred in file file-name (line-number).



Explanation:

An error occurred while processing the object. The error code indicates
the reason for the failure. This information can be used to diagnose the
problem.

System action:

The IBM Spectrum Protect client may or may not fail the operation,
depending on the code.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS1798W

An error occurred while accessing encrypted data of the object
'object-name', skipping object. Windows system error code error, reason
'error-reason'



Explanation:

An error occurred while processing encrypted data of the object. The
error information captured indicates the reason for the failure. This
information can be used to diagnose the problem.

System action:

Object skipped.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS1799I

The last access date for 'fullpath-name' could not be reset because the
file is read-only.



Explanation:

Option PRESERVELASTACCESSDATE YES is in effect, but the IBM Spectrum
Protect client was unable to reset the last access date for the
specified file because the file's "read only" attribute is enabled. The
client cannot reset the last access date for "read only" files.

System action:

The last access date for the specified file is not reset. Otherwise
processing continues.

User response:

This message is informational and can be safely ignored. You might want
to turn off the "read only" attribute for the file so that subsequent
backups can reset the last access date. Before turning off the
attribute, you should verify that doing so will not impact the integrity
of the file or the applications that use the file. You should also make
sure that turning off the attribute will not conflict with the file
management policies of your organization.

------------------------------------------------------------------------
ANS1800W

The last access date for 'fullpath-name' could not be reset: function
'func-name' failed with return code return-code



Explanation:

Option PRESERVELASTACCESSDATE YES is in effect, but the IBM Spectrum
Protect client was unable to reset the last access date for the
specified file. The message includes the name of the function that
failed and the return code from that function.

System action:

The last access date for the specified file is not reset. Otherwise
processing continues.

User response:

If the problem is reproducible, obtain a SERVICE trace that captures an
instance of this problem. Run the QUERY SYSTEMINFO command and collect
the dsminfo.txt file. Contact IBM support and report the exact text of
this error message. Be sure to provide support with the dsminfo.txt and
dsmerror.log files and (if available) the SERVICE trace.

------------------------------------------------------------------------
ANS1801E

Unable to register the new ID with server.



Explanation:

The reasons of this problem can be lack of client system memory or
server protocol error. The IBM Spectrum Protect activity log might
contain a corresponding error message with further information about the
cause.

System action:

The new ID is not registered with the server.

User response:

Please check your network connection and try again after time. If the
error appears again, please contact your client machine administrator.

------------------------------------------------------------------------
ANS1802E

Incremental backup of 'file-name' finished with failCount failure(s)



Explanation:

This message is issued after completion of an incremental backup
operation for the named file specification when one or more objects in
that file specification could not be backed up.

System action:

Processing continues.

User response:

Examine the client error log for additional messages that indicate the
reasons that each failed object could not be backed up. Take any
corrective action as suggested by the messages.

------------------------------------------------------------------------
ANS1803E

Archive processing of 'file-space name' finished with failures.



Explanation:

This message is issued after completion of an archive operation for the
named file specification when one or more objects in that file
specification could not be archived.

System action:

Processing continues.

User response:

Examine the client error log for additional messages that indicate the
reasons that each failed object could not be archived. Take corrective
action as suggested by the messages.

------------------------------------------------------------------------
ANS1804E

Selective Backup processing of 'file-space name' finished with failures.



Explanation:

This message is issued after completion of a selective backup operation
for the named file specification when one or more objects in that file
specification could not be backed up.

System action:

Processing continues.

User response:

Examine the client error log for additional messages that indicate the
reasons that each failed object could not be backed up. Take any
corrective action suggested by those messages.

------------------------------------------------------------------------
ANS1805E

Unable to restore symbolic link 'file-name'.



Explanation:

The client operating system is not able to create a symbolic link
because the link points to a filename that is not given.

System action:

Processing continues.

User response:

Try the restore on a different operating system.

------------------------------------------------------------------------
ANS1806W

Size exceeded the maximum file size limit on your system for
'file_space_namepath_namefile_name' of 'file_size'.



Explanation:

You tried to restore or retrieve a file that has exceeded the maximum
file size limitation on your system.

System action:

The process cannot restore or retrieve the file.

User response:

Restore or retrieve this file on a system that supports the file size.
See your system administrator.

------------------------------------------------------------------------
ANS1807E

Unable to recall file from server due to error from recall daemon.



Explanation:

Unable to recall file. The recall daemon reported an error while trying
to recall a file. Look in the recall daemon's error log for more
information. This can happen if the server is down, the connection is
broken, or the file is missing on the server. It is also possible that
the migration server in the system option file has been changed to a
different server. The recall daemon does not check the system option
file for changes once it has started.

System action:

File skipped.

User response:

See if the server is up, and retry. If the problem still exists, look in
the error log. Also have the workstation administrator run dsmreconcile
against the file system and see if the file shows up in the
.SpaceMan/orphan.stubs file. If system option file has been changed,
stop all recall daemons and restart the master recall daemon to pick up
the changes.

------------------------------------------------------------------------
ANS1808E

The Logical Volume Snapshot Agent is not at the correct level. It is
possible that the Client was upgraded to a newer level but the LVSA
driver was not updated at the same time. Use the Setup Wizard to
configure either Online Image or Open File support and choose Update the
Logical Volume Snapshot Agent.



Explanation:

The selected operation requires the current level of the Logical Volume
Snapshot Agent. Use the Setup Wizard to update the LVSA.

System action:

The selected operation is not performed.

User response:

Retry the operation after updating the Logical Volume Snapshot Agent.

------------------------------------------------------------------------
ANS1809W

A session with the IBM Spectrum Protect server has been disconnected. An
attempt will be made to reestablish the connection.



Explanation:

This message is issued after the session with the IBM Spectrum Protect
server is unexpectedly lost. Some possible reasons that this message
might be issued: - There is a problem with the network. - The IBM
Spectrum Protect server was shut down. - The IBM Spectrum Protect server
administrator cancelled the client session.

System action:

The client will try to reestablish a connection with the server. If the
IBM Spectrum Protect server administrator cancelled the session, then
the attempt to reestablish the connection will fail and message ANS1369E
will be issued. If the attempt to reestablish the connection is
successful, then processing will continue. If the attempt to reestablish
the connection fails, then the client will continue to try to
reestablish a connection according to the COMMRESTARTDURATION and
COMMRESTARTINTERVAL client option settings.

User response:

If the session was cancelled by the IBM Spectrum Protect server
administrator and you do not know why, or if the client is unable to
reestablish a session with the IBM Spectrum Protect server, then contact
your IBM Spectrum Protect server administrator for further information.
Frequent occurrences of the ANS1809W message can indicate a problem with
the network. If this message is repeatedly found in the dsmerror.log,
investigate possible networking trouble, such as a failing network
interface card or router problem. One common problem is the media speed
of the network adaptors: If the network adaptors are set to
"auto-negotiate", try changing them to "100%% full duplex". If the
problem persists, then as a temporary measure ask your IBM Spectrum
Protect server administrator increase the COMMTIMEOUT and IDLETIMEOUT
option settings on the IBM Spectrum Protect server. This might reduce
the frequency of this message.

------------------------------------------------------------------------
ANS1810I

A session with the IBM Spectrum Protect server has been reestablished.



Explanation:

The session with the server has been reestablished after a connection
failure. This message is usually preceded by message ANS1809W.

System action:

Processing will continue.

User response:

None. This message is informational only.

------------------------------------------------------------------------
ANS1811S

IBM Spectrum Protect session could not be reestablished.



Explanation:

The session with the server has been lost. Attempts to reestablish the
session were unsuccessful. Possible causes include, but are not limited
to the following:

*  The server has been halted.

*  The network connection to the server is down.

*  The communication program that IBM Spectrum Protect is interacting
   with has encountered some problem.

System action:

Processing is stopped.

User response:

Check network connection to the server. Insure that the IBM Spectrum
Protect server is running. Insure that the communication program
underlying IBM Spectrum Protect is working properly.

------------------------------------------------------------------------
ANS1813E

Image Backup processing of 'filespace-name' finished with failures.



Explanation:

The image backup operation failed. This message is usually preceded by
other messages indicating the nature of the failure.

System action:

The failing file space is skipped and processing continues.

User response:

Examine the messages preceding this message and the IBM Spectrum Protect
Client error log for more specific indications about the problem. A
common cause is that a tape could not be mounted on the IBM Spectrum
Protect server, perhaps due to an insufficient number of mount points.
If there is a problem with the server, contact your System Administrator
for further assistance.

------------------------------------------------------------------------
ANS1814E

Unable to start the scheduled event 'event-name'



Explanation:

The scheduled event is no longer valid on the server. Either the window
has elapsed or the schedule has been deleted.

System action:

The client scheduler queries the server to obtain the next scheduled
event.

User response:

If the problem continues, contact your system administrator to correct
the problem on the server.

------------------------------------------------------------------------
ANS1815E

Either the window has elapsed or the schedule has been deleted



Explanation:

Scheduled event was no longer valid on the server.

System action:

The client scheduler queries the server to obtain the next scheduled
event.

User response:

If the problem continues, see your system administrator to correct the
problem on the server.

------------------------------------------------------------------------
ANS1816E

Invalid scheduling mode



Explanation:

The mode entered for the scheduled event was not correct.

System action:

Event does not occur.

User response:

Enter the correct scheduling mode and retry the operation.

------------------------------------------------------------------------
ANS1817E

Schedule function can only be run by a IBM Spectrum Protect authorized
user.



Explanation:

An attempt to use the schedule function failed because of improper
authority.

System action:

Processing stopped.

User response:

See the IBM Spectrum Protect authorized user for schedule function
information.

------------------------------------------------------------------------
ANS1818E

The SCHEDULE command is not allowed in LOOP (interactive) mode.



Explanation:

The SCHEDULE command may only be given on the inital command line. Enter
the HELP SCHED command for a complete description of the SCHEDULE
command.

System action:

The client does not execute any scheduled events.

User response:

Start the scheduler from the OS prompt. For example: dsmc schedule
Windows clients can also use the client scheduler service. Read the
client manual for information on how to use the SCHEDULE command and how
to use the IBM Spectrum Protect client scheduler features.

------------------------------------------------------------------------
ANS1819E

The IBM Spectrum Protect server was unable to register the address for
this node.



Explanation:

This is a rare situation, and is usually an indication of a problem with
the IBM Spectrum Protect server.

System action:

Processing stopped.

User response:

Check the error log for any other messages that might indicate a reason
for the failure. Ask your IBM Spectrum Protect server administrator to
check the IBM Spectrum Protect server activity log for any messages that
might indicate a problem on the server. Try to correct any indicated
problems, then try the operation again. If the problem persists, contact
IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1820E

Command line options must be preceded by a '-'



Explanation:

An option was specified without a '-' delimiter.

System action:

Processing stopped.

User response:

Enter the command again with a dash preceding each option.

------------------------------------------------------------------------
ANS1821E

Unable to start POSTSCHEDULECMD/ PRESCHEDULECMD 'command'



Explanation:

The requested action required a new process to be created. Either an
option or a schedule "action" that requested an operating system command
to be executed was entered.

System action:

Request is ignored.

User response:

Remove the request from the options file or the schedule defined on the
server.

------------------------------------------------------------------------
ANS1822E

Too many objects were selected for restore. Please select less than
max_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 the number of objects selected.

------------------------------------------------------------------------
ANS1823E

The TESTFLAGS or TRACEFLAGS option specifies unknown flag name 'keyword'
or the value supplied is invalid for the named keyword.



Explanation:

Either the testflag or traceflag name is incorrectly spelled, or the
value supplied for that flag is not valid.

System action:

If the TESTFLAGS or TRACEFLAGS option was specified in the client
options file or on the command line during client initialization, the
the client program does not start. If the option was specified from the
command line client while running in LOOP (interactive) mode, then the
operation does not run.

User response:

Correct the TESTFLAGS or TRACEFLAGS flag name or correct the value
specified for the TESTFLAG keyword shown in the message. These options
are typically used at the direction of IBM technical support or as
specified in the IBM Spectrum Protect Problem Determination Guide. If
you are not sure which flag names to use, review the IBM Spectrum
Protect Problem Determination Guide for additional information or
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1824E

Invalid trace file name (name too long).



Explanation:

A TRACEFILE option in the preferences files used a file name that is too
long.

System action:

Client program did not initialize.

User response:

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

------------------------------------------------------------------------
ANS1827W

Directories cannot be selected with the table of contents currently
loaded on the server.



Explanation:

The table of contents that is currently loaded on the server for this
volume does not contain objects corresponding to the one and only
point-in-time backup. It contains an incomplete point in time or
multiple points in time.

System action:

The directory is not selected for restore.

User response:

To be able to select an entire directory for restore, select "Use
Latest" or "Use Point in Time" from the Point in Time dialog.

------------------------------------------------------------------------
ANS1828E

Screen size is too small for using the PICK option.



Explanation:

You cannot use the PICK option on a workstation that has a screen
smaller than 20 characters across and 10 lines down.

System action:

IBM Spectrum Protect did not complete the operation.

User response:

Retry the operation using a workstation that has a screen with the
minimum size, or do not use the PICK option.

------------------------------------------------------------------------
ANS1831E

Password expired. The administrator for this system must run IBM
Spectrum Protect to update the password.



Explanation:

The password expired.

System action:

IBM Spectrum Protect ends.

User response:

The administrator for this system must update the password.

------------------------------------------------------------------------
ANS1832W

The option 'option' is no longer supported and will be ignored by IBM
Spectrum Protect client in this release.



Explanation:

The specified option is in the process of being made obsolete and will
be ignored by the client in this release. This option will be removed in
the next release and will no longer be valid.

System action:

Processing continues.

User response:

Remove the option from the option file. Also check the documentation to
see if this option has been replaced by a newer option.

------------------------------------------------------------------------
ANS1834S

Unable to write to 'file-name' for storing password



Explanation:

IBM Spectrum Protect cannot write to the specified file-name.

System action:

Processing continues.

User response:

Check access permissions and disk space. If unsuccessful, see your
system administrator.

------------------------------------------------------------------------
ANS1835E

PASSWORDACCESS is GENERATE, but password needed for server
'server-name'. Either the password is not stored locally, or it was
changed at the server.



Explanation:

Either the password is not stored locally, or it was changed at the
server.

System action:

IBM Spectrum Protect prompts you for the password if IBM Spectrum
Protect is running in the foreground.

User response:

If IBM Spectrum Protect was running as a background process, issue any
IBM Spectrum Protect command from the foreground. Enter the password in
answer to the prompt. Then try your background IBM Spectrum Protect
command again.

------------------------------------------------------------------------
ANS1836I

Unable to process Processor Value Unit hardware scan info file 'file
name', errno, cause.



Explanation:

The internal-use data file was not readable.

System action:

Processor Value Unit information is not sent to the IBM Spectrum Protect
server. Processing continues.

User response:

No response is necessary. This does not affect regular processing.
Correct any file access permission issues and try the command again. If
the file exists, delete the file and try the command again.

------------------------------------------------------------------------
ANS1837S

File space file_space_name is ignored. Processing continues.



Explanation:

The specified file space in the system options file is invalid.

System action:

The process attempts to continue the current operation.

User response:

Check the file space in the system options file and use a valid file
space. Retry the operation.

------------------------------------------------------------------------
ANS1838E

An error occurred while opening user-specified options file
'file_space_name'.



Explanation:

The specified options file could not be located or opened.

System action:

The process attempts to open the default options file.

User response:

Ensure that the specified options file exists and is valid.

------------------------------------------------------------------------
ANS1839E

Cannot read password.



Explanation:

An error occurred in setting up the input file (for example, the
terminal) to be read.

System action:

Processing stopped.

User response:

Check the attributes of the terminal.

------------------------------------------------------------------------
ANS1852E

Recall failed: offset 'offset' and read size 'size' are beyond the file
size of 'filesize'.



Explanation:

An attempt was made to read beyond the end of the file.

System action:

Processing stopped.

User response:

You must read within the file size. When determining offset and read
size values, all values are processed as bytes.

------------------------------------------------------------------------
ANS1853E

Server could not load the Table of Contents. Status: status



Explanation:

A failure occurred when the server attempted to load a file-level Table
of contents for an NDMP volume. No file-level queries can be performed
against the volume until the problem is solved.

System action:

The table of contents is not loaded.

User response:

Check the server Activity Log to determine the cause of failure. Retry
the operation after correcting the problem.

------------------------------------------------------------------------
ANS1862W

No table of contents information is available on the server for this
volume.



Explanation:

No objects for the selected volume exist on the server that were backed
up with table of contents information. Consequently no file-level
queries can be performed against the volume.

System action:

none

User response:

If file-level information is desired, use TOC option during backup.

------------------------------------------------------------------------
ANS1865E

Session rejected: Named Pipes connection failure.



Explanation:

An attempt to connect to the server using Named Pipes communications
failed. This might have occurred if an incorrect NAMEDPIPENAME was
specified in the options files or if your system administrator canceled
a backup operation.

System action:

Processing stopped.

User response:

Retry the operation, or wait until the server comes back up and retry
the operation. Ensure that the value specified on the NAMEDPIPENAME
option is the same as the one used by the server. If the problem
continues, contact your system administrator for further help.

------------------------------------------------------------------------
ANS1867E

The server generated a CRC for verb type CRC verb which does not match
the received verb verb received.



Explanation:

A cyclic redundancy check (CRC) failed between IBM Spectrum Protect
client and server communication.

System action:

The current object is skipped. Processing continues with the next
object.

User response:

This is an unusual condition, and could indicate a communications
problem between the IBM Spectrum Protect client and server. Try the
operation again. If the problem persists, contact IBM for further
assistance.

------------------------------------------------------------------------
ANS1871W

The server CRC version is server CRC version which does not match the
client version client CRC version.



Explanation:

This is a rare situation. The server and client are using different
versions of cyclic redundancy check (CRC) algorithms.

System action:

Processing continues without CRC checking.

User response:

Clients can be no more than one version downlevel from the IBM Spectrum
Protect server. Make sure the client and server are at compatible
levels. The command line client displays both client and server versions
when the client starts and connects to the server. The QUERY SESSION
command will also display the server version. From the GUI, use the
\"Help/About\" menu item to identify the client version, and the
\"File/Connection Information\" menu item to identify the server
version. If the client and server versions are incompatible, then the
IBM Spectrum Protect server administrator can turn off CRC checking for
your node.

------------------------------------------------------------------------
ANS1873E

An unknown error occurred while processing system object
'sys-obj-name':utility function 'func-name' failed with error error



Explanation:

An unknown error occurred while processing a system object. The error
information captured indicates the reason for the failure. This
information can be used to diagnose the problem.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS1877E

The parsed string is too long for IBM Spectrum Protect to process and
has been truncated to prevent a buffer overflow.



Explanation:

This is a rare condition. A very long string would have to be entered by
the user in a command line, dsm.opt file, or filelist. This string
exceeds the maximum input string size of 1024 bytes.

System action:

IBM Spectrum Protect truncated the string to the maximum possible length
of 1024, then continued with the operation. The operation may fail later
due to this truncation.

User response:

Check the client error log for other messages that might have been
logged after this message was written, and take any corrective action
suggested by those messages. If the problem persists, contact IBM
support for further assistance.

------------------------------------------------------------------------
ANS1878E

An unknown error occurred while processing system object
'sys-obj-name':Service 'service-name' and its dependent services could
not be stopped.



Explanation:

An unknown error occurred while processing a system object. The service
listed in the message and all of its dependent services could not be
stopped. Processing cannot complete until the service is stopped.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Manually stop the service and retry the operation.

------------------------------------------------------------------------
ANS1882E

Unable to stop service 'service-name'; error error



Explanation:

The service could not be stopped by the program.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Manually stop the service and retry the operation.

------------------------------------------------------------------------
ANS1891W

SUBDIR is not a valid option when using FILELIST, SUBDIR will be
ignored.



Explanation:

When Specifying FILELIST each entry is a single object and so SUBDIR
will not apply.

System action:

The option SUBDIR is ignored.

User response:

You may have either a -FILELIST or SUBDIR on this command, but not both.

------------------------------------------------------------------------
ANS1892W

Expire command is not allowed on the IBM Spectrum Protect journaled
filespace 'filespace'.



Explanation:

You cannot expire files from the server on a IBM Spectrum Protect
journaled filespace.

System action:

The expire command will not work on this filespec

User response:

If you want to expire this filepec remove it from the local filesystem.

------------------------------------------------------------------------
ANS1895I

Highest macro return code was return code value.



Explanation:

This message is issued after all commands in a client macro have
completed. The return code represents the highest return code that was
issued during processing of the macro. 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

System action:

None.

User response:

For return codes other than 0, the user may wish to verify the results
of the client operation(s) and take diagnostic and repair actions, as
necessary.

------------------------------------------------------------------------
ANS1898I

***** Processed count files *****



Explanation:

IBM Spectrum Protect has processed the specified number of files.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1899I

***** Examined count files *****



Explanation:

IBM Spectrum Protect has examined the specified number of files.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1900I

Return code is return code value.



Explanation:

The return code has been issued for the preceding client command. 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 return code indicates the highest severity message that was issued
during execution of the client command. For a scheduled event, the event
will be considered successful if the return code is 0, 4, or 8. The
event will be considered to have failed if the return code is 12.

System action:

None.

User response:

For return codes other than 0, the user may wish to verify the results
of the client operation and take diagnostic and repair actions, as
necessary.

------------------------------------------------------------------------
ANS1901I

Highest return code was return code value.



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

System action:

None.

User response:

For return codes other than 0, the user may wish to verify the results
of the client operation(s) and take diagnostic and repair actions, as
necessary.

------------------------------------------------------------------------
ANS1902E

The PRESCHEDULECMD command failed. The scheduled event will not be
executed.



Explanation:

The command specified by the PRESCHEDULECMD option must complete
successfully in order to execute the scheduled event. If the command
completed with a return code of 0 (zero), it is considered to have
completed successfully. If the command completed with any other return
code, it is considered to have failed. If the command failed then the
scheduled event is not executed.

System action:

The client does not execute the scheduled event, and the result code of
the scheduled event will be 12.

User response:

Identify and repair the problem that caused the command to fail. If it
is not necessary for the command to complete before starting the
scheduled event, then consider using the PRENSCHEDULECMD option, which
does not require that the command complete successfully. If a non-zero
return code is normal for this command, then consider wrapping the
command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS1903W

The POSTSCHEDULECMD command failed.



Explanation:

If the command specified by the POSTSCHEDULECMD option completed with a
non-zero return code, then the scheduled event is considered to have
completed successfully, but with a warning-level result. Note that the
result of the POSTSCHEDULECMD command will not supercede a higher result
from the scheduled client command. For example, if the scheduled client
command completed with a return code of 12, the scheduled event will be
considered to have completed with a return code of 12, regardless of the
outcome of the POSTSCHEDULECMD command.

System action:

At a minimum, the result code of the scheduled event is 8.

User response:

Identify and repair the problem that caused the command to fail. If it
is not necessary for the command to complete before posting the result
of the scheduled event, then consider using the POSTNSCHEDULECMD option.
If a non-zero return code is normal for this command, then consider
wrapping the command in a script that always exits with a return code of
zero.

------------------------------------------------------------------------
ANS1904E

The archive description may not contain any wildcard characters like '?'
or '*'.



Explanation:

Descriptions for archive files must not contain wildcard characters.

System action:

Processing stopped.

User response:

Enter an archive description that does not contain wildcard characters.

------------------------------------------------------------------------
ANS1906I

Destination must be specified for this operation when using FROMNODE.



Explanation:

You must specify a destination with a Restore/Retrieve command when
using FROMNODE processing.

System action:

Processing stops.

User response:

Retry the Restore/Retrieve command with 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/

------------------------------------------------------------------------
ANS1907E

An error occurred while trying to perform an object merge operation on
the server.



Explanation:

For NetWare clients: The IBM Spectrum Protect server is unable to
perform a NetWare long name conversion. For Unix or Windows image
backup: The group used to store associated image components could not be
closed.

System action:

The operation ends.

User response:

For NetWare: It is possible that a more current level of the IBM
Spectrum Protect server can perform the conversion. Contact your IBM
Spectrum Protect server administrator for assistance. For Unix or
Windows: This error indicates an authorization problem. Contact your IBM
Spectrum Protect server administrator for assistance. If the problem
still cannot be resolved, contact IBM technical support for further
assistance.

------------------------------------------------------------------------
ANS1908I

The scheduled command completed successfully.



Explanation:

The scheduled command completed with return code of zero, which is
interpreted as success.

System action:

The scheduled event is successful. The result code for the event is 0.

User response:

None.

------------------------------------------------------------------------
ANS1909E

The scheduled command failed.



Explanation:

The scheduled command completed with a non-zero return code, which is
interpreted as failure.

System action:

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

User response:

Identify and repair the problem that caused the command to fail. If a
non-zero return code is normal for this command, then consider wrapping
the command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS1912E

An invalid registry hive was specified.



Explanation:

The specified registry hive is invalid.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1913E

An invalid registry subkey was specified.



Explanation:

The specified registry subkey is invalid.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1914E

The specified subkey isn't valid for the specified hive.



Explanation:

The specified registry subkey is invalid for the specified registry
hive.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1915E

Too many arguments specified for the BACKUP REGISTRY command.



Explanation:

Too many arguments were specified for the BACKUP REGISTRY command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1916E

Too many arguments specified for the RESTORE REGISTRY command.



Explanation:

Too many arguments were specified for the RESTORE REGISTRY command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1917E

Too few arguments specified for the BACKUP REGISTRY command.



Explanation:

Too few arguments were specified for the BACKUP REGISTRY command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1918E

Too few arguments specified for the RESTORE REGISTRY command.



Explanation:

Too few arguments were specified for the RESTORE REGISTRY command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1919E

The specified eventlog is not valid.



Explanation:

The specified eventlog is not valid.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1920E

Too many arguments specified for the BACKUP EVENTLOG command.



Explanation:

Too many arguments were specified for the BACKUP EVENTLOG command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1921E

Too many arguments specified for the RESTORE EVENTLOG command.



Explanation:

Too many arguments were specified for the RESTORE EVENTLOG command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1922E

Too few arguments specified for the BACKUP EVENTLOG command.



Explanation:

Too few arguments were specified for the BACKUP EVENTLOG command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1923E

Too few arguments specified for the RESTORE EVENTLOG command.



Explanation:

Too few arguments were specified for the RESTORE EVENTLOG command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1924E

The specified system object is not valid.



Explanation:

The specified system object is not valid.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1925E

The specified system object type is not valid.



Explanation:

The specified system object type is not valid.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1926E

The specified system object type is only valid on Windows NT.



Explanation:

The specified system object type is only valid on Windows NT.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1928E

Server-initiated sessions are not available in the LAN-free mode.



Explanation:

Conflicting options SESSIONINIT=serveronly and ENABLELANFREE=yes were
specified. This combination is not allowed.

System action:

Processing stops.

User response:

Use client-initiated sessions or disable LAN-free.

------------------------------------------------------------------------
ANS1929E

An error occurred saving the registry key.



Explanation:

The active registry key cannot be copied to the ADSM.SYS staging
directory.

System action:

The registry backup operation stops.

User response:

Check the space available on the Windows boot partition to ensure there
is room to contain a copy of the Windows registry. This might require
several megabytes of free space. Also check the Windows permissions on
the ADSM.SYS staging directory and ensure that the Windows user which
you are using to run IBM Spectrum Protect has full access to that
directory and its contents.

------------------------------------------------------------------------
ANS1930W

IBM Spectrum Protect Express client view not supported with a IBM
Spectrum Protect Enterprise server. CLIENTVIEW option ignored.



Explanation:

The IBM Spectrum Protect Express client view is only supported when
going to a IBM Spectrum Protect Express server. When a IBM Spectrum
Protect Express client connects to a IBM Spectrum Protect Enterprise
server, the CLIENTVIEW option is ignored, and the IBM Spectrum Protect
Standard client view is displayed instead.

System action:

The CLIENTVIEW option is ignored and the IBM Spectrum Protect Enterprise
client view is displayed.

User response:

If you intend to use the IBM Spectrum Protect Enterprise server, then
update your CLIENTVIEW option to a value of STANDARD. Otherwise, update
your TCPSERVERADDRESS option to point to your IBM Spectrum Protect
Express server.

------------------------------------------------------------------------
ANS1931E

An error saving one or more eventlogs.



Explanation:

An error occurred saving one or more eventlogs.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1932E

An error occurred replacing one or more registry keys.



Explanation:

The registry key or keys being replaced are exclusively held by another
process. The registry keys were previously restored but the system was
not restarted.

System action:

processing stops.

User response:

This error occurs because the registry key or keys being replaced are
exclusively held by another process. This can happen if the registry
keys were previously restored but the system was not rebooted. Reboot
the system and attempt the restore operation again.

------------------------------------------------------------------------
ANS1933E

Error accessing file or device 'name'.



Explanation:

An error has occurred while accessing the file or device.

System action:

Backup set operation is not completed.

User response:

Verify that the file or device exists and is accessible.

------------------------------------------------------------------------
ANS1934E

Backup set 'name' not found.



Explanation:

The backup set name was not found on the server.

System action:

The backup set operation is not processed.

User response:

Verify that the backup set name is correct.

------------------------------------------------------------------------
ANS1935E

Too many arguments specified for the BACKUP NTDS command.



Explanation:

Too many arguments were specified for the BACKUP NTDS command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1936E

Not enough arguments specified for the BACKUP NTDS command.



Explanation:

Not enough arguments were specified for the BACKUP NTDS command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1937E

No NTDS server name specified for the BACKUP NTDS command.



Explanation:

No NTDS server name was specified for the BACKUP NTDS command.

System action:

Processing stopped.

User response:

Specify NTDS server name at the command and retry the operation.

------------------------------------------------------------------------
ANS1938E

NT Active Directory is not supported in this OS level.



Explanation:

NT Active Directory is not supported in this OS level.

System action:

Processing stopped.

User response:

Install Active Directory before performing backup operation.

------------------------------------------------------------------------
ANS1939E

File Replication Service backup failed.



Explanation:

IBM Spectrum Protect encountered an error while backing up files under
control of the Windows 2000 File Replication Service

System action:

Processing stopped.

User response:

Examine the Windows 2000 File Replication Service Event log to insure
the File Replication Service is operating properly. Restart the service
and retry the backup operation.

------------------------------------------------------------------------
ANS1940E

File Replication Service restore failed.



Explanation:

IBM Spectrum Protect encountered an error while restoring files under
control of the Windows 2000 File Replication Service

System action:

Processing stopped.

User response:

Examine the Windows 2000 File Replication Service Event log to insure
the File Replication Service is operating properly. Restart the service
and retry the restore operation.

------------------------------------------------------------------------
ANS1941E

System Volume backup failed.



Explanation:

IBM Spectrum Protect encountered an error while backing up files of the
Windows 2000 System Volume

System action:

Processing stopped.

User response:

Examine the Windows 2000 File Replication Service Event log to insure
the system volume was successfully initialized. Restart the service and
retry the backup operation

------------------------------------------------------------------------
ANS1942E

System Volume restore failed.



Explanation:

IBM Spectrum Protect encountered an error while restoring files under
control of the Windows 2000 File Replication Service

System action:

Processing stopped.

User response:

Examine the Windows 2000 File Replication Service Event log to insure
the system volume was successfully initialized. Restart the service and
retry the restore operation.

------------------------------------------------------------------------
ANS1943E

The operation is not supported: Downlevel server version.



Explanation:

The operation cannot be performed because server version is downlevel.

System action:

Processing stopped.

User response:

Use correct server version.

------------------------------------------------------------------------
ANS1944E

Error accessing file or device.



Explanation:

An error has occurred while accessing the file or device.

System action:

Backup set operation is not completed.

User response:

Verify that the file or device exists and is accessible.

------------------------------------------------------------------------
ANS1945E

The long namespace has been removed from the local file space. If you
wish to proceed with the backup/archive operation, rename your file
space on the server.



Explanation:

The process has detected that the server namespace is NTW:LONG, but the
local volume does not have long name support. If you would like to back
up the volume using the short names, rename the file space on the
server. If you would like to back up using long names, add the long
namespace support back to the volume in question.

System action:

Processing stopped.

User response:

Add the long namespace support to the volume or rename(remove) the
corresponding server file space.

------------------------------------------------------------------------
ANS1946W

File exists, skipping



Explanation:

The client tried to restore or retrieve the specified file, but the file
already existed in the target restore location and the user chose not to
replace the existing file.

System action:

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

User response:

The file was skipped because either REPLACE NO was in effect, causing
all existing files and directories to be skipped, or REPLACE PROMPT was
in effect, and when prompted, the user chose to skip this file or all
existing directories and files. No additional action is necessary if the
decision to skip the file was deliberate. Otherwise the operation can be
retried using either REPLACE ALL (automatically replace existing
directories and files) or REPLACE PROMPT (prompt the user whether to
replace the file).

------------------------------------------------------------------------
ANS1947W

The following directory exists and is skipped: file-space_name
directory_path directory_name



Explanation:

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:

No additional action is necessary.

To replace the files, try the operation again and set option
REPLACE=ALL. You can set REPLACE=PROMPT and when prompted, choose to
replace the directory.

------------------------------------------------------------------------
ANS1948E

The Microsoft volume shadow copy system components could not be queried.



Explanation:

IBM Spectrum Protect encountered an error while querying the system
writers under control of the Windows volume shadow copy service. The
error log and Windows event log might contain additional information
about this error.

System action:

Processing stops.

User response:

Try the operation again. If the error persists, review the error log and
Windows event log for information related to this error. You might need
to restart the volume shadow copy service, then try the operation again.
It might be necessary to reboot the machine to clear the volume shadow
copy error state.

------------------------------------------------------------------------
ANS1949E

Microsoft volume shadow copy snapshot initialization failed.



Explanation:

IBM Spectrum Protect encountered an error while initializing the
Microsoft Volume Shadow Copy Service for backup or restore. The error
log and Windows event log can contain additional information about this
error.

System action:

processing stops.

User response:

Try the operation again. If the error persists, review the error log and
Windows event log for information related to this error. Use the Windows
command 'vssadmin list writers' to determine the status of the Volume
Shadow Copy service. You can reboot the machine to clear the volume
shadow copy error state. If the system is a Domain Controller and the
Active Directory service is stopped, restarting the Active Directory
service will resolve the issue.

------------------------------------------------------------------------
ANS1950E

Backup using Microsoft volume shadow copy failed.



Explanation:

IBM Spectrum Protect encountered an error while performing a backup
operation using the Microsoft volume shadow copy service. The error log
and Windows event log might contain additional information about this
error.

System action:

processing stops.

User response:

Review the error log and Windows event log for information related to
this error. Restart any failing system service indicated in the Windows
event log. Restart the volume shadow copy Service. You can use the
Windows command 'vssadmin list writers' to determine the status of the
volume shadow copy service. It might be necessary to reboot the machine
to clear the Volume Shadow Copy error state.

------------------------------------------------------------------------
ANS1951E

Restore using Microsoft volume shadow copy failed.



Explanation:

IBM Spectrum Protect encountered an error while restoring with the
Microsoft Volume Shadow Copy Service.

System action:

processing stops.

User response:

Review the error log and Windows event log for information related to
this error. Restart any failing system service indicated in the Windows
event log. Restart the volume shadow copy Service. You can use the
Windows command 'vssadmin list writers' to determine the status of the
volume shadow copy service. It might be necessary to reboot the machine
to clear the Volume Shadow Copy error state.

------------------------------------------------------------------------
ANS1952E

Invalid symbolic link destination 'file-name' entered



Explanation:

You entered a restore/retrieve destination file-name specification that
is a symbolic link. To restore to symbolic link, make sure you set the
followsymbolic option to yes. Also, check where this symbolic link
points. You can restore/retrieve to a symbolic link that points to an
existing object.

System action:

Processing stopped.

User response:

Enter a correct file specification.

------------------------------------------------------------------------
ANS1954E

Backup processing of 'file-space name' finished with failures.



Explanation:

This message indicates that the file system backup has completed, but
encountered errors during backup processing.

System action:

Processing continues.

User response:

Examine the client error log for additional messages related to errors
in backing up the file system. Take any corrective action as suggested
by the messages.

------------------------------------------------------------------------
ANS1956E

Too few arguments specified for the BACKUP GROUP command.



Explanation:

Too few arguments were specified for the BACKUP GROUP command.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1957E

Showmembers and inactive are mutually exclusive parameters on a query.



Explanation:

Showmembers and inactive are mutually exclusive parameters on a query.

System action:

Processing terminates.

User response:

Specify one of the mutually exclusive parameters on the query

------------------------------------------------------------------------
ANS1958W

No base group found, attempting a full backup.



Explanation:

A differential backup requires a previous full backup to have been
performed.

System action:

Processing continues, and a full backup is attempted.

User response:

None. Perform a full backup before attempting a differential backup

------------------------------------------------------------------------
ANS1959I

Removing previous incomplete group 'name' Id:hi-lo



Explanation:

A previous group backup failed without cleaning up the temporary groups
correctly.

System action:

The previous incomplete groups are removed and processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1971E

The remote client agent (dsmagent) could not be started.



Explanation:

The remote client agent cannot be started. This error message is usually
preceded or followed by other messages.

System action:

Processing is stopped.

User response:

Check the error log for any other messages 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 operation again. If the
problem persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1972E

The connection to the remote client agent (dsmagent) failed. Either the
port number could not be read, or the port number is invalid.



Explanation:

An error occurred when trying to read the port number. A connection to
the remote client agent cannot be made.

System action:

Processing stopped.

User response:

Check the error log for any other messages 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 operation again. If the
problem persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS1973I

VSS writer for system object 'name' does not exist. Restore skipped.



Explanation:

Microsoft Volume Shadow Copy Service does not detect a writer for this
system component. Either the component is not installed or is not
running..

System action:

Object skipped.

User response:

Install or enable the affected system service and retry the operation.

------------------------------------------------------------------------
ANS1974W

Error removing previous incomplete group Id:hi-lo



Explanation:

A previous group backup failed without cleaning up the temporary groups
correctly, and the error still can not be cleaned up.

System action:

The previous incomplete groups remain and processing continues.

User response:

None.

------------------------------------------------------------------------
ANS1975W

IBM Spectrum Protect server error reason occurred closing and renaming
the group



Explanation:

An error was encountered closing and renaming the temporary group.

System action:

The backup is unsuccessful.

User response:

Ensure that the user has the proper authority to update the group and
try the operation again.

------------------------------------------------------------------------
ANS1976E

The specified system service is not valid.



Explanation:

The specified system service is not valid.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS1977E

Dsmcad schedule invocation was unsuccessful. This command will be tried
again in 10 minutes.



Explanation:

Dsmcad was unable to get the valid scheduler information from the dsmc
schedule process. This could be due to some problems during the
scheduler initialization, such as incorrect option usage.

System action:

Dsmcad will try to invoke the scheduler again in 10 minutes in order to
get the valid information.

User response:

Check the console and error logs to determine what kind of error
occurred during the dsmc process and correct the problem.

------------------------------------------------------------------------
ANS1978E

The IBM Spectrum Protect server is downlevel and does not support the
requested function. See error log for version information.



Explanation:

The function being used requires a more current IBM Spectrum Protect
Server.

System action:

The operation fails.

User response:

Upgrade your IBM Spectrum Protect Server to a level that supports this
function. See error log for version information.

------------------------------------------------------------------------
ANS1979E

The IBM Spectrum Protect Storage Agent is downlevel and does not support
the requested function. See error log for version information.



Explanation:

The function being used requires a more current IBM Spectrum Protect
Storage Agent.

System action:

The operation fails.

User response:

Upgrade your IBM Spectrum Protect Storage Agent to a level that supports
this function. See error log for version information.

------------------------------------------------------------------------
ANS1980E

The IBM Spectrum Protect Server and IBM Spectrum Protect Storage agent
are downlevel and do not support the requested function. See error log
for version information.



Explanation:

The function being used requires a more current IBM Spectrum Protect
Server and IBM Spectrum Protect Storage agent

System action:

The operation fails.

User response:

Upgrade your IBM Spectrum Protect Server and IBM Spectrum Protect
Storage agent to a level that supports this function. See error log for
version information.

------------------------------------------------------------------------
ANS1981E

Server :Version ver, Release rel, Level lev.subl Storage Agent:Version
SAver, Release SArel, Level SAlev.SAsubl



Explanation:

This message supplies extra detail to downlevel messages.

System action:

The operation fails.

User response:

This message supplies extra detail to downlevel messages.

------------------------------------------------------------------------
ANS1986E

Initialization functions cannot open the trace file specified.



Explanation:

The file could not be opened during initialization. The specified path
might be incorrect. It is also possible that the current user does not
have permission to write to the tracefile in the directory specified. It
is also possible that no space is available at the tracefile location.

System action:

Processing stops.

User response:

Make sure the tracefile option points to a valid path and that the user
has proper permissions to write to the specified file.

------------------------------------------------------------------------
ANS1987E

A destination file specification is not allowed with this command.



Explanation:

Of all the system object restore commands only RESTORE ASR allows the
entry of a destination file specification.

System action:

Processing stopped.

User response:

Re-issue the command without a destination file specification.

------------------------------------------------------------------------
ANS1989E

Initialization functions cannot open the error log file specified.



Explanation:

The error log file could not be opened during initialization. The
specified path may be incorrect. It is also possible that the current
user does not have permission to write to the logfile in the directory
specified. It is also possible that no space is available at the given
logfile location.

System action:

Processing terminates.

User response:

Make sure the logfile option points to a valid path and that the user
has proper permissions to write to the file specified.

------------------------------------------------------------------------
ANS1990W

The 'filesystem name' volume mount point can not be accessed. The IBM
Spectrum Protect return code is 'rc'.



Explanation:

The client is unable to access volume mount point. The common reasons
for this are that the account under which the client is running does not
have access to the volume mount point, or the volume is mounted onto a
cluster volume which is currently not available.

System action:

The inaccessible mount point is skipped and processing continues. with
the next mount point or volume.

User response:

Check the error log for additional messages that might yield additional
information about the problem that prevents access to the volume mount
point. Ensure that the IBM Spectrum Protect client is running under an
account which as access to the volume mount point. Ensure that the mount
point is not accessing a clustered volume. Please refer to Microsoft KB
Article 280297 for more information about how to configure volume mount
points on a clustered server.

------------------------------------------------------------------------
ANS1991E

An error occurred processing registry key 'key-name', data value
'value-name'. See the client error log for additional information about
this error.



Explanation:

An unexpected error occurred when the client tried to read or update the
Windows registry. Additional information regarding the error is usually
placed in the error log.

System action:

The operation might not execute correctly, depending on the error.

User response:

Check the client error log for any other messages that might have been
logged when this message was written, and take any corrective action
suggested by those messages. If the problem persists, contact IBM
support for further assistance.

------------------------------------------------------------------------
ANS1995W

Objects of different types cannot be deleted at the same time.



Explanation:

Deleting objects of different types is not allowed. For example,
deleting Backup Sets and regular file objects at the same time is not
possible.

System action:

No processing takes place.

User response:

Select objects of the same type to perform delete operation.

------------------------------------------------------------------------
ANS1996W

The volume mount points enumeration on 'filesystem name' volume failed.
Windows system error code: error; reason: 'error-reason'.



Explanation:

The client was unable to scan the specified volume for volume mount
points. The error information captured indicates the reason for the
failure. A common reason is that the account under which the client is
running does not have access to the volume.

System action:

The processing continues with the next volume.

User response:

Ensure that the client is running under an account which has access to
the volume and volume mount points. Correct the condition causing the
error and try the operation again. If the problem persists, contact your
system administrator or IBM Spectrum Protect administrator for further
help.

------------------------------------------------------------------------
ANS1997W

No files have been previously backed up for the VSS component
'component-name'.



Explanation:

You tried to restore the Microsoft Volume Shadow Copy (VSS) System State
component which does not contain file data. This is not necessarily a
problem.

System action:

Processing continues.

User response:

Check the error log for any other messages that occurred during backup.
The logs can indicate a reason for the failure.

------------------------------------------------------------------------
ANS1998W

Transaction byte limit 'name' is not supported by the server. Value
reset to limit



Explanation:

The TXNBYTELIMIT is larger than the server supports. The value will be
reset to a supported limit.

System action:

TXNBYTELIMIT is reset, and processing continues.

User response:

Set the option to a value supported by the server.

------------------------------------------------------------------------
ANS1999E

type of the operation processing of 'filespace-name' stopped.



Explanation:

The client has encountered a condition where it can not continue
processing the specified file space. The IBM Spectrum Protect client
error log or schedule log should contain additional messages related to
this error.

System action:

Processing stops.

User response:

Check the IBM Spectrum Protect client error log and schedule log for any
additional messages related to this error. Take any corrective action
that might be suggested by the related messages, then try the operation
again. If the problem persists, contact your IBM Spectrum Protect
administrator for further assistance.

------------------------------------------------------------------------
ANS2025W

Object 'object-name' has been removed from DB (Fix IT19964).



Explanation:

Fix of the APAR IT19964

System action:

None

User response:

Nothing

------------------------------------------------------------------------
ANS2026W

Bad sectors were detected on the volume 'volname'.



Explanation:

Bad sectors are skipped during image backup/restore operations.

System action:

Processing continues.

User response:

Make sure the volume data is not corrupt by using system tools like
chkdsk (Windows) or fsck (Unix).

------------------------------------------------------------------------
ANS2027E

GSKit function func-name failed with error-code: During the SSL/TLS
handshake, the client could not agree on a supported SSL/TLS protocol
version to use with server. session



Explanation:

A GSKit function has failed with the GSK_ERROR_BAD_MESSAGE.

System action:

Processing stopped

User response:

Make sure you have configured the key database for SSL communication as
described in the documentation. Possible issues could be during the
SSL/TLS handshake, the client could not agree on a supported SSL/TLS
protocol version to use with server If the problem persists, contact IBM
Spectrum Protect customer support.

------------------------------------------------------------------------
ANS2032I

The client VM restore is skipping the unsupported Independent disk :
vmdk



Explanation:

The VMware vStorage APIs do not support snapshoting Independent disks,
no backups were created.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2033W

'symboliclink name': is a symbolic link to a file or directory in a
different file system.



Explanation:

The dsmls file specs operand or the used file list contains a symbolic
link to a file or directory in another file system. Processing may lead
to incorrect status of the object the symbolic link refers to.

System action:

Status of objects are displayed.

User response:

To display the correct status of objects use dsmls with the full
qualifying path to the objects.

------------------------------------------------------------------------
ANS2036W

Pruning functions cannot open one of the IBM Spectrum Protect prune
files: log-name. errno = errno-value,



Explanation:

The file "log-name could not be opened during pruning. The system set
the error code errno-value. If the reason given is "access denied," the
current user does not have permission to write to the file in the
directory specified. It is also possible that no space is available at
the given file location or another IBM Spectrum Protect 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 the current user can write.

------------------------------------------------------------------------
ANS2037W

Schedule log pruning failed.



Explanation:

The schedule log pruning function completed with errors.

System action:

Processing continues.

User response:

Check error log for possible reasons of failure.

------------------------------------------------------------------------
ANS2038W

Invalid option 'option-name' received from the IBM Spectrum Protect
server client options set.



Explanation:

The client received an invalid option from the IBM Spectrum 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 Spectrum
   Protect client.

*  Missing brackets or directory delimiters.

*  Include and exclude patterns that are too complex.

System action:

The option is ignored by the IBM Spectrum Protect client.

User response:

Contact the IBM Spectrum Protect server administrator to determine if
the option can be removed from the client option set.

------------------------------------------------------------------------
ANS2039E

Invalid destination file specification 'file-name' entered



Explanation:

The destination file specification must end with directory delimiter
when performing a file list restore, or when the restore specification
is for more than one file, or when the option SUBDIR YES is in effect.

System action:

Processing stopped.

User response:

Specify a destination that ends with directory delimiter.

------------------------------------------------------------------------
ANS2040E

While attempting to communicate with the remote client, a version check
reveals that the versions do not match. The version is remoteversion but
the expected version is localversion.



Explanation:

During initialization between the local client and the remote client,
version checking reveals that the versions do not match. This is usually
the result of an upgrade of one client module without upgrading other
client modules that are part of product solution.

System action:

The calling procedure returns and control is passed back the user.

User response:

Check the versions of all IBM Spectrum Protect Client products that
communicate with each other and ensure that they are all at the same
version, release, and level.

------------------------------------------------------------------------
ANS2041E

Snapshot Differencing support is not available on the specified NetApp
filer.



Explanation:

Incremental by snapshot difference backup cannot be performed because
required support on the specified NetApp filer is not availble. .

System action:

Processing terminates.

User response:

None.

------------------------------------------------------------------------
ANS2042W

'symboliclink':is a symbolic link to a file or directory in another
filesytem. ACLs or extended attributes might not be backed up.



Explanation:

The backup or archive operand contains a symbolic link to a file or
directory in another file system. Processing may lead to loss of ACLs or
other extended attributes because they might not be processed.

System action:

The file data is backed up. Processing continues with the next object.

User response:

If you need to ensure that ACLs and other extended attributes are backed
up successfully, do not use symbolic links to back up files on other
file systems of different file system types. Instead use IBM Spectrum
Protect to process the other file system directly.

------------------------------------------------------------------------
ANS2043I

The virtual machine template 'name' has already been backed up.



Explanation:

Virtual machine templates are skipped if no change has occurred since
the last backup.

System action:

Processing skips this virtual machine template.

User response:

To back up this virtual machine template, run an incremental forever
full backup operation.

------------------------------------------------------------------------
ANS2044E

The template virtual machine 'name' cannot be restored when the IBM
Spectrum Protect data mover node on the vStorage Backup Server is
connected directly to an ESX/ESXi host.



Explanation:

The VMware vStorage API do not support template virtaul machine
operations when connected directly to an ESX/ESXi host.

System action:

Processing stops for this template virtual machine

User response:

Virtual machine template operations are supported when the IBM Spectrum
Protect data mover node connects directly to a ESX/ESXi host. Modify the
VMCHOST to connect the IBM Spectrum Protect data mover to a vCenter
Server.

------------------------------------------------------------------------
ANS2045E

The VMENABLETEMPLATEBACKUPS option is not specified. The virtual machine
template 'name' can not be backed up.



Explanation:

The VMENABLETEMPLATEBACKUPS template option must specify YES in order
for a virtual machine template to be included in a backup operation. The
default value is NO.

System action:

Processing stops for this template virtual machine

User response:

Use the option -vmenabletemplatebackups=yes and run the operation again.

------------------------------------------------------------------------
ANS2046S

Error 'errtxt' (errno=errno) occurred trying to write to audit log
'file-name'. The audit log function is disabled.



Explanation:

There was an error encountered writing to the audit log (for example,
there is not enough space on the disk).

System action:

Audit logging is disabled for the rest of the operation. The return code
for the operation is set to 12 to indicate that the contents of the
audit log are incomplete.

User response:

If this is an out of space condition either free up space on the volume
or try to write the audit log to a volume with more space.

------------------------------------------------------------------------
ANS2047E

An unexpected error was encountered processing a system state/services
request. IBM Spectrum Protect function name : function-name IBM Spectrum
Protect function : function-desc IBM Spectrum Protect return code :
TSM-rc IBM Spectrum Protect explanation : TSM-msg IBM Spectrum Protect
file : file-name (line-number)



Explanation:

None.

System action:

Processing the system state stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS2048W

Named stream of object 'object-name path-name file-name' is corrupt.



Explanation:

One or more of the file's named streams are corrupt.

System action:

The named stream is not restored/retrieved.

User response:

The backup copy of the named stream is damaged. The file is restored to
as great an extent as possible, but the file should be examined to
verify that it is usable.

------------------------------------------------------------------------
ANS2049W

Named stream of object 'object-name' may be corrupt.



Explanation:

One or more of the file's named streams may be corrupt.

System action:

The named stream is restored/retrieved to as great an extent as
possible.

User response:

The backup copy of the named stream may be damaged. The file is restored
to as great an extent as possible, but the file should be examined to
verify that it is usable.

------------------------------------------------------------------------
ANS2050E

IBM Spectrum Protect needs to prompt for the password but cannot prompt
because the process is running in the background.



Explanation:

If PASSWORDACCESS=PROMPT or if the password that is stored locally is
incorrect, IBM Spectrum Protect attempts to prompt the user for the
password. The attempt to prompt the user fails because the process is
running in the background. When a process is running in the background,
prompting is not allowed.

System action:

Processing stopped.

User response:

If RUNASSERVICE=YES, do not set PASSWORDACCESS=PROMPT. Use
PASSWORDACCESS=GENERATE.

------------------------------------------------------------------------
ANS2051W

The local snapshot repository was not found on location.



Explanation:

The specified directory for the local snapshot location does not exist.

System action:

Processing continues.

User response:

A new local snapshot repository will be build in the specified
directory.

------------------------------------------------------------------------
ANS2052E

Information about the disk subsystem is missing.



Explanation:

The local snapshot repository could not be initialized due to missing
information about the disk subsystem.

System action:

Processing stops.

User response:

The application ensures that the disk subsystem is initialized properly.
Check for preceding error messages.

------------------------------------------------------------------------
ANS2053E

A memory allocation error has occurred in file filename, line number
linenumber.



Explanation:

Enough memory was not available to continue processing.

System action:

Processing ends.

User response:

Ensure that your system has sufficient real and virtual memory. Close
unnecessary applications.

------------------------------------------------------------------------
ANS2054E

Operating system error errno: messagetext.



Explanation:

The application encountered an unexpected message error during the
execution of a system function. The respective operating system error
and message text will be displayed.

System action:

Processing stops.

User response:

Check the specific error message.

------------------------------------------------------------------------
ANS2055I

The local snapshot manager could not be locked.



Explanation:

The local repository is locked by another application. This process will
proceed when the other application unlock the local repository.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2056I

Waiting maximal timeout seconds until the lock is released by the other
application.



Explanation:

While the local repository is locked by another application, the program
will wait a specific period of time to proceed. For example, in the
mySAP environment, the wait period is 1 hour.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2057E

Local snapshot manager not initialized.



Explanation:

The local snapshot repository was used without previous initialization.

System action:

Processing ends.

User response:

The system normally ensures that the local repository is initialized.
Check for preceding error messages.

------------------------------------------------------------------------
ANS2058E

The data container with ID dcID could not be updated in the local
repository.



Explanation:

During a FlashCopy backup the target set record in the local repository
is updated with the correspondent properties. A failure occurred during
that process.

System action:

Processing ends.

User response:

Check for preceding error messages like memory allocation error or other
system error.

------------------------------------------------------------------------
ANS2059E

Cannot find a target data container that match with the source data
container.



Explanation:

During a snapshot type backup or hardware function, the process tries to
find a target data container that match to the source data container to
satisfy the operation. A matching target data container could not be
found.

System action:

Processing ends.

User response:

See the rules for select one of multiple target data containers. For
example, this message will be displayed if the user is trying to start a
FlashCopy backup of type 'INCR' and all the target sets are being used
for the FlashCopy type 'COPY'. Make sure also that the target volumes
are available to the backup system and the syntax is correct for the
following setup file parameters: 1. shark_target_volume 2.
shark_copy_service_code 3. java_home_directory 4.
primary_copyservices_servername 5. shark_username 6. shark_password

------------------------------------------------------------------------
ANS2060W

Cannot find a volume in the target data container dcID to match with the
source srcvol.



Explanation:

This warning message indicates that for the specific source not any
target volume could be found in this target data container that matches
for a FlashCopy operation. If multiple target data containers are being
used, the processing will continue checking the volumes of the next
target data container.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2061W

The target data container with ID dcid was not found in the local
repository.



Explanation:

An inquire of the data container with the specified ID could not be
satisfied because that target set does not exists in the local
repository.

System action:

Processing may continue.

User response:

The application that is requesting the inquire will decide whether or
not the error should end the program. Check for following messages.

------------------------------------------------------------------------
ANS2062W

Could not find a target data container in the state state to fulfill the
requested criteria.



Explanation:

A data container in the specified state was not found in the local
repository to satisfy specific criteria requested by the application.

System action:

Processing may continue.

User response:

Which criteria have been passed is application specific. Check for
following messages. The application will decide whether or not that
warning should end the program.

------------------------------------------------------------------------
ANS2063W

The local snapshot repository already exists on the directory location.



Explanation:

An application tried to create the local repository in a directory that
already exists.

System action:

Processing may continue.

User response:

The application will decide whether or not that warning should end the
program. Check for following messages.

------------------------------------------------------------------------
ANS2064I

The local snapshot repository will be created on the directory location.



Explanation:

The local snapshot repository containing information about the state of
the data containers is being created.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2065I

The local snapshot repository could not be created on the directory
location.



Explanation:

A failure occurred creating the local snapshot repository.

System action:

Processing ends.

User response:

Look for a operating system error message.

------------------------------------------------------------------------
ANS2066E

Cannot read the .fct file filename.



Explanation:

The .fct file containing the target data containers was not found or is
not accessible.

System action:

Processing ends.

User response:

Check the name, the path and the right of the file.

------------------------------------------------------------------------
ANS2067E

The exception CLsmException was thrown. Reason: txt.



Explanation:

An unexpected error occurred processing a function of the local snapshot
repository.

System action:

Processing ends.

User response:

Check the specific reason.

------------------------------------------------------------------------
ANS2068E

No target LUNs were found for the data container dcID in the .fct file
filename.



Explanation:

The program will search in the .fct file for each specific data
container a list of entries with the label <PREFIX>TARGET_VOLUME where
the prefix depends on the hardware type. Either you have a wrong label
for the target volumes of the specified data container or this data
container in the .fct file does not have any target LUNs.

System action:

Processing ends.

User response:

This error can only occurred if the application does not have a GUI
where the user provides the input of the target data containers and the
format will automatically be checked. If so, please check the format of
the .fct file.

------------------------------------------------------------------------
ANS2069E

Cannot read the file filename of the local snapshot repository.



Explanation:

The system keeps some information about the state of the data containers
locally in a file. This file was not found or is not accessible.

System action:

Processing ends.

User response:

Check the name, the path and the right of the file.

------------------------------------------------------------------------
ANS2070E

The repository state file filename is empty or has a wrong format.



Explanation:

The system keeps some information about the state of the data containers
locally in a file. This file was found but the expected format of the
data in not correct.

System action:

Processing ends.

User response:

Normally the system ensures that the format of this file is correct.
Check for preceding error.

------------------------------------------------------------------------
ANS2071E

The data container dcID could not be inserted in the local snapshot
repository.



Explanation:

The system keeps some information about the state of the data containers
locally in a file. Inserting an entry for a new data container occurred
an error.

System action:

Processing ends.

User response:

This is an unexpected error. Check for preceding error. If not any other
error can be seen, collect the logs and traces and contact the support.

------------------------------------------------------------------------
ANS2072E

An unexpected error was encountered processing a IBM Spectrum Protect
operation using a hardware or snapshot function. IBM Spectrum Protect
function name : function-name IBM Spectrum Protect function :
function-desc IBM Spectrum Protect return code : TSM-rc IBM Spectrum
Protect file : file-name (line-number)



Explanation:

None.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS2073E

The file filename of the local snapshot repository could not be opened
for writing.



Explanation:

The system keeps some information about the state of the data containers
in the local snapshot repository. Opening a file of this repository
occurred an error.

System action:

Processing ends.

User response:

Check the rights permission of that file.

------------------------------------------------------------------------
ANS2074E

Cannot open user input FlashCopy target file 'fct_file'.



Explanation:

The FlashCopy target file that the user provided cannot be read.

System action:

The operation fails.

User response:

Run the client configuration utility and provide a valid FlashCopy
target user input file.

------------------------------------------------------------------------
ANS2075E

There is no VTOC data available for the volume. The volume cannot be
backed up.



Explanation:

The volume disk label type is not VTOC. It is possible that your disk is
formatted with an EFI label. The IBM Spectrum Protect client on Solaris
currently supports only VTOC disk labels.

System action:

The volume is not backed up.

User response:

Do not attempt to backup volumes formatted with a non-VTOC disk label.

------------------------------------------------------------------------
ANS2076E

program-name: Space Managment can not be added for file system
'filesystem' The length of the file system name exceeds the maximum
length of 'maxlength' which can be stored in a DMAPI attribute.



Explanation:

The DMAPI has a limitation in the size of data that can be stored in a
DMAPI attribute. If the lenght of the file system name exceeds this
limit the IBM Spectrum Protect client can not add space management to
the file system.

System action:

Space management cannot be added to file system.

User response:

Please make sure that the length of the file system name does not exceed
the DMAPI limit.

------------------------------------------------------------------------
ANS2077E

program-name: Reconcile for file system 'filesystem' can not be started
for the selected mode in a non-scout environment. Please use Two Way
Orphan Check Reconcile instead.



Explanation:

The IBM Spectrum Protect client reconciliation program can not be
started in orphan check or stub restore mode when the HSM system is
configured to run without the scout daemon.

System action:

Reconcile can not run in a non scout environment.

User response:

If you have configured a non scout environment you need to use the Two
Way Orphan Check Reconcile.

------------------------------------------------------------------------
ANS2078E

System state backup is not allowed CLUSTERNODE is set to YES.



Explanation:

When the CLUSTERNODE option is set to YES, the backup systemstate
command is not valid.

System action:

System state backup is stopped.

User response:

If the CLUSTERNODE option is incorrectly set to YES, then change the
option to NO and try the operation again. Otherwise see the
backup-archive client manual for further information about configuring
the client to run in a cluster environment.

------------------------------------------------------------------------
ANS2079E

Error processing 'filespace namepath-namefile-name': error scanning
snapshot



Explanation:

This message is issued when the IBM Spectrum Protect client is unable to
read data from a snapshot used for the backup. If you are performing the
Microsoft Volume Shadowcopy Service (VSS) snapshot backup one possible
cause is that the operating system deleted a VSS snapshot because the
shadow copy storage could not grow. If you are performing the snapshot
difference incremental backup on normal NetApp/N-Series volumes one
possible cause is that the base snapshot was accidentally removed from
the NetApp file server.

System action:

Backup processing for the file system stops.

User response:

If you were performing VSS snapshot-based backup, examine the client
error log and the Microsoft Windows system event log for any other
messages that might help identify the problem. If there are no obvious
reasons for the failure, try the operation again,the problem might be
caused by temporary I/O conflicts between VSS and other system disk I/O
activities. If you were performing snapshot difference incremental
backup, contact your IBM Spectrum Protect administrator to verify that
base snapshot was not accidentally deleted.

------------------------------------------------------------------------
ANS2080W

The value 'option' for the option 'option' is no longer supported and
will be ignored by IBM Spectrum Protect client in this release.



Explanation:

The specified option value is in the process of being made obsolete and
will be ignored by the client in this release. This option value will be
removed in the next release and will no longer be valid.

System action:

Processing continues.

User response:

Update the option value or remove the option from the option file. Also
check the documentation to see if this option has been replaced by a
newer option.

------------------------------------------------------------------------
ANS2083W

No vApps that match the input specification were found.



Explanation:

A vApp that matches the specified input or the VAPP value in the
DOMAIN.VCD option was not found.

System action:

The operation is stopped

User response:

Make sure the the VAPP value in the DOMAIN.VCD option is correct.

------------------------------------------------------------------------
ANS2084I

Creating a new vApp



Explanation:

The estore is attempting to create the destination vApp.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS2085E

The virtual machine is configured as a fault tolerant virtual machine.
As a result, it cannot be backed up.



Explanation:

vSphere does not allow for the snapshot or backup of fault tolerant
virtual machines with vStorage API for Data Protection.

System action:

The virtual machine is not backed up.

User response:

To back up a fault tolerant virtual machine with vStorage API for Data
Protection, first disable fault tolerant. Then, after the backup
completes, enable fault tolerant.

------------------------------------------------------------------------
ANS2088E

Session rejected: The client does not use unicode.



Explanation:

The server cannot accept the client session because the client does not
use unicode and the node already contains a unicode filespace. The
server records whether or not the client's data is unicode, and does not
let the node change this attribute.

System action:

Processing stops.

User response:

Logon to the server from a client with a platform that uses unicode
data. For example, the original platform that was used to create the
existing filespaces for this node. Alternatively, if the client node
needs to change to the platform that is currently being attempted,
contact the server administrator to remove the existing filespaces that
contain unicode data and try the node connection again.

------------------------------------------------------------------------
ANS2089E

The string string_text can not be converted to Unicode.



Explanation:

An object contains a multibyte sequence that is invalid for the current
locale.

System action:

The operation stops.

User response:

Verify that the locale is appropriate for the objects that are
processed.

------------------------------------------------------------------------
ANS2090I

The virtual machine folder could not be found in this path: 'name'.



Explanation:

The destination target does not have the original inventory path that
was saved with the virtual machine. As a result, the virtual machine is
restored to the top level of the ESX/ESXi inventory.

System action:

Processing continues

User response:

None

------------------------------------------------------------------------
ANS2091I

The virtual machine resource could not be found in this path: 'name'.



Explanation:

The destination target does not have the original resource path that was
saved with the virtual machine. As a result, the virtual machine is
restored to the top level of the ESX/ESXi inventory.

System action:

Processing continues

User response:

None

------------------------------------------------------------------------
ANS2092I

The restore process will override the original inventory path that was
saved with this virtual machine.



Explanation:

Specifying the -datacenter or -host option will override the original
inventory path that was saved with the virtual machine. As a result, the
virtual machine is restored to the top level of the ESX/ESXi inventory.

System action:

Processing continues

User response:

None

------------------------------------------------------------------------
ANS2093E

The remote file system agent is downlevel and does not support this
operation. NODENAME : node MULTI-NODE NAME : multi-node hostname : host
TCP/IP address : tcpaddr:tcpport version : version.release.level..mod



Explanation:

None.

System action:

The operation fails.

User response:

Upgrade the remote file system agent to a supported level.

------------------------------------------------------------------------
ANS2097E

Unable to establish a session with the IBM Spectrum Protect server as
target node 'target' using agent node 'agent'.



Explanation:

None.

System action:

Processing ends.

User response:

Ensure that the multi-node name exists on the server and that the agent
node has the proper authority to target node listed.

------------------------------------------------------------------------
ANS2100E

Backup of virtual machine 'virtual-machine-name' cannot continue because
an invalid disk area was encountered during backup.



Explanation:

During a backup of the virtual machine, one or more virtual hard disks
indicated an invalid disk area for backup such as a length of zero, a
length greater than the size of the disk, invalid starting position, or
negative values.

System action:

The backup was stopped.

User response:

Check that the virtual machine's storage is configured properly, working
correctly, and all storage hardware is properly connected to the virtual
machine. Try the command again. If the problem persists contact IBM
Spectrum Protect customer support.

------------------------------------------------------------------------
ANS2101E

Compressed data grew.



Explanation:

The size of data is growing after compression

System action:

Processing continues.

User response:

The application must abort the transaction.

Please turn off compression and try to resend the object.

------------------------------------------------------------------------
ANS2102E

File list processing not started



Explanation:

An error occured before the file list processing was started.

System action:

Processing stops.

User response:

Examine the client error log for additional messages that might indicate
the reason for the problem. Try to follow the suggested corrective
actions (if any) and try the operation again.

------------------------------------------------------------------------
ANS2104E

An error occured after processing the file list.



Explanation:

An error occured after the file list processing completed.

System action:

Processing stops.

User response:

Examine the client error log for additional messages that might indicate
the reason for the problem. Try to follow the suggested corrective
actions (if any) and try the operation again.

------------------------------------------------------------------------
ANS2105I

File list entry not Processed: File List Entry



Explanation:

A file list operation encounted an error. This entry from the file list
was not processed.

System action:

This message is for auditing purposes only.

User response:

This message is for auditing purposes only.

------------------------------------------------------------------------
ANS2106I

Connection to primary IBM Spectrum Protect server primary server; failed



Explanation:

A communication error occured while attempting to connect to the primary
server. The node is configured for replication and will attempt to
connect to the failover server.

System action:

Processing continues.

User response:

Contact the IBM Spectrum Protect server administrator to verify if the
primary server is available. If the primary server is available, check
the error log for communications failures and correct any configuration
issues. If the IBM Spectrum Protect server is not available, allow the
node to fail over to the failover server as configured by the primary
IBM Spectrum Protect server administrator.

------------------------------------------------------------------------
ANS2107I

Attempting to connect to failover server failover server; at failover
server; : TCP/IP Port;



Explanation:

The node is configured for replication and will attempt to connect to
the failover server. The failover server address and port are configured
by the primary IBM Spectrum Protect server administrator and are saved
in the options file.

System action:

Processing continues.

User response:

Contact the IBM Spectrum Protect server administrator to verify if the
primary server is available. If the primary server is available, check
the IBM Spectrum Protect error log for communications failures and
correct any configuration issues. If the IBM Spectrum Protect server is
not available, allow the node to fail over to the failover server as
configured by the primary IBM Spectrum Protect server administrator.

------------------------------------------------------------------------
ANS2108I

Connected to failover server failover server;.



Explanation:

The node is configured for replication and has successfully connected to
the failover server.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2110I

Connection to failover server IBM Spectrum Protect failover server;
failed



Explanation:

A communications error occured while attempting to connect to the
failover server. The node is configured for replication and an attempt
to connect to the failover server was made but failed.

System action:

Processing continues.

User response:

Contact the IBM Spectrum Protect server administrator to verify if the
failover server is available. If the failover server is available, check
the error log for communications failures and correct any configuration
issues.

------------------------------------------------------------------------
ANS2111E

The REPLSERVERNAME entry for the specified MYREPLICATIONSERVER option
was not found.



Explanation:

The MYREPLICATIONSERVER option must have a matching REPLSERVERNAME entry
in the options file. The REPLSERVERGUID, REPLTCPPORT, and
REPLTCPSERVERADDRESS must also be specified. These options are normally
set by the IBM Spectrum Protect server administrator and saved to the
options file during logon to the primary server.

System action:

Processing stops.

User response:

Manually edit the options file to either correct or remove the options.

------------------------------------------------------------------------
ANS2112I

failover server is configured as 'read-only'. Backup and Archive
operations are not supported when the failover server is in 'read-only'
mode



Explanation:

The IBM Spectrum Protect client has established a session with a server
that is configured as 'read-only'. The IBM Spectrum Protect server is
configured as a replication server and will not accept data from this
node.

System action:

Processing continues.

User response:

The IBM Spectrum Protect may be used for Restore, Retrieve and Query
operations. Backup and Archive commands will fail. The IBM Spectrum
Protect server administrator can enable Backup and Archive operations
for the node with the 'Update Node' command.

------------------------------------------------------------------------
ANS2113E

The command is not enabled when connected to the failover server in
failover mode.



Explanation:

The IBM Spectrum Protect client has failed over and established a
session with a failover server. The IBM Spectrum Protect server is
configured as a replication server and will not accept data from this
node. Commands that store data on the server are disabled.

System action:

Processing continues.

User response:

You can use the IBM Spectrum Protect client for Restore, Retrieve, and
Query operations. Backup and Archive operations will fail.

------------------------------------------------------------------------
ANS2114W

IBM Spectrum Protect application protection did not copy the VSS
Manifest files from VM 'VM'.



Explanation:

The VSS Manifest files are not found on the guest machine.

System action:

The VSS Manifest files cannot be copied. Verify that the VSS and SQL
Writer services are running on the guest VM

User response:

None

------------------------------------------------------------------------
ANS2115I

Replication server connection information saved: connection information;



Explanation:

This node is configured for replication. The replication server
connection information has been saved to the options file. The
replication server options are set by the IBM Spectrum Protect
Administator, sent to the client during logon, and are saved to the
options file.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2116W

IBM Spectrum Protect application protection did not back up the VSS
Manifest files from VM 'VM'.



Explanation:

A failure occurred while backing up the files that are necessary for
application protection.

System action:

The back up of this VM failed.

User response:

Check the dsmerror.log for additional information. Then try the
operation again.

------------------------------------------------------------------------
ANS2117E

Source volume is of subtype dev-type and destination is of subtype
dev-type. Destination must be larger than source.



Explanation:

Logical volumes from scalable volume groups (subtype DS_LVZ) do not
contain an LVCB. That is, the very first block contains user data. AIX
LVM volumes from original volume groups (subtype LVM) contain a Logical
Volume Control Block (LVCB) on the first block (512 bytes) of the
volume. When restoring to a volume of subtype LVM, the first block must
be skipped in order to preserve the existing LVCB of the destination
volume. That is, the restore operation begins writing at the second
block of the volume. This means that given two volumes of identical
size, one of subtype DS_LVZ and the other is of subtype LVM, the latter
has one less 512-byte block in which to store user data. Thus when you
restore a volume of subtype DS_LVZ to a volume of subtype LVM, it is not
sufficient for the destination volume to be the same size as the source
volume. Instead, the destination volume must be at least one 512-block
larger than the source volume.

System action:

The restore operation is not performed.

User response:

Make sure that both source and destination logical volumes are of the
same type, or choose a larger destination volume, or increase the size
of the destination volume.

------------------------------------------------------------------------
ANS2118I

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



Explanation:

A write failure is often a result of insufficient access permissions to
the options file, but could also be caused by the lack of available disk
space. The replication server connection information can not be saved
and failover will not be possible.

System action:

The operation failed.

User response:

Check the local disk for possible causes of the write error, and check
to see that sufficient access to the options file is configured.

------------------------------------------------------------------------
ANS2119I

An invalid replication server address return code rc value = rc-value
was received from the server.



Explanation:

An invalid replication server address return code indicates that the
server was not able to aquire connection information.

System action:

Possible server problem.

User response:

Check the server log for more information.

------------------------------------------------------------------------
ANS2120W

The last store operation date reported by the server replication server;
of server commit date; UTC does not match the last store operation date
of client commit date; UTC stored by the client for the filespace
filespace;.



Explanation:

The last store operation date reported on the server does not match the
date stored locally on the client. If connected to the replication
server it is likely that the replication was done before the last store
operation from the client to the primary server. Hence, the replication
is out of date. If connected to the primary server it is likely that the
previous backup was done from another machine.

System action:

Processing continues.

User response:

Contact the IBM Spectrum Protect server administrator. Restoring from an
out of date replica may lead to loss of data. If the primary server
cannot be recovered, a full backup to the replica may be appropriate. If
connected to the primary server, the message can be ignored.

------------------------------------------------------------------------
ANS2122E

The name of virtual machine 'VM-name' ends with a period. The
backup/restore of such machines is not supported.



Explanation:

The specified virtual machine ends with a period character that are not
supported for virtual machine backup and restore operations.

System action:

The backup for the specified virtual machine fails.

User response:

Rename the virtual machine so that it does not ends with period.

------------------------------------------------------------------------
ANS2123W

Issue the dsmc SET PASSWORD -type=VCD 'vCloud Director hostname'
'userid' 'password' command to save an encrypted password.



Explanation:

The VCDPW option was found either in an options file or as a command-
line entry. Although both methods of entry are allowed, they present a
security risk because the password is in plain text and is not
encrypted.

System action:

The option is accepted and the VCD password is used in the current
session.

User response:

To save an encrypted password, issue the following command: dsmc SET
PASSWORD -type=VCD 'VirtualCenter hostname' 'userid' 'password'

------------------------------------------------------------------------
ANS2124W

Client node replication table is locked by another process.



Explanation:

Another process is using the client node replication table. Only one
process may use it at a time.

System action:

This process does not use the client node replication table.

User response:

You can serialize processes using the client node replication table. Or
you can reconfigure the current process to use a different table path to
avoid contention.

------------------------------------------------------------------------
ANS2126E

The Organization VDC node that contains snapshots of Organization VDC
'org vdc name' of organization 'org name' was not found.



Explanation:

The Organization VDC node contains the backup data to be restored. The
specified organization and organization VDC are not mapped to this
Organization VDC node. As a result, the restore operation cannot
proceed.

System action:

The operation stops.

User response:

Verify that the specified organization, organization VDC, and vApp are
correct.

------------------------------------------------------------------------
ANS2127E

The snapshot data that is required to restore 'vapp name' cannot be
retrieved from the IBM Spectrum Protect Server.



Explanation:

The required snapshot data was unable to be retrieved from the IBM
Spectrum Protect Server.

System action:

The operation stopped.

User response:

Check the dsmerror.log file for information about why the data was not
retrieved. Then, try the operation again. If the problem persists, visit
the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2128E

Failed in creating a restored version of vApp 'vapp name'.



Explanation:

The operation to create a restored vApp on the vCloud failed. The data
associated with the vApp snapshot might not be complete.

System action:

The operation stops.

User response:

Check the dsmerror.log file for information about why the operation
failed. Then, try the operation again. If the problem persists, visit
the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2129E

A VM you tried to rename 'rename' did not appear in the list of VMs to
restore 'list'.



Explanation:

The VMNAME option for parallel restores requires pairing the name and
rename fields together. You cannot rename a VM which you are not
attempting to restore.

System action:

The operation will not begin.

User response:

Verify the syntax of the command and spelling of the VMs you are trying
to restore.

------------------------------------------------------------------------
ANS2135E

The node on the IBM Spectrum Protect server is in read only mode.



Explanation:

The server has prevented a store operation on the IBM Spectrum Protect
server. The most likely explaination for this is the node has failed
over to the failover server.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect server administrator to verify if the
primary server is available. If the primary server is available, check
the error log for communications failures and correct any configuration
issues.

------------------------------------------------------------------------
ANS2136E

Operation not permitted. The failover server reports the primary server
is available. Quit and restart the IBM Spectrum Protect client and retry
the command.



Explanation:

The server has prevented a store operation on the failover IBM Spectrum
Protect server. The failover server reports that the primary server is
available. However, the IBM Spectrum Protect client failed over to the
failover server.

System action:

Processing stops.

User response:

Restart the IBM Spectrum Protect client and verify the primary server
connection is made. If the IBM Spectrum Protect client is unable to
connect to the primary server, contact the IBM Spectrum Protect server
administrator to verify if the primary server is available. If the
primary server is available, check the error log for communications
failures and correct any configuration issues.

------------------------------------------------------------------------
ANS2138E

Failed in restoring the vApp properties to vApp: 'vapp name'.



Explanation:

The vApp properties were not restored to 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, it is possible that the restored
object does not contain all of the expected content.

User response:

Check the backed up vApps on the vCloud. In addition, check the
dsmerror.log file for any additional messages that might be related to
this problem. Try the operation again. If the problem persists, visit
the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2143E

vApp verification failed. Data inconsistency was found.



Explanation:

During the verification of a vApp, an inconsistency was found in the
backup data.

System action:

The restore operation was stopped.

User response:

Examine the client error log for any additional messages that might be
related to this problem and contact IBM Spectrum Protect technical
support for further assistance.

------------------------------------------------------------------------
ANS2145W

Warning - updating an existing virtual machine named 'name'. The restore
operation continues.



Explanation:

The virtual machine exists and will be updated with the disks specified.

System action:

The virtual machine will be updated by the restore operation.

User response:

No user action is necessary.

------------------------------------------------------------------------
ANS2146E

The target vCenter or ESX/ESXi host is no longer supported, for virtual
machine backups, by this version of IBM Spectrum Protect.



Explanation:

The target vCenter or ESX/ESXi host is no longer supported, for virtual
machine backups, by this version of IBM Spectrum Protect.

System action:

Processing stops for this virtual machine.

User response:

Specify another target vCenter or ESX/ESXi host that is supported by
this version of IBM Spectrum Protect.

------------------------------------------------------------------------
ANS2147E

The virtual machine named 'name' already exists on the target system.



Explanation:

The virtual machine cannot be restored because the name already exists
on the target system.

System action:

Processing stops for this virtual machine

User response:

Use the -vmname option to rename the virtual machine.

------------------------------------------------------------------------
ANS2148I

Virtual machine templates cannot be backed up in incremental mode,
switching to full mode.



Explanation:

The backup of virtual machine templates are only supported as full
backups.

System action:

Processing continues in full mode for this template virtual machine.

User response:

To back up this virtual machine template use full mode.

------------------------------------------------------------------------
ANS2149E

The restore operation for this virtual machine to the target ESX/ESXi
host is not supported because virtual machine hardware version is
incompatible.



Explanation:

The target ESX/ESXi host does not support the virtual hardware version
of the virtual machine. As a result, a restore of the specified virtual
machine to this host is not supported.

System action:

Processing stops for this virtual machine.

User response:

Specify another virtual machine to restore or specify another target
ESX/ESXi host that supports virtual hardware version of the virtual
machine.

------------------------------------------------------------------------
ANS2150E

Set HSMDISABLEAUTOMIGDAEMONS YES in the dsm.opt file to use HSM
multi-server functionality.



Explanation:

Set HSMDISABLEAUTOMIGDAEMONS YES in the dsm.opt file to use HSM
multi-server functionality.

System action:

HSM multi-server processing stops.

User response:

Set HSMDISABLEAUTOMIGDAEMONS YES in dsm.opt.

------------------------------------------------------------------------
ANS2155W

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 the file.

------------------------------------------------------------------------
ANS2156E

The server 'server-name' was not added to the environment.



Explanation:

The requested IBM Spectrum 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 Spectrum Protect server for the file system was not
   yet added to the multi-server environment.

*  The IBM Spectrum Protect server name is not valid.

System action:

HSM multi-server processing stops.

User response:

Eliminate the possible causes for this issue and retry.

------------------------------------------------------------------------
ANS2157E

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



Explanation:

The requested IBM Spectrum 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 Spectrum Protect server is the default server for the file
   system and must be removed last.

*  The IBM Spectrum Protect server name is not valid.

System action:

HSM multi-server processing stops.

User response:

Eliminate the possible causes for this issue and retry.

------------------------------------------------------------------------
ANS2158E

The server 'server-name' was not added to the environment. You must
first add the default IBM Spectrum Protect server
('default-server-name') for this file system.



Explanation:

The requested IBM Spectrum Protect server was not added to the
multi-server environment. The requested IBM Spectrum Protect server is
not the default server for the file system.

System action:

HSM multi-server processing stops.

User response:

Add the default IBM Spectrum Protect server first.

------------------------------------------------------------------------
ANS2159I

The server 'server-name' was added to the environment.



Explanation:

The requested IBM Spectrum Protect server was added to the multi-server
environment.

System action:

HSM multi-server processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2160I

The server 'server-name' was removed from the environment.



Explanation:

The requested IBM Spectrum Protect server was removed from the
multi-server environment.

System action:

HSM multi-server processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2161E

The server 'server-name' is not a valid IBM Spectrum Protect server for
this environment.



Explanation:

The requested IBM Spectrum Protect server was not added to the
multi-server environment.

System action:

HSM multi-server processing stops.

User response:

Check the dsm.sys file for the correct IBM Spectrum Protect server name.

------------------------------------------------------------------------
ANS2162E

HSM cannot be removed from the file system. The IBM Spectrum Protect
multi-server list is not empty.



Explanation:

HSM management was not removed from the file system.

System action:

HSM processing continues.

User response:

Remove all IBM Spectrum Protect servers from the multi-server list
before removing HSM.

------------------------------------------------------------------------
ANS2163E

The default IBM Spectrum Protect server ('server-name') for the file
system will be removed.



Explanation:

The default IBM Spectrum Protect server will be removed. The IBM
Spectrum Protect server list for multi-server will be empty after this
step.

System action:

HSM processing continues without multi-server support.

User response:

nothing.

------------------------------------------------------------------------
ANS2165I

The server 'server-name' is the default server and has been removed
last.



Explanation:

The requested IBM Spectrum Protect server was removed from the
multi-server environment.

System action:

HSM multi-server processing continues.

User response:

None

------------------------------------------------------------------------
ANS2166I

The IBM Spectrum Protect server 'server-name' is not included in the
multi-server environment.



Explanation:

The requested IBM Spectrum Protect server is not part of the
multi-server environment.

System action:

HSM multi-server processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2167W

Can not read SERVERNAME attribute.



Explanation:

IBM Spectrum Protect cannot read the SERVERNAME attribute from file.

System action:

HSM multi-server processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2168W

Can not write SERVERNAME attribute.



Explanation:

IBM Spectrum Protect cannot write SERVERNAME attribute to file.

System action:

HSM multi-server processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2169E

Skipping - Requested server is not included in multi-server environment
for filesystem 'file-system'.



Explanation:

The requested IBM Spectrum Protect server is not part of the
multi-server environment.

System action:

HSM multi-server processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2170W

Skipping - file linked to another server.



Explanation:

The file is already coupled to another IBM Spectrum Protect server.

System action:

HSM continues with normal operation.

User response:

Use the correct server to process the file.

------------------------------------------------------------------------
ANS2171E

The DMAPI version 'dmapi-version' is not supported.



Explanation:

The DMAPI version installed on this node is not supported from the given
IBM Spectrum Protect client.

System action:

Due to this issue the affected HSM process ends.

User response:

Use the documentation to identify the supported DMAPI versions. Install
a supported DMAPI and retry the HSM command or process.

------------------------------------------------------------------------
ANS2172E

Command not supported in HSMBACKENDMODE TSMFREE.



Explanation:

That command is not supported using an external HSM backend.

System action:

Exit programm

User response:

Do not use the command

------------------------------------------------------------------------
ANS2173E

Volume 'volume name' from vFiler 'vFiler name' is mounted using AIX NFS
version 4. This configuration is not supported for snapshot difference
incremental backups.



Explanation:

Snapshot difference incremental backups are not supported for vFiler
volumes mounted using AIX NFS version 4.

System action:

Snapshot difference incremental backup fails.

User response:

This problem is documented by NetApp BURT 630200. Apply the fix for this
once it is available from NetApp. Specify "testflag
snapdiffenablevfilernfs4" in dsm.opt file and retry the snapshot
difference incremental backup.

------------------------------------------------------------------------
ANS2174E

Conflicting options HSMLOGMAX and HSMLOGRETENTION were specified.



Explanation:

Values were specified for both the HSMLOGMAX and the HSMLOGRETENTION
options. These options are mutually exclusive.

System action:

Processing stops.

User response:

Specify a nonzero value for HSMLOGMAX if you wish to have the IBM
Spectrum Protect hsm log wrap when it reaches the specified maximum
value. Use HSMLOGRETENTION if you wish you have the hsm log limited in
size on a time-based schedule.

------------------------------------------------------------------------
ANS2175I

Data from server 'server-name' should be recalled using the script
'dsmMultiServerRemove.pl'.



Explanation:

Migrated files must be recalled before a server can be removed from the
multiserver configuration.

System action:

The server will not be removed.

User response:

Check the documentation for detailed information about the
'dsmMultiServerRemove.pl' script.

------------------------------------------------------------------------
ANS2176E

The sample journal configuration file '' could not be copied to ''.



Explanation:

The IBM Spectrum Protect Journal Engine setup wizard tried to create a
new journal configuration file by copying the sample configuration file.
However the sample configuration file could not be successfully copied.

System action:

The IBM Spectrum Protect Journal Engine setup wizard stops.

User response:

Manually copy the sample journal configuration file
"config\tsmjbbd.ini.smp" to "baclient\tsmjbbd.ini", then try the IBM
Spectrum Protect Journal Engine setup wizard. The "baclient" and
"config" directories can be found in the directory where you installed
the IBM Spectrum Protect Backup-Archive Client. For example, "C:\Program
Files\Tivoli\TSM\baclient" and "C:\Program Files\Tivoli\TSM\config"

------------------------------------------------------------------------
ANS2177E

The vCloud vApp named 'vapp name' already exists on the target system.



Explanation:

The restore vApp command does not support restoring a vApp with an
existing name.

System action:

The restore was not performed.

User response:

Execute the required restore command again, considering that the given
name for the restored vApp is not used.

------------------------------------------------------------------------
ANS2181I

Option primary server; saved.



Explanation:

This node is configured for replication. The primary server name option
is now saved to the options file. The replication server options are set
by the IBM Spectrum Protect Administator, sent to the client during
logon, and are saved to the options file.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2182I

Option failover server; saved.



Explanation:

This node is configured for replication. The replication server option
is now saved to the options file. The replication server options are set
by the IBM Spectrum Protect Administator, sent to the client during
logon, and are saved to the options file.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2183E

Organization 'Org name' not found in the vCloud Director.



Explanation:

The specified Organization is not recognized by the vCloud Director.

System action:

The action requested for the organization is canceled.

User response:

Verify that an organization by the specified name exists in the vCloud.
Organization names are case-sensitive.

------------------------------------------------------------------------
ANS2184E

Organization VDC 'Org vDC name' not found in organization 'Org name'.



Explanation:

The specified organization VDC is not part of the specified
organization.

System action:

The action requested for the organization VDC is canceled.

User response:

Verify that an organization VDC by the specified name exists in the
specified organization. Organization and organization VDC names are
case-sensitive.

------------------------------------------------------------------------
ANS2185E

Failed to log on to the vCloud Director on 'vCD host name' with user
name 'vCD user name': Authentication failed.



Explanation:

The vCloud credentials specified in the VCDUser and VCDPass options were
rejected by the vCloud director.

System action:

vCloud operations cannot be performed.

User response:

Update the VCDUser and VCDPass options with valid credentials for the
vCloud Director.

------------------------------------------------------------------------
ANS2187E

Failed to establish connection to the vCloud Director on 'vCD host
name'.



Explanation:

A connection cannot be established to the vCloud Director on the host
that is specified by the VCDHost and VCDPort options.

System action:

vCloud operations cannot be performed.

User response:

Verify that the values of the VCDHOst and VCDPort options are valid,
network connectivity to the host exists, and that the vCloud Director
service is running.

------------------------------------------------------------------------
ANS2188E

The vCloud protection runtime library is not installed or failed to
load.



Explanation:

The vCloud runtime library is not installed or cannot be loaded.

System action:

vCloud operations cannot be performed.

User response:

Verify that the IBM Spectrum Protect for Virtual Environments vCloud
runtime library is installed. If neccessary, reinstall IBM Spectrum
Protect for Virtual Environments.

------------------------------------------------------------------------
ANS2189E

The vCloud protection runtime library cannot be initialized.



Explanation:

The vCloud protection runtime library failed to initialize. This issue
might be caused by the Java runtime not being installed.

System action:

vCloud operations cannot be performed.

User response:

Verify that Java is installed.

------------------------------------------------------------------------
ANS2190E

The vCloud protection runtime library encountered an internal error.



Explanation:

An internal error had occured in the vCloud runtime library.

System action:

vCloud operations cannot be performed.

User response:

Check the dsmerror.log file for any additional messages that might be
related to this problem. Try the operation again. If the problem
persists, visit the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2191E

An error occurred creating the default VSS staging directory 'path'.



Explanation:

The IBM Spectrum Protect client uses an VSS staging directory to store
files related to to VSS snapshot operations. The IBM Spectrum Protect
client was unable to create this directory structure.

System action:

The IBM Spectrum Protect client stopped.

User response:

If the problem persists, contact IBM technicalsupport for further
assistance.

------------------------------------------------------------------------
ANS2192E

Failed to read the node configuration information from node 'node name'.



Explanation:

Node mapping information is required for this vCloud operation. However,
the mapping information either does not exist or cannot be read from the
specified node.

System action:

The operation is canceled.

User response:

Make sure that you are accessing the correct node. The node mapping
information is stored in the Provider VDC node. If necessary, go to the
Configuration page and click 'Run the Configuration Wizard' to make
corrections to the node mapping.

------------------------------------------------------------------------
ANS2193E

The required filespace for the vApp 'vapp name' backup does not exist.



Explanation:

No filespace exists for the specified vApp backup.

System action:

The restore was not performed.

User response:

Make sure that the specified vApp is correct. Then, try the restore
operation again.

------------------------------------------------------------------------
ANS2194E

The snapshot data is incomplete for vApp 'vapp name'.



Explanation:

Inconsistent data was found in the backed up vApp. It is not possible to
restore the specified vApp.

System action:

The restore was not performed.

User response:

Check the dsmerror.log file for any additional messages that might be
related to this problem. If the problem persists, visit the IBM Support
Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2195E

The number of VMs that are available for restore is different from
expected according to the vApp 'vapp name' metadata.



Explanation:

Inconsistent data was found in the vApp metadata. It is not possible to
restore the specified vApp. More VMs have been backed up than are now
available for restore. This may happen due to incomplete node
replication or if a file space was deleted.

System action:

The restore was not performed.

User response:

Check the dsmerror.log file for any messages that may indicate the
problem. Run a detailed query for this vApp to verify that all VMs
backups exist. If node replication is used, ensure it is working
correctly. If the problem persists, visit the IBM Support Portal for
additional information at http://www.ibm.com/support/entry/portal/.
Contact IBM Spectrum Protect administrator for more information.

------------------------------------------------------------------------
ANS2196W

An incompatible disk configuration is detected for the following disk:
'disk name'. The individual database restore for the following database
is not supported:'database name'.



Explanation:

One or more database files in this operation are located on the dynamic
or GUID Partition Table (GPT) disks. In this configuration, individual
database restore is not supported.

System action:

Backup of the full VM continues.

User response:

To restore the environment to the previous statue, issue a full VM
restore.

------------------------------------------------------------------------
ANS2197E

The verification test of vApp 'vapp name' indicates that VM data is
incomplete in the vApp. The vApp cannot be restored.



Explanation:

Inconsistent data was found in the VM for the specified vApp. It is not
possible to restore the specified vApp. This may happen due to
incomplete node replication or if a file space was deleted.

System action:

Operation continues.

User response:

Check the dsmerror.log file for any additional messages that might be
related to this problem. Run a detailed query for this vApp to verify
that 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 the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/. Contact IBM Spectrum Protect
administrator for more information.

------------------------------------------------------------------------
ANS2198I

Backup of VMware vCloud Director vApp 'vApp name' in Organization VDC
'Org VDC name' of organization 'Org name' completed successfully. VMs:
number of VM backed up out of number of VMs in vApp VMs backed up
successfully.



Explanation:

The backup operation completed. The number of VMs backed up and the
total number of VMs in the vApp are displayed.

System action:

This message is for informational purposes only.

User response:

If the number of VMs backed up is less than the total in the vApp please
check the error logs for more information.

------------------------------------------------------------------------
ANS2200I

***** Filling Cache count files *****



Explanation:

IBM Spectrum Protect the specified number of files have been added to
the disk cache.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2201I

***** Inspecting Cache count files *****



Explanation:

IBM Spectrum Protect the specified number of files have been examined in
the disk cache.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2202E

Disk Full Error Accessing Disk Cache.



Explanation:

A disk full error occurred attempting to access or write to the
specified disk cache file during a disk cache incremental backup. See
the client error log for more detailed information.

System action:

Processing stops.

User response:

This error can be resolved by freeing up space in the file system
containing the cache file, or specifying a different location for the
cache file. Use the diskcachelocation option to specify the location of
the cache file.

------------------------------------------------------------------------
ANS2203E

Error Accessing Disk Cache.



Explanation:

An error occurred attempting to access the specified disk cache file
during a disk cache incremental backup. See the client error log for
more detailed information. IBM Spectrum Protect.

System action:

Processing stops.

User response:

None.

------------------------------------------------------------------------
ANS2204E

Disk cache restarted.



Explanation:

The length of an object name exceeded the configured disk cache key
length during a disk cache incremental backup. The backup must be
restarted.. IBM Spectrum Protect.

System action:

Backup is restarted with a larger key length to accommodate the object
name.

User response:

None required. The name of the object that caused the failure can be
found in the dsmerror.log file.

------------------------------------------------------------------------
ANS2206W

The user must have root authority to use the memory efficient backup
disk cache method. The operation will continue using memory efficient
backup method without disk caching.



Explanation:

None.

System action:

The operation continues without using disk caching.

User response:

None.

------------------------------------------------------------------------
ANS2213W

The virtual machine 'vm-name' is configured with an invalid number of
snapshot attempts specified by the tag 'tag' for category 'cat'.



Explanation:

An invalid number of snapshot attempts is specified for the quiescing or
nonquiescing snapshot attempts in the tag value. The maximum value that
you can specify is 10 for either type of snapshot attempts. The minimum
value that you can specify is 0, but both numbers cannot be 0.

System action:

The operation continues with the default number of quiescing and
nonquiescing attempts (2,0).

User response:

Change the pair of numbers in the tag so that the number of quiescing
and nonquiescing attempts is between 0-10, and that both numbers cannot
be 0.

------------------------------------------------------------------------
ANS2218I

The encryption key password for node node name and server server name
has been migrated.



Explanation:

The format of the IBM Spectrum Protect password file has recently
changed. The option MIGRATEENCRYPTKEY is set and the stored encryption
key password was automatically migrated to the new format. This message
confirms that the migration was successful.

System action:

The encryption key password has been migrated.

User response:

No response.

------------------------------------------------------------------------
ANS2219E

Cannot backup or archive files into filespace because it is owned by a
IBM Spectrum Protect API application.



Explanation:

IBM Spectrum Protect Client cannot archive or backup files into a file
space that is used a IBM Spectrum Protect API application.

System action:

Processing stops.

User response:

Use separate node names for IBM Spectrum Protect Client and IBM Spectrum
Protect API application(s).

------------------------------------------------------------------------
ANS2220E

The cluster disk could not be put in maintenance mode.



Explanation:

The system call to put the cluster disk in maintenance mode failed.

System action:

Processing stopped.

User response:

Try the operation again. If the problem continues, check the client
error log for any other messages that might have been logged when this
message was written, and take the corrective action (if any) suggested
by those messages. Examine the Windows event log which may contain
additional information. See your system administrator or IBM Spectrum
Protect administrator for further help.

------------------------------------------------------------------------
ANS2221W

Java was not able to resolve the IP address of your local machine due to
network misconfiguration problems! Please verify your network and DNS
configuration are setup correctly. Note that on UNIX machines the
hostname must be reported correctly (the same) for IPv4 and IPv6
communication methods in the /etc/hosts configuration file. IBM Spectrum
Protect processing continues.



Explanation:

Java was not able to get the local host address due to network
misconfiguration problems.

System action:

Processing continues.

User response:

Please verify your network and DNS configuration are setup correctly.
Note that on UNIX machines the hostname must be reported correctly (the
same) for IPv4 and IPv6 communication methods in the /etc/hosts
configuration file. See your system administrator or IBM Spectrum
Protect administrator for further help.

------------------------------------------------------------------------
ANS2223W

Rejected unauthenticated server-initiated session from peer name.



Explanation:

For security, the client will not accept server-initiated sessions from
servers that have authentication turned off.

System action:

The client-server session is not opened, and the schedule is not
executed. The scheduler continues to wait for contact by a server that
has authentication turned on.

User response:

If the client system is supposed to accept scheduled events from the
prompting IBM Spectrum Protect server, either ask the IBM Spectrum
Protect server administrator to turn authentication on, or do not use
server-initiated sessions. If the client system is not supposed to
accept scheduled events from the prompting server, ask the IBM Spectrum
Protect server administrator to remove the client node name from the
schedule on the prompting server.

------------------------------------------------------------------------
ANS2225W

User has specified 'SNAPSHOTROOT' option. snapshot provider snapshot
backup is not valid in conjunction with this option. "SNAPSHOTROOT
option will take precedence and processing will continue without the use
of a snapshot taken internally by IBM Spectrum Protect.



Explanation:

The (-SNAPSHOTROOT) option is incompatible with IBM Spectrum Protect
snapshot providers such as Logical Volume Snapshot Agent, VSS snapshot
provider, JFS2 snapshot provider etc. which provide a comprehensive
snapshot solution withot having to use the (-SNAPSHOTROOT) option. It is
strongly recommended that the snapshot capabilities provided by the IBM
Spectrum Protect snapshot providers be used instead of using the
(-SNAPSHOTROOT) option. Processing will continue without the use of the
IBM Spectrum Protect snapshot providers.

System action:

Processing continues without the use of the IBM Spectrum Protect
snapshot providers.

User response:

See the appropriate Using the Backup-Archive Client book for your
operating system for correct use of the named option.

------------------------------------------------------------------------
ANS2226W

The virtual machine 'vm-name' is configured with an invalid hard disk
list, specified by the tag 'tag' for category 'cat'.



Explanation:

An invalid hard disk number is specified in the disk backup list tag
value. The minimum hard disk number that you can specify is 1 and the
maximum hard disk number that you can specify is 999. Also, the hard
disk numbers must be comma separated positive integer values.

System action:

Processing stopped.

User response:

Change the hard disk list tag so that the hard disk numbers are between
1-999, and are listed as comma separated values.

------------------------------------------------------------------------
ANS2227W

Server option 'option-name' 'option-value' has not been applied on the
client due to the client option SRVOPTSETENCRYPTIONDISABLED.



Explanation:

When the client option SRVOPTSETENCRYPTIONDISABLED is set to YES on the
client it prevents the IBM Spectrum Protect administrator from setting
one of the following client options ENCRYPTIONTYPE, EXCLUDE.ENCRYPT,
INCLUDE.ENCRYPT. The client option setting ENCRYPTKEY GENERATE is also
prevented, but the client option settings ENCRYPTKEY PROMPT and
ENCRYPTKEY SAVE are not prevented.

System action:

The option is ignored.

User response:

None.

------------------------------------------------------------------------
ANS2228W

Backup of VMware vCloud Director vApp 'vApp name' in Organization VDC
'Org VDC name' of organization 'Org name' completed. Some VMs were not
backed up. VMs: number of VM backed up out of number of VMs in vApp VMs
backed up successfully.



Explanation:

The vApp backup operation completed successfully. However, one or more
VMs for the specified vApp were not backed up. These VMs will not be
created during the restore operation.

System action:

Processing continues to the next vApp.

User response:

Check the log file for this vApp for more information about this
message. Resolve the problem, then try the operation again.

------------------------------------------------------------------------
ANS2229E

Failed to initialize the vCloud protection environment. See the local
client error log for detailed error message information.



Explanation:

The vCloud protection package could not be initialized.

System action:

The operation is stopped

User response:

Make sure all options that are related to the vCloud environment are
specified correctly. Check the dsmerror.log file for detailed
information.

------------------------------------------------------------------------
ANS2230E

Failed to create vApp list according to spec 'vApp specification'



Explanation:

The vApp list was unable to be retrieved from the vCloud Director.

System action:

The operation is stopped

User response:

Make sure the values specified in the VCDHost, VCDUser, VCDPW, and
DOMAIN.VCD options are correct. Make sure the vCloud Director is alive.

------------------------------------------------------------------------
ANS2231I

The IBM category 'cat' was not found.



Explanation:

The IBM Spectrum Protect option 'VMTAGDATAMOVER' is enabled so that IBM
categories and tags can be applied to virtual machines, but the IBM
category was not found.

System action:

The backup operation continues without tagging support.

User response:

Create the required IBM categories in the VMware vSphere web client or
disable the data mover option 'VMTAGDATAMOVER' in the client options
file.

------------------------------------------------------------------------
ANS2232E

Failed to retrieve the list of VMs for vApp 'vApp name' from the vCloud
Director.



Explanation:

The VM information for the specified vApp was not retrieved from the
vCloud Director. This failure might be caused by the vCloud Director not
being alive or accessible.

System action:

The VMs that compose the specified vApp are not backed up. Processing
continues to the next vApp.

User response:

Make sure that the vCloud Director is alive and accessible. Check the
dsmerror.log file for specific errors that are related to this issue.

------------------------------------------------------------------------
ANS2233I

The IBM tag 'tag' for category 'cat' was not found.



Explanation:

The IBM Spectrum Protect option 'VMTAGDATAMOVER' is enabled so that IBM
categories and tags can be applied to virtual machines, but the IBM tag
was not found.

System action:

The operation continues without tagging support.

User response:

Create the required IBM tags in the VMware vSphere web client or disable
the data mover option 'VMTAGDATAMOVER' in the client options file.

------------------------------------------------------------------------
ANS2234W

Restore from virtual machine backup 'vm-name' is not available for
database 'db-name'. reason



Explanation:

Restore from virtual machine backup is not supported for in-guest
application databases for one of the following reasons:

*  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 Spectrum 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.



------------------------------------------------------------------------
ANS2236I

The virtual machine 'VM-name' contains one or more disks that exceed the
maximum size set by the VMMAXVIRTUALDISKS option. These disks will be
excluded from the backup.



Explanation:

The IBM Spectrum Protect client does not back up VMDKs that are larger
than the maximum size.

System action:

The virtual machine is backed up; however, the disks that exceed the
limit are excluded from the backup.

------------------------------------------------------------------------
ANS2238E

VCDHOST option must be set before running this operation.



Explanation:

VCDHOST option is missing.

System action:

Operation cannot continue without this option being set.

User response:

Add the option to the client options file, either via the preferences
editor or by manually editing the file, or specify the option on the
command line.

------------------------------------------------------------------------
ANS2242E

No nodes were found that matched the input specification: node
specification



Explanation:

An invalid node specification was entered.

System action:

The operation was stopped.

User response:

Check documentation how to specify nodes.

------------------------------------------------------------------------
ANS2244W

The virtual machine contains one or more disks that exceed the maximum
size set by the VMMAXVIRTUALDISKS option. You can use the
VMMAXVIRTUALDISKS option to change the maximum size or specify the
'-VMSKIPMAXVIRTUALDISKS=yes' option to exclude these disks from the
backup.



Explanation:

The IBM Spectrum Protect client does not back up VMDKs or VHDXs that are
larger than the maximum size.

System action:

The virtual machine is not backed up.

User response:

Use the VMMAXVIRTUALDISKS option to change the maximum size or specify
the '-VMSKIPMAXVIRTUALDISKS=yes' option to exclude these disks from the
backup.

------------------------------------------------------------------------
ANS2245E

Virtual machine backups and restores are not supported on 32 bit data
movers.



Explanation:

Virtual machine operations such as backups and restores are not
supported on 32 bit Data Movers.

System action:

The operation is not performed.

User response:

Update to a 64 bit Data Mover and retry the operation.

------------------------------------------------------------------------
ANS2246W

Failed to disable maintenance mode for vApp vApp name.



Explanation:

The client has tried to disable the maintenance mode of this vApp. This
operation failed.

System action:

Operation continues.

User response:

Check whether the vApp is still in maintenance mode. If yes, disable it
manually.

------------------------------------------------------------------------
ANS2247E

ASNODENAME option must be specified when running this command.



Explanation:

When running vCloud-related commands, ASNODENAME option must specify the
Provider vDC node.

System action:

Operation cannot continue.

User response:

Specify the Provider vDC node as ASNODENAME to the command.

------------------------------------------------------------------------
ANS2248E

Failed to load or initialize the Java runtime library.



Explanation:

The Java runtime library (libjvm), required by the vCloud Protection
environment, cannot be loaded, or initialization of Java runtime
environment failed

System action:

Operation is stopped

User response:

For Linux operating system, verify that a link named 'jre', referencing
the 'jre' directory under your Java installation path, exists in the
backup-archive client installation directory. If a link does not exist,
create the link (e.g. ln -s /opt/ibm/java-x86_64-70/jre
/opt/tivoli/tsm/client/ba/bin/jre). Alternatively, modify
LD_LIBRARY_PATH to include the path to libjvm.so (e.g. export
LD_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 that the JRE directory exists under
the client installation directory. Reinstall the backup-archive client
if necessary.

------------------------------------------------------------------------
ANS2249W

A virtual machine named 'vmname' exists on this system. Do you want to
replace the existing virtual machine?



Explanation:

Restoring this virtual machine will stop and delete the existing virtual
machine and all of its files. To protect application data, stop any
applications that are running, and then shut down the virtual machine
before you restore it.

System action:

If the user chooses to continue, the system will stop and delete the
existing virtual machine and all of its files.

User response:

Choose whether to replace the existing virtual machine.

------------------------------------------------------------------------
ANS2250W

A IBM Spectrum Protect core file or crash report was found: filename



Explanation:

The presence of a core dump or crash report indicates a process has
abnormally terminated.

System action:

The core file or crash report name is reported in the message.
Processing continues.

User response:

Review the error log for any other error messages that may help diagnose
the cause of the core dump. If possible, correct any issues found. As a
core dump is generally caused by a programming error, save the file
noted in this message and contact IBM technical support.

------------------------------------------------------------------------
ANS2253W

The version of the message catalog, catalogversion, in use by IBM
Spectrum Protect does not match the version of IBM Spectrum Protect,
clientversion



Explanation:

A check of the catalog version indicates the catalog and IBM Spectrum
Protect are not the same version. This may lead to missing or incorrect
messages being used.

System action:

Processing continues.

User response:

Review the installation of IBM Spectrum Protect, verify the message
catalog files match the installed version of IBM Spectrum Protect.
Re-installation of IBM Spectrum Protect may be required, or a system
reboot may be required to complete the installtion.

------------------------------------------------------------------------
ANS2254E

program-name with session id sessid aborted recall for token token.
ERRNO errno : errno-text was set. See message explanation.



Explanation:

A recall was aborted from HSM. The ERRNO set from HSM explains why the
recall was aborted.

System action:

The recall request was aborted from the HSM service.

User response:

Transient errors: Solve problem indicated from the errno. On GPFS
platforms: Use command dsmmigfs q -d -n=all to verify HSM and GPFS are
running properly. Retry the recall operation if failed file can be
identified. Enable HSM Logging if failed failed file cannot be
identified and wait for new occurrence. (HSM Logging allows you to map
between the token displayed from the ANS message and the recalled file)
Static errors: Restore the file from backup.

------------------------------------------------------------------------
ANS2260E

Failed to lock IBM Spectrum Protect password file.



Explanation:

In multi-process environment IBM Spectrum Protect client locks the
password file during authentication to avoid conflicts on updating
password in case the currect password is expired.

System action:

processing stops

User response:

Try to use MAXRETRIESLOCK test flag to increase number of attempts to
lock the file. The default value is 1500.

------------------------------------------------------------------------
ANS2261E

IBM Spectrum Protect client failed to lock options file.



Explanation:

In multi-process environment IBM Spectrum Protect client locks the
options file during initialization to avoid conflicts on reading or
adding an option.

System action:

processing continue

User response:

Try to decrease a number of IBM Spectrum Protect client processes

------------------------------------------------------------------------
ANS2262I

The service is starting.



Explanation:

The file restore service is starting.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2263I

The service started.



Explanation:

The file restore service started.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2264I

The shutdown is in progress.



Explanation:

The shutdown is in progress.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2265I

The service is shutting down.



Explanation:

The file restore service is shutting down.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2266I

The option 'option-name' is set to the default value of 'default-value'.



Explanation:

An error was detected with the option value.

System action:

The default setting is used.

User response:

To use a non-default value, correct the option value in the
frConfig.props file.

------------------------------------------------------------------------
ANS2267W

The 'option-name' option value 'invalid-value' is invalid.



Explanation:

An error was detected with the option value.

System action:

The default setting is used.

User response:

To use a non-default value, correct the option value in the
frConfig.props file. Then, restart the web server that is hosting the
file restore interface.

------------------------------------------------------------------------
ANS2268W

The TCP/IP port address on the mount proxy node cannot be located or is
invalid.



Explanation:

The mount proxy node requires a TCP/IP port address. This address is
used for communication by the client acceptor on the mount proxy node.

*  If a local mount proxy node is used, the TCP/IP port address that was
   specified with the configuration wizard or notebook is invalid.

*  If a remote mount proxy node is used, the default_mp_httpport option
   in the frConfig.props file is either not specified or is invalid.

Communication with the client acceptor cannot start.

System action:

Processing stops.

User response:

If a local mount proxy node is used, use the Mount Proxy Node Pairs page
in the configuration wizard or notebook to remove the mount proxy node.
Then, add the mount proxy node again to resolve this issue.

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.

------------------------------------------------------------------------
ANS2269E

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.



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.

------------------------------------------------------------------------
ANS2271W

Unsuccessful deletion of archived file fshlll



Explanation:

An attempt to delete the archived file was unsuccessful.

System action:

Processing continues.

User response:

Check the console or schedule log for additional information. Retry the
operation at a later time.

------------------------------------------------------------------------
ANS2272E

The Comma Separated Values (CSV) file specified 'CSV_file' could not be
found or opened.



Explanation:

The CSV option uses a Comma Separated Values (CSV) file as input for
this operation. The specified CSV file could not be found or opened.

System action:

The operation has stopped.

User response:

Check that the file path is correct and that the file permissions allow
read access. Try the operation again.

------------------------------------------------------------------------
ANS2273E

The Comma Separated Values (CSV) file has two or more columns
'column_title' with the same title. Duplicate column names are not
allowed.



Explanation:

The specified operation, started from a Comma Separated Values (CSV)
file, requires unique columns. For example, if you specify the column
"New Host" twice, the operation cannot determine which value to use.

System action:

The operation has stopped.

User response:

Remove any duplicat ecolumns. Try the operation again.

------------------------------------------------------------------------
ANS2274I

The column 'column_title' in the Comma Separated Values (CSV) file is
not recognized for the current operation and will be ignored.



Explanation:

Each operation type recognizes a different set of column names in a
Comma Separated Values (CSV) file. The specified column is not used by
the current operation.

System action:

The column that the operation could not recognize is ignored. The
operation continues.

User response:

Change the name if it the column is misspelled. Otherwise, no action is
needed. You can also simply remove the column.

------------------------------------------------------------------------
ANS2275W

The element 'element_name' in the column labeled 'column_title' in the
Comma Separated Values (CSV) file can not be used in this operation. Row
elements must be unique for each column.



Explanation:

The operation requires that each element in the Comma Separated Values
(CSV) file is unique for that column. For example, if two rows contained
the same value for "Virtual Machine Name", inconsistent instructions
could be applied to that VM.

System action:

The operation has stopped.

User response:

Remove the row that contains the duplicate element. Try the operation
again.

------------------------------------------------------------------------
ANS2276E

The Comma Separated Values (CSV) file 'file_name' has a row count of
row_count. The current operation requires a minimum of
required_row_count to execute.



Explanation:

The current operation requires a certain number of rows in the Comma
Seperated Values (CSV) file in order to execute. The row count in the
CSV file is below this value.

System action:

The operation has been stopped.

User response:

Add the input rows required for this operation to the CSV file. Try the
operation again.

------------------------------------------------------------------------
ANS2277E

The element in the Comma Separated Values (CSV) file on row row under
column 'column_name' with the value of 'element_value' is invalid or
missing.



Explanation:

The current operation encountered an invalid or missing value in the
Comma Separated Values (CSV) file.

System action:

The operation has been stopped.

User response:

Correct the identified element. Try the operation again.

------------------------------------------------------------------------
ANS2278E

The time_option option cannot be used without specifying the date_option
option on row row of the Comma Separated Values (CSV) file.



Explanation:

If the PITTIME option cell exists thens the corresponding PITDATE cell
must exist.

System action:

Processing has stopped.

User response:

Either remove the PITTIME option cell or add the corresponding PITDATE
option cell.

------------------------------------------------------------------------
ANS2279E

The Comma Separated Values (CSV) file is missing the required column
'column_name' for the current operation.



Explanation:

To perform the task, the current operation requires a specific column in
the CSV file. This column is missing from the CSV file.

System action:

Processing has stopped.

User response:

Add the required column and the required elements for that column to the
CSV file.

------------------------------------------------------------------------
ANS2280E

The Comma Separated Values (CSV) file 'csv_file' is invalid. The CSV
file must have the same number of columns per row. The first row of the
CSV file contains first_row_column_count columns.



Explanation:

The CSV file submitted is invalid because the number of columns on each
row is not identical.

System action:

Processing has stopped.

User response:

Edit the CSV file so that the number of columns per row is identical.
Try the command again.

------------------------------------------------------------------------
ANS2281E

The current operation encountered a blank element in the Comma Separated
Values (CSV) file 'csv_file' on row row_number, column column_number.



Explanation:

The current operation found a blank element in the CSV file where a
value is required for the operation to continue. CSV files used for this
operation must contain values in all fields. All required columns must
be present.

System action:

Processing has stopped.

User response:

Edit the CSV file and provide data where a cell is blank or an entire
column is missing. Try the operation again.

------------------------------------------------------------------------
ANS2282E

An element in the Comma Separated Values (CSV) file csv_file is not a
valid element: 'string_value'



Explanation:

The current operation encountered a invalid or missing value that is
required for the operation in the Comma Separated Values (CSV) file.

System action:

The operation is stopped.

User response:

Correct the identified element.

------------------------------------------------------------------------
ANS2284E

The Microsoft Hyper-V backup cannot be deleted.



Explanation:

Deleting the Hyper-V backup will cause data integrity issues because the
next incremental backup operation will not back up all required data.
For this reason, do not delete Hyper-V backups.

System action:

The backup is not deleted, but system operation continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2307I

IBM Spectrum Protect category or tag can not be found on vCeter.
Category: category-name, tags: tag-names



Explanation:

Spectrum Protect category are not present on the vCenter. Setup might be
incomplete. Please run 'dsmc set vmtags' to add the necessary tags. This
message can safely be ignored if the tag-based schedule is not being
used.

System action:

Processing continues.

User response:

Check the vcsplugin.log file for additional information and contact the
IBM Spectrum Protect administrator if you require further assistance.

------------------------------------------------------------------------
ANS2308E

The VMware vCloud Suite API reported the following error message:
'api-message'.



Explanation:

The VMware vCloud Suite API reported an error with the specified
message.

System action:

Processing stops.

User response:

Check the vcsplugin.log file for additional information and contact the
IBM Spectrum Protect administrator if you require further assistance.

------------------------------------------------------------------------
ANS2309I

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



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.

------------------------------------------------------------------------
ANS2310E

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



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.

------------------------------------------------------------------------
ANS2311E

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



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.

------------------------------------------------------------------------
ANS2312E

-DELTYPE=ALL is not allowed for DELETE BACKUP -OBJTYPE=VM.



Explanation:

DELTYPE=ALL is not a valid option value when deleting VM backup objects.

System action:

The command is not executed.

User response:

If you wish to delete all backups for a VM node, use the DELETE
FILESPACE command.

------------------------------------------------------------------------
ANS2313E

-FILELIST is not allowed for DELETE BACKUP or EXPIRE when -OBJTYPE=VM.



Explanation:

-filelist is not a valid option value when deleting or expiring VM
backup objects.

System action:

The command is not executed.

User response:

If you wish to delete or expire all backups for a VM node, use the
DELETE FILESPACE command.

------------------------------------------------------------------------
ANS2314E

No VM backup exists for VM-Name.



Explanation:

The IBM Spectrum Protect server has no record of a VM backup for the VM
name provided. The backup might have been deleted, or the VM name
spelled incorrectly.

System action:

The command is not executed.

User response:

If spelling is the problem, correct it and resubmit the command.

------------------------------------------------------------------------
ANS2315E

-PICK is not allowed for EXPIRE when -OBJTYPE=VM.



Explanation:

-pick is not a valid option value when expiring VM backup objects.

System action:

The command is not executed.

User response:

If you wish to expire all VM nodes, use the DELETE FILESPACE command.

------------------------------------------------------------------------
ANS2316E

Wildcards are not allowed in the VM name argument.



Explanation:

When expiring or deleting a VM backup, the VM name must be specified
exactly. The EXPIRE -OBJTYPE=VM command processes only one backup on
each invocation. When -INACTIVE is present the DELETE BACKUP -OBJTYPE=VM
command displays all versions of a single VM backup in a list from which
to choose. If -INACTIVE is not present, this command expires the current
active VM backup.

System action:

The command is not executed.

User response:

Specify only one VM name without wild cards. It may be in upper or lower
case.

------------------------------------------------------------------------
ANS2317E

Deletion of VM object VMname failed. Reason:



Explanation:

The transaction which deletes the named VM object failed at the server.
The reason code ....?????

System action:

The deletion is skipped and processing continues with the next
selection, if any.

User response:

Consult the error log for specific reasons for this failure.

------------------------------------------------------------------------
ANS2318E

Command with -OBJTYPE=VM requires exactly one non-option argument



Explanation:

This command accepts only a single VM name as an argument. Either no
arguments were entered or more than one appeared on the command line.

System action:

The command is not executed.

User response:

Specify only one VM name without wild cards. It may be in upper or lower
case.

------------------------------------------------------------------------
ANS2319W

DELETE BACKUP -OBJTYPE=VM finished with failures.



Explanation:

One or more deletions failed.

System action:

The VM backups which failed have been reported in previous messages.
Processing continues with the next selection, if any.

User response:

Consult the previous error messages for the cause of each failure.

------------------------------------------------------------------------
ANS2320I

DELETE BACKUP -OBJTYPE=VM finished without failures.



Explanation:

All VM backups selected for deletion were deleted.

System action:

Control returns to the command line.

User response:

No action is required, this message is informational.

------------------------------------------------------------------------
ANS2321W

EXPIRE with -OBJTYPE=VM finished with failures.



Explanation:

The command did not complete, no objects were expired.

System action:

The VM expire which failed has been reported in previous messages.

User response:

Consult the previous error messages for the cause of the failure.

------------------------------------------------------------------------
ANS2322I

EXPIRE with -OBJTYPE=VM finished without failures.



Explanation:

The EXPIRE command executed successfully.

System action:

Control returns to the command line.

User response:

No action is required, this message is informational.

------------------------------------------------------------------------
ANS2323E

The user ID and password for VMware vCloud Director 'vCD host name' are
not set.



Explanation:

The user ID and password for VMware vCloud Director could not be read
from encrypted password file.

System action:

Processing stops.

User response:

Issue the dsmc SET PASSWORD -type=VCD 'vCloud Director hostname'
'userid' 'password' command to save an encrypted password.

------------------------------------------------------------------------
ANS2324W

WARNING: The VMware vCloud Director user ID <hostuserid> read from the
password file is different from the VCDUser option value <vmcuserid>.
Using stored value.



Explanation:

All user IDs that are specified in the TSM.PWD file and in the VCDUSER
option must be the same.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information that
is provided in this message.

------------------------------------------------------------------------
ANS2325E

Error Accessing Snapshot Differential Change Log for filer '' volume '',
see client error log for more information.



Explanation:

The Snapshot Differential Change Log needed needed to backup the
specified filer volume could not be accessed

System action:

The backup of the specified volume fails.

User response:

Ensure that the client staging directory where change logs are located
is accessible.

------------------------------------------------------------------------
ANS2326W

Corrupt Snapshot Differential Change Log detected, change log will be
reset and a full progressive incremental will be performed.



Explanation:

A corrupt snapshot differential change log for the filer volume being
backed up was detected.

System action:

The change log will be reset and a full progressive incremental with a
new base snapshot will be performed.

User response:

none.

------------------------------------------------------------------------
ANS2327I

Creating Snapshot Differential Change Log.



Explanation:

A new snapshot differential change log was created.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS2328I

Using Snapshot Differential Change Log.



Explanation:

A snapshot differential change log is being used for the backup.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS2329W

Down level Snapshot Differential Change Log detected, Change Log will be
reset and a full progressive incremental will be performed.



Explanation:

none.

System action:

none.

User response:

none.

------------------------------------------------------------------------
ANS2330E

Failed to unfreeze the VSS writers because the snapshot time exceeded
the 10 second timeout limitation.



Explanation:

Microsoft VSS has a 10 second timeout limitation between freeze and thaw
events for VSS writers on a VM. When the snapshot time exceeds the 10
second timeout limit, the VSS writers return to a 'failed' state. This
failed state occurs because the VSS provider did not thaw the VSS
writers within the allowed time.

System action:

Processing stops.

User response:

Check the event log. Ensure that the writers on the guest VM are in
'stable' state before trying an application protection VM backup
operation again. A snapshot operation must be completed within 10
seconds.

------------------------------------------------------------------------
ANS2331W

No match found on the server for the Hyper-V VM name or VMList 'string'
entered



Explanation:

No match found on the server for the Hyper-V VM name or VMList parameter
entered.

System action:

None.

User response:

Specify another Hyper-V VM name or VMList parameter that exists on the
server.

------------------------------------------------------------------------
ANS2332E

Failed to log on to the vCloud Director. Authentication failed.



Explanation:

The vCloud credentials were rejected by the vCloud Director.

System action:

The operation is stopped

User response:

Update username and password for the vCloud Director.

------------------------------------------------------------------------
ANS2333E

Failed to establish connection to the vCloud Director.



Explanation:

A connection cannot be established to the vCloud Director on the host
that is specified by the VCDHost and VCDPort options.

System action:

The operation is stopped

User response:

Verify that the values of the VCDHOst and VCDPort options are valid,
network connectivity to the host exists, and that the vCloud Director
service is running.

------------------------------------------------------------------------
ANS2334E

An operation requiring the Windows Management Instrumentation (WMI)
service has failed with the error 'errorstring'. Unable to connect to
the Hyper-V namespace. Confirm that Hyper-V is installed on the backup
node.



Explanation:

The Windows Management Instrumentation (WMI) namespace
"root\virtualization\v2" for Hyper-V could not be found. This namespace
is installed with Hyper-V. If Hyper-V is installed, Hyper-V is not in a
good state.

System action:

Creating a connection to the Hyper-V WMI provider.

User response:

Check that Hyper-V is installed. If Hyper-V is not installed, install
Hyper-V before attempting this operation again.

------------------------------------------------------------------------
ANS2335E

An operation requiring the Windows Management Instrumentation (WMI)
service has failed with the error 'errorstring'. The WMI service is in
the shutting down or shutdown state. Restart the service and try again.



Explanation:

The Windows Management Instrumentation (WMI) service has received a
request to shutdown or has been shutdown due to an external error. An
internal operation which requires WMI has been attempted and failed. The
requested operation is unavailable while WMI is shutdown.

All Hyper-V operations require the Windows Management Instrumentation
service.

System action:

An internal IBM Spectrum Protect operation involving Windows Management
Instrumentation has occurred.

User response:

Restart the Windows Management Instrumentation service.

------------------------------------------------------------------------
ANS2336W

IBM Spectrum Protect has detected that the following Hyper-V virtual
machine "virtual_machines" has an interrupted incremental backup chain.
Performing a full backup on the specified Hyper-V virtual machine.



Explanation:

The last operation of the virtual machine was a restore; or an unknown
party has performed incremental backup operations on the listed virtual
machine. To prevent backup corruption a full backup will be performed
instead.

System action:

IBM Spectrum Protect has detected that a virtual machine has an
interrupted incremental backup chains.

User response:

A full backup is performed instead of an incremental.

------------------------------------------------------------------------
ANS2337E

The process was unable to take cluster resource 'resourcename' offline.
The current operation requires the resource to be offline. Turning the
cluster resource off failed with rc=rc.



Explanation:

The cluster resource was not taken offline within the time limit or an
attempt was made to take offline a failed cluster resource.

System action:

The current operation stops.

User response:

Check that the cluster resource is not in a failed state. Verify that
the cluster resource can be taken offline.

------------------------------------------------------------------------
ANS2338W

The process has detected a request to backup a virtual machine replica.
The state of the replica 'vmreplicaname', ID='vmid' may differ from the
original virtual machine. If the names of the original virtual machine
and the replica are identical the same file space will be used. The data
may become unrecoverable because the state of the original virtual
machine and the replica may differ.



Explanation:

Backups of an original virtual machine and their replica overwrite each
other as their name and ID are usually identical. Virtual machine
replicas are taken in definite time intervals. Between these intervals
the data on the original and the replica may differ. In some occasions
the difference may cause data corruption if a backup of the original is
followed by a backup of the replica.

System action:

A backup request of a virtual machine replica is being processed.

User response:

Configure IBM Spectrum Protect to back up only the original virtual
machine or the replica. Alternatively, one can change the name of the
replica compared to the original virtual machine; and the replica will
back up to a separate file space.

------------------------------------------------------------------------
ANS2339W

The Hyper-V VM 'vmname' is in a "branch" state compared to the last
backup. Incremental Forever - Incremental backup cannot be performed. An
Incremental Forever - Full backup will be performed instead.



Explanation:

The VM state is in a "branch" compared to the last backup. This causes a
fallback to Incremental Forever - Full as backup consistency in this
state is not guaranteed.

System action:

An Incremental Forever - Full backup will be performed.

User response:

None.

------------------------------------------------------------------------
ANS2340W

The target virtual machine 'VM-name' exists, use the REPLACE option to
overwrite.



Explanation:

The specified target VM exists and the user specified not to allow
restore to replace existing machines.

System action:

The virtual machine is not restored.

User response:

Specify a different virtual machine as a restore target or specify that
existing virtual machines can be replaced.

------------------------------------------------------------------------
ANS2341E

The target virtual machine 'VM-name' cannot be restored: The guid
differs from the backup copy.



Explanation:

The specified target VM exists and has a different guid than the virtual
machine was backed up with..

System action:

The virtual machine is not restored.

User response:

Specify a different virtual machine as a restore target or delete the
specified target virtual machine.

------------------------------------------------------------------------
ANS2342E

The specified restore target 'VM-name' is ambiguous: Multiple virtual
machines with the same name exist.



Explanation:

The specifed restore target is ambiguous, multiple virtual machine with
the same name exist.

System action:

The virtual machine is not restored.

User response:

Specify a different virtual machine as a restore target.

------------------------------------------------------------------------
ANS2343E

A snapshot of Virtual machine 'vmname' cannot be taken because a
physical disk attached.



Explanation:

The Volume Snapshot Service (VSS) is unable to snapshot a virtual
machine with a physical disk.

System action:

The full backup of the the virtual machine finished with failures. The
next virtual machine in the backup will be processed.

User response:

Do not include this virtual machine in domain.vmfull for backup. A
snapshot of this virtual machine cannot be taken.

------------------------------------------------------------------------
ANS2344E

'drive-name1' is a disk witness.



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.

User response:

If the CLUSTERNODE option is incorrectly set to YES, then change the
option to NO and try the operation again. Otherwise see the client
manual for further information about configuring the IBM Spectrum
Protect client to run in a cluster environment.

------------------------------------------------------------------------
ANS2345W

The virtual machine named '' was found to have an old snapshot ''. A
command was sent to the vCenter to remove it.



Explanation:

During the snapshot clean-up process the backup-archive client found old
snapshots on the virtual machine. A remove snapshot command was sent to
the VMware vCenter to remove the old snapshots.

System action:

Processing continues

User response:

Confirm that the the virtual machine is free of all snapshots before the
next scheduled backup.

------------------------------------------------------------------------
ANS2346E

Expiration of VM object VMname failed. Reason:



Explanation:

The transaction which expires the named VM object failed at the server.
The reason code ....?????

System action:

The expiration is not completed.

User response:

Consult the error log for specific reasons for this failure.

------------------------------------------------------------------------
ANS2347E

IBM Spectrum Protect application protection cannot be used. The correct
Java Runtime Environment version has not been detected on machine. A
Java Runtime Environment version or higher is required to run this
program. If you have already installed this level of Java version on
this machine, please ensure that the correct Java executable is on your
PATH and start the program again.



Explanation:

IBM Spectrum Protect application protection vm backup cannot be started
because the Java runtime environment does not meet the requirements.

System action:

Processing stops.

User response:

Verify that the correct java executable is on your PATH or install the
required version of Java runtime environment and run the backup again.

------------------------------------------------------------------------
ANS2348E

Mount proxy host 'remoteversion' does not have a supported operating
system.



Explanation:

The mount proxy node needs to be configured on a supported operating
system.

System action:

The calling procedure returns and control is passed back the user.

User response:

Check the documentation for a list of supported operating systems.
Configure the mount proxy node on a supported operating system.

------------------------------------------------------------------------
ANS2349W

The virtual machine named '' was found to need snapshot consolidation. A
command was sent to the VMware vCenter to perform consolidation.



Explanation:

During the virtual machine backup process the backup-archive client
found the virtual machine needed snapshot consolidation. A command was
sent to the VMware vCenter to perform consolidation.

System action:

Processing continues

User response:

Confirm that the virtual machine is clean of all snapshots and snapshot
delta files before the next scheduled backup.

------------------------------------------------------------------------
ANS2350E

Virtual machine 'VM name' will not be backed up because it contains at
least one of the following unsupported special characters \ / : ; , * ?
" ' < > |



Explanation:

The specified virtual machine contains characters that are not supported
for virtual machine backup and restore operations.

System action:

The backup for the specified virtual machine fails.

User response:

Rename the virtual machine so that it does not contain any of the
specified special characters.

------------------------------------------------------------------------
ANS2351E

Duplicate virtual machine name 'vmname' was detected in the same backup
operation. Backups of a virtual machine can not continue without a
unique object name.



Explanation:

The backup of the virtual machine failed because no unique object name
is available.

System action:

The backup for the specified virtual machine fails. The next virtual
machine to back up will be processed.

User response:

Rename the virtual machine so that it is unique among virtual machines
for the node.

------------------------------------------------------------------------
ANS2352E

Validation of virtual machine 'vmname' configuration returned the
following message from Hyper-V: hypervmessage This message indicated
that the virtual machine could not be restored until the message from
Hyper-V is addressed.



Explanation:

When validating the virtual machine with Hyper-V a message was returned
that prevents the virtual machine restore from continuing.

System action:

Cannot continue with restore until the issue is resolved.

User response:

Resolve the issue outlined by the message.

------------------------------------------------------------------------
ANS2353W

The virtual machine to be restored 'vm-name' exceeds the amount of
vCPUs, virtual memory, or both, that are allowed by the host. The
virtual machine was reset to the minimum amount that is allowed by the
host so that the restore operation can continue.



Explanation:

The virtual machine to be restored is configured for more vCPUs, virtual
memory, or both, than are allowed by the host. The amount of vCPUs and
virtual memory can be adjusted after the restore operation completes.

System action:

The vCPUs, virtual memory, or both, are reset to the minimum amount that
are allowed by the host. The restore operation continues.

User response:

Adjust the amount of vCPUs, virtual memory, or both, after the restore
operation completes.

------------------------------------------------------------------------
ANS2373E

The VMware vCloud Suite plug-in library failed to connect to the
Platform Services Controller (PSC) and perform a single sign-on session.



Explanation:

A connection cannot be established with the Platform Services
Controller.

System action:

vCloud Suite API operations cannot be performed.

User response:

Verify that the value of the VMCHOST option is correct, that network
connectivity to the host exists, and that the Platform Services
Controller is running either embedded or external.To receive any
additional messages that might be related to this problem, enable
TRACEFLAGS VCLOUD tracing in the client options file. To determine which
Platform Services Controller the vCenter Server is referencing, examine
the vCenter Server's Advanced Settings key 'config.vpxd.sso.sts.uri'.
Confirm the system time between the PSC, vCenter and the client on the
data mover node are in sync. Also, check the vCloud Suite plug-in error
file vcsplugin.log.

------------------------------------------------------------------------
ANS2374E

The VMware vCloud Suite plug-in library failed to connect to the vCenter
Management Server.



Explanation:

A connection cannot be established with the vCenter Management Server.

System action:

vCloud Suite API operations cannot be performed.

User response:

Verify that the value of the VMCHOST option is correct, and that network
connectivity to the host exists. To receive any additional messages that
might be related to this problem, enable TRACEFLAGS VCLOUD tracing in
the client options file. Also, check the vCloud Suite plug-in log file
vcsplugin.log.

------------------------------------------------------------------------
ANS2375E

The VMware vCloud Suite plug-in library failed to connect to the vCenter
Management Server because the instance name could not be found.



Explanation:

A connection cannot be established with the vCenter Management Server
because the instance name could not be found. This could be a spelling
error in the host name or the Domain Name System (DNS) is not
functioning.

System action:

vCloud Suite API operations cannot be performed.

User response:

Verify that the value of the VMCHOST option is correct and matches the
name used to register the vCenter with the Platform Services Controller
often this is the fully qualified domain name (FQDN). To receive any
additional messages that might be related to this problem, enable
TRACEFLAGS VCLOUD tracing in the client options file.

------------------------------------------------------------------------
ANS2376I

The target vCenter version does not support VMware's vCloud Suite SDK so
tagging operations cannot be performed by the client on the data mover
node.



Explanation:

The client option 'VMTAGDATAMOVER' is enabled so that IBM Spectrum
Protect categories and tags can be applied to virtual machines, but the
vCenter version is below version 6.0.

System action:

The operation continues without the vCloud Suite plug-in library and
vSphere tagging support.

User response:

Use a vCenter that is at or above version 6.0 or disable the
'VMTAGDATAMOVER' option in the client options file.

------------------------------------------------------------------------
ANS2377I

The IBM category data has been created, or already existed, on the
VMware Platform Services Controller.



Explanation:

The categories used for tagging support in the backup-archive client are
available for use on the VMware Platform Services Controller.

System action:

The operation has completed.

User response:

None.

------------------------------------------------------------------------
ANS2378W

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



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.



System action:

The client on the data mover node will attempt a credential login as a
result of the single sign-on login failure.

User response:

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

------------------------------------------------------------------------
ANS2380E

Connection to the Windows Management Instrumentation (WMI) default
namespace failed with the error 'error'.



Explanation:

The Windows Management Instrumentation (WMI) default namespace
"root\cimv2" could not be found. Possibly because the WMI repository is
corrupted.

System action:

Processing stops.

User response:

Please verify that the WMI repository is consistent using the command
'winmgmt /verifyrepository'.

------------------------------------------------------------------------
ANS2398I

The virtual machine 'VM-name' is configured as a VMware Site Recovery
Manager placeholder virtual machine on the recovery site. As a result,
the virtual machine will be skipped.



Explanation:

VMware Site Recovery Manager creates placeholder virtual machines that
have no virtual disk data. As a result, these virtual machines cannot be
backed up.

System action:

The backup operation skips the placeholder virtual machine and continues
processing the remaining virtual machines.

User response:

None

------------------------------------------------------------------------
ANS2399I

The virtual machine is configured as a VMware Site Recovery Manager
placeholder virtual machine on the recovery site. As a result, the
virtual machine will be skipped.



Explanation:

VMware Site Recovery Manager creates placeholder virtual machines that
have no virtual disk data. As a result, these virtual machines cannot be
backed up.

System action:

The backup operation skips the placeholder virtual machine and continues
processing the remaining virtual machines.

User response:

None

------------------------------------------------------------------------
ANS2408I

The virtual machine named 'VMNAME' is ready for Instant Access



Explanation:

The Instant Access operation for the specified virtual machine
successfully completed.

System action:

None.

User response:

None

------------------------------------------------------------------------
ANS2409E

The Instant Restore type was not identified.



Explanation:

The client encountered a connection error when querying the IBM Spectrum
Protect server for Instant Restore and Access information.

System action:

Processing stops.

User response:

Verify that the client is connected to the server. Then run the
operation again. Check with the command QUERY SESSION what is the cause
for the connection issue. Also check the dsmerror.log for additional
information

------------------------------------------------------------------------
ANS2410E

Instant Restore information for the specified virtual machines was not
found.



Explanation:

The IBM Spectrum Protect server does not contain Instant Restore
information for the specified virtual machines. Or, the virtual machines
were specified incorrectly.

System action:

Processing stops.

User response:

Issue the QUERY VM * -VMRESTORETYPE=ALLTYPE command. This command
queries all active Instant Access, Restore, and Disk sessions available
on the IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS2411E

Instant Restore/Access of virtual machine 'vmname' failed with rc =
return-code



Explanation:

An error happened during processing of an Instant Restore or Access. See
previous output what happens exactly.

System action:

Processing stops.

User response:

Check the error log for information about how to resolve this error.

------------------------------------------------------------------------
ANS2412E

IBM Spectrum Protect Recovery Agent is not installed.



Explanation:

IBM Spectrum Protect Recovery Agent is not installed.

System action:

Processing stops.

User response:

Ensure that IBM Spectrum Protect Recovery Agent is correctly installed
and configured.

------------------------------------------------------------------------
ANS2413E

Cannot find the Recovery Agent shell command in the expected
installation path. Ensure that IBM Spectrum Protect for VE is correctly
installed and configured.



Explanation:

The Recovery Agent shell command was not found in the expected
installation path.

System action:

Processing stops.

User response:

Ensure that IBM Spectrum Protect for VE is correctly installed and
configured.

------------------------------------------------------------------------
ANS2414E

An error occurred when the hostname for the local machine was called.



Explanation:

The system call gethostname failed.

System action:

Processing stops.

User response:

Verify that the configuration of the network interface is correct.

------------------------------------------------------------------------
ANS2415E

An error occurred when the machine address information was called.



Explanation:

The system call getaddrinfo failed.

System action:

Processing stops.

User response:

Verify that the configuration of the network interface is correct.

------------------------------------------------------------------------
ANS2416E

An error occurred when the machine name information was called.



Explanation:

The system call getnameinfo failed.

System action:

Processing stops.

User response:

Verify that the configuration of the network interface is correct.

------------------------------------------------------------------------
ANS2417E

Unexpected communication method. Only TCP and TCPv6 are accepted.



Explanation:

An unexpected communication method was detected.

System action:

Processing stops.

User response:

Verify that the communication method for IBM Spectrum Protect is
correct. Use either TCP or TCPv6.

------------------------------------------------------------------------
ANS2418E

Unable to read or write to the local instant restore data. filename File
cannot be accessed or is damaged.



Explanation:

Instant access and instant restore operations require read/write access
on the local data mover to store data.

System action:

Processing stops.

User response:

To store the instant restore restore data, the data mover application
requires read and write access to the C:\Documents and
Settings\AllUsers\Application Data\Tivoli\TSM\ or
C:\ProgramData\Tivoli\TSM folder. Set the access rights to this
directory so that your user has the correct rights. If the file was
damaged it can be helpfull to replace the current version with the .bak
file.

------------------------------------------------------------------------
ANS2419E

The datastore does not have enough free space for the instant restore
operation.



Explanation:

The space on the selected datastore is not sufficient for the instant
restore operation.

System action:

Processing stops.

User response:

Increase the datastore space or choose a different datastore.

------------------------------------------------------------------------
ANS2420E

Cannot detect storage device information.



Explanation:

Storage device information cannot be retrieved.

System action:

Processing stops.

User response:

Ensure that the communication with the ESX host is working. Also, review
the log messages on the ESX host.

------------------------------------------------------------------------
ANS2421E

The iSCSI initiator cannot be detected on the hypervisor host.



Explanation:

The iSCSI initiator name of the hypervisor host cannot be detected.

System action:

Processing stops.

User response:

VMware: Review the log file on the ESX host to ensure that the
communication with it is working. Hyper-V: Ensure that the iSCSI
initiator service is running and working properly.

------------------------------------------------------------------------
ANS2422E

Cannot detect the iSCSI Host Bus Adapter.



Explanation:

The iSCSI adapter was not detected.

System action:

Processing stops.

User response:

Ensure that the communication with the ESX host is working. Also, review
the log messages on the ESX host.

------------------------------------------------------------------------
ANS2424E

Cannot find the ESX host 'ESXHOST' in the vCenter.



Explanation:

The specified ESX host cannot be found in the vCenter.

System action:

Processing stops.

User response:

Ensure that the specified ESX host is in the vCenter. Ensure that the
name of the ESX host is correct. Alternatively, specify another ESX
host.

------------------------------------------------------------------------
ANS2425E

Cannot connect to the ESX host 'ESXHOST'



Explanation:

A connection to the specified ESX host cannot be made

System action:

Processing stops.

User response:

Ensure that the specified ESX host is connected to the vCenter and the
network. Alternatively, specify another ESX host.

------------------------------------------------------------------------
ANS2426E

The ESX host 'ESXHOST' is not powered on.



Explanation:

The specified ESX host is not powered on.

System action:

Processing stops.

User response:

Turn on the power to the ESX host. Alternatively, specify another ESX
host.

------------------------------------------------------------------------
ANS2427E

The ESX host 'ESXHOST' is in maintenance mode.



Explanation:

The specified ESX host is in maintenance mode. A connection cannot be
made to this host.

System action:

Processing stops.

User response:

Change the ESX host back to normal mode and try again. Alternatively,
specify another ESX host.

------------------------------------------------------------------------
ANS2428E

The ESX host 'ESXHOST' is not connected.



Explanation:

The specified ESX host is not connected in the vCenter.

System action:

Processing stops.

User response:

Connect the ESX host in the vCenter and try again. Alternatively,
specify another ESX host.

------------------------------------------------------------------------
ANS2430E

Cannot find the datacenter 'DATACENTER'.



Explanation:

The specified Datacenter cannot be found in the vCenter.

System action:

Processing stops.

User response:

Ensure that the specified datacenter is in the vCenter. Alternatively,
specify another datacenter.

------------------------------------------------------------------------
ANS2431E

Cannot find the temporary datastore 'TEMPDATASTORE' on the ESX host
'ESXHOST'.



Explanation:

The specified temporary datastore cannot be found on the specified ESX
host.

System action:

Processing stops.

User response:

Ensure that the specified datastore is on the ESX host. Alternatively,
specify another datastore.

------------------------------------------------------------------------
ANS2432E

The temporary datastore 'TEMPDATASTORE' is the same as the target
datastore 'DATASTORE'.



Explanation:

The specified temporary datastore must be a different datastore than the
one where the machine is restored to. You must specify two different
datastores for Storage vMotion to work.

System action:

Processing stops.

User response:

Specify another datastore as a temporary datastore.

------------------------------------------------------------------------
ANS2433E

The '-vmtempdatastore' option must be specified for an instant restore
operation.



Explanation:

You must specify two different datastores for Storage vMotion to work.
Use the '-vmtempdatastore' option to specify a temporary datastore.

System action:

Processing stops.

User response:

Specify a temporary datastore.

------------------------------------------------------------------------
ANS2434E

The datastore 'DATASTORE' was not found on the host 'ESXHOST'.



Explanation:

The specified datastore cannot be found on the ESX host.

System action:

Processing stops.

User response:

Ensure that the specified datastore is on the ESX host. Alternatively,
specify another datastore.

------------------------------------------------------------------------
ANS2435E

IBM Spectrum Protect Recovery Agent detected the following failure while
attempting to mount a snapshot of VM 'VM' from disc='disk-label':
FBCxxxxE-error-message



Explanation:

The attempt to mount a VM disk as an iSCSI device failed.

System action:

The operation stops.

User response:

Check the Recovery Agent logs and the FBCxxxxE error message, resolve
the problem, and try the operation again.

------------------------------------------------------------------------
ANS2436E

IBM Spectrum Protect Recovery Agent detected the following failure while
trying to dismount a snapshot of VM 'VM' from target 'target':
FBCxxxxE-error-message



Explanation:

The snapshot for the specified VM could not be dismounted from the iSCSI
target.

System action:

The operation stops.

User response:

Check the Recovery Agent logs and the FBCxxxxE error message, resolve
the problem, and try the operation again.

------------------------------------------------------------------------
ANS2442W

The Linux mount proxy node information is not available.



Explanation:

The Windows mount proxy was unable to retrieve its partner Linux mount
proxy node information.

System action:

A connection to the Linux mount proxy is not established.

User response:

Ensure that the Linux mount proxy node is set up and the DSMCAD service
is running on the Linux mount proxy node. Then, try this operation
again.

------------------------------------------------------------------------
ANS2444E

Cannot find the datacenter for host 'ESXHOST'.



Explanation:

Unable to determine the datacenter where the ESX host is located.

System action:

The operation was stopped.

User response:

Check that the vCenter of the ESX host is in a datacenter and that the
user has the proper authority to access this information.

------------------------------------------------------------------------
ANS2445E

Virtual machine 'VM' is running. You cannot delete this VM.



Explanation:

You cannot delete a virtual machine that is running.

System action:

The operation was stopped.

User response:

Ensure that you have the proper authority to power off virtual machines,
then power off and delete the VM.

------------------------------------------------------------------------
ANS2447E

Failed to delete VM 'VM' from the ESX host.



Explanation:

You cannot delete the virtual machine form the ESX host.

System action:

The operation was stopped.

User response:

Ensure that you have the proper authority to delete virtual machines,
then delete the VM.

------------------------------------------------------------------------
ANS2448E

Mount command failed. Command wasCOMMAND Shell command returned:RESULT



Explanation:

The mount command was not successful.

System action:

The operation was stopped.

User response:

Determine the problem from the error details returned for the mount
command. Resolve the problem, then run the command again.

------------------------------------------------------------------------
ANS2452E

num_discovered iSCSI devices were discovered on the ESX host, while
num_mounted were expected.



Explanation:

After the ESX host bus adapter was scanned, the number of devices that
were discovered is different from the number of mounted devices.

System action:

The Instant Restore or Instant Access process is stopped.

User response:

Verify that the IBM Spectrum Protect mount is configured to use the
correct ESX host IP. To clean the environment, you must run the cleanup
process.

------------------------------------------------------------------------
ANS2453E

An error occurred when the host bus adapter was scanned.



Explanation:

An error occurred when the ESX host bus adapter was scanned.

System action:

The Instant Restore, Instant Access, or cleanup process is stopped.

User response:

Run the cleanup process after you fix any problems with the ESX host bus
adapter.

------------------------------------------------------------------------
ANS2454E

An error occurred when the iSCSI target target_name was disconnected
from the ESX host bus adapter.



Explanation:

An error occurred when a specific iSCSI target was disconnected from the
ESX host bus adapter.

System action:

The cleanup operation is stopped.

User response:

Run the cleanup process after you fix any problems with the ESX host bus
adapter.

------------------------------------------------------------------------
ANS2455I

The virtual machine has been started. You can use the machine after it
has booted, or you can connect to it and manage its settings through the
vCenter console.



Explanation:

The virtual machine is being started.

System action:

Processing continues.

User response:

While the boot is in progress, you can connect to the virtual machine
and view or manage BIOS settings, manage the bootloader options, or
perform other tasks. After the boot process completes, you can use the
virtual machine and its applications and resources.

------------------------------------------------------------------------
ANS2462E

Unable to start the vMotion task for virtual machine 'vm_name'.



Explanation:

An instant restore of the specified virtual machine was attempted but
failed. The client could not start a vMotion task to migrate the virtual
machine.

System action:

The Instant Restore operation stops.

User response:

Examine the client dsmerror.log file to see if a log entry indicates why
the vMotion task failed. Additional information about the failure might
also be available in the vCenter server, on the Task and Events tab for
the ESXi host that you were migrating the VM from. If possible, use the
log and event records to determine what caused the vMotion task to fail
and fix it. Then, clean up the virtual machine (use the Restore VM
command with the -VMRESToretype=VMCLeanup option) and restart the
vMotion task. If you cannot restart the task, suspend the virtual
machine and use the vSphere web client to start the virtual machine
migration from one host to another.

------------------------------------------------------------------------
ANS2463W

Instant Restore information cannot be saved on the server.



Explanation:

An error occurred when Instant Restore information was being saved on
the server. The Instant Restore process is still running.

System action:

The operation continues.

User response:

The client dsmerror.log file might contain information to help
troubleshoot the reason for this error. Let the Instant Restore process
complete on its own. You might need to run a clean up operation on the
virtual machine. Use the Restore VM command, and specify the
-VMRESToretype=VMCLeanup option.

------------------------------------------------------------------------
ANS2464E

Unable to delete Instant Restore information from the server.



Explanation:

An error occurred while attempting to delete Instant Restore information
from the server.

System action:

The Instant Restore operation continues.

User response:

The most likely reason for this error is that an ANS2463W warning
previously occurred, and there is no data to delete. If you have not
previously seen an ANS2463W message, the client dsmerror.log file might
contain information to help you troubleshoot this error. Clean up the
virtual machine to remove old information from the server. Use the
Restore VM command, and specify the -VMRESToretype=VMCLeanup option.

------------------------------------------------------------------------
ANS2465E

An error occurred during a storage vMotion operation.



Explanation:

A storage vMotion task failed while trying to migrate a running virtual
machine.

System action:

The Instant Restore operation stops.

User response:

Examine the client dsmerror.log file to see if a log entry indicates why
the vMotion task failed. Additional information about the failure might
also be available in the vCenter server, on the Task and Events tab for
the ESXi host that you were migrating the VM from. If possible, use the
log and event records to determine what caused the vMotion task to fail
and fix it. Then clean up the virtual machine (use the Restore VM
command with the -VMRESToretype=VMCLeanup option) and restart the
vMotion task. If you cannot restart the task, suspend the virtual
machine and use the vSphere web client to start the VM migration from
one host to another.

------------------------------------------------------------------------
ANS2466W

If you continue you will lose all data created on this virtual machine.
The virtual machine will also be removed from the ESXi host. Are you
sure that you want to do this? Press Y the virtual machine data and
remove it from the ESXi host. Press any other key to continue without
deleting data or the VM.



Explanation:

You are performing an operation that, if allowed to continue, will
delete all data that was created after this virtual machine was created.

System action:

If Y is pressed, the Instant Restore operation is stopped, and a cleanup
operation is performed

User response:

Respond to the prompt. Press Y to destroy all data and delete the
virtual machine from the server. Press any other key to continue without
deleting.

------------------------------------------------------------------------
ANS2467W

Unable to delete the snapshot that was created for the virtual machine
named 'vm_name'



Explanation:

When a virtual machine is restored by an instant restore operation, a
snapshot is created to store all data that were written to the virtual
machine disks. When the restore is completed, the ESXi host deletes the
snapshot. The snapshot for the specified virtual machine could not be
deleted.

System action:

Operation continues.

User response:

Examine the vSphere log to determine why is it not possible to delete
the snapshot and resolve the problems that prevent the deletion. Then,
delete the snapshot by using the snapshot manager.

------------------------------------------------------------------------
ANS2468E

The necessary iSCSI targets could not be found on the ESX host.



Explanation:

An instant restore operation was initiated and one or more of the
required iSCSI targets could not be found on the ESXi host.

System action:

Processing stops.

User response:

Verify that the IP address that was specified with the
-VMISCSISERVERADDRESS parameter is correct.

------------------------------------------------------------------------
ANS2469E

Unable to remove the iSCSI target.



Explanation:

An error occurred while trying to remove an iSCSI target.

System action:

Processing stops.

User response:

Check vSphere client log file for the reason this operation failed and
remove the iSCSI target. To remove the failed iSCSI static targets go to
your ESXi host Configuration -> Storage Adapters -> Select the iSCSI
Adapter -> right click on it -> Click Properties -> Static Discovery and
select the failed iSCSI targets and remove them.

------------------------------------------------------------------------
ANS2471E

Unable to stop the vMotion Task 'task'.



Explanation:

The specified vMotion task could not be stopped.

System action:

The instant restore operation is stopped.

User response:

Examine the vSphere log to determine why the migration cannot be
stopped. Resolve the problem and cancel the vMotion task. Then, use the
-VMRESToretype=VMFULLCleanup option on the Restore VM command to remove
any files or other resources that were created by the instant restore
operation.

------------------------------------------------------------------------
ANS2472E

Cannot detect the LUN for the attached RDM devices for virtual machine
named vmname'. The restore operation for this virtual machine cannot be
completed.



Explanation:

The LUNs for the RDM devices use by the specified virtual machine are
either missing, are mapped to an other machine, or the device name and
the LUN do not match.

System action:

The restore operation is stopped.

User response:

For restore operations where vmrestoretype=instantrestore or
vmrestoretype=instantaccess, verify that the iSCSI server address and
the VMkernel port binding match. Verify this information by checking the
following things: 1. Check the Data Protection for VMware configuration
file RecoveryAgent.conf and verify that the iSCSI server address is
bound to the correct network card and segment. 2. Use the vSphere client
to connect to your ESXi host. In vSphere, select Configuration->Storage
Adapters to display a list of the iSCSI adapters. Right click the
adapter that you are verifying. Then, select Properties ->Network
Configuration. In the VMkernel Port Bindings Details output, verify that
the VMkernel Adapter is on the same subnet that the datamover node is
on.

------------------------------------------------------------------------
ANS2473E

Unable to create a Snapshot of the virtual machine named 'vm_name'.



Explanation:

An instant restore operation was attempted for the specified virtual
machine. The snapshot that is used to restore the virtual machine could
not be created.

System action:

The instant restore operation stops.

User response:

Examine the vCenter logs to determine why the snapshot could not be
created and try the instant restore operation again.

------------------------------------------------------------------------
ANS2474E

Unable to cleanup after an instant restore operation for the virtual
machine named 'vm_name', because vMotion task is still running.



Explanation:

An instant restore operation is still running for the specified virtual
machine.

System action:

The cleanuop operation stops.

User response:

Use the query command to check on the status of the instant restore
operation. Examine the vCenter to determine the status of the vMotion
task. If you want to stop the instant restore, cancel the operation in
the DP VMware GUI or stop the vMotion task from the vCenter interface.
Then, start the cleanup operation again.

------------------------------------------------------------------------
ANS2476E

A restore location must be specified via the TARGETPATH option when
restoring to a different virtual machine name.



Explanation:

A restore location must be specifed via the TARGETPATH option when
restoring to a different virtual machine name specified by the VMNAME
option.

System action:

The virtual machine is not restored.

User response:

Specify a restore location with the TARGETPATH option.

------------------------------------------------------------------------
ANS2484I

Virtual Machine 'vm_name' was successfully restored



Explanation:

The Virtual Machine was successfully restored.

System action:

None.

User response:

None

------------------------------------------------------------------------
ANS2485E

Cannot query the IBM Spectrum Protect server to get instant access
information



Explanation:

The server did not respond to the query for instant access information.

System action:

The virtual machine cleanup operation is halted.

User response:

Examine the dsmerror.log file and the IBM Spectrum Protect server
activity logs to determine the cause of this error.

------------------------------------------------------------------------
ANS2488E

Error mounting the iSCSI device.



Explanation:

An error occurred while trying to mount the iSCSI device. Check the
dsmerror.log file to determine the cause of this error.

System action:

The operation was stopped.

User response:

No action is required.

------------------------------------------------------------------------
ANS2490E

The VM 'VM' cannot be powered off.



Explanation:

The specified virtual machine cannot be powered off. Attempts to clean
up the resources that were created to restore the virtual machine cannot
be completed.

System action:

The restore operation was stopped.

User response:

Turn off the virtual machine by using your hypervisor management client.

------------------------------------------------------------------------
ANS2513I

The virtual machine has no disks attached



Explanation:

The virtual machine exists, but it does not have any disks attached. The
machine can be cleaned up.

System action:

None.

User response:

None

------------------------------------------------------------------------
ANS2514I

Disk status cannot be determined



Explanation:

It is not possible to determine the status of this disk.

System action:

None.

User response:

Examine the vSphere Client log to determine what is wrong with the
machine. If the log entries do not reveal problems with this virtual
machine, inspect the virtual machine in the vSphere Client to determine
why the disk status cannot be determined. See the vSphere documentation
for additional guidance, if necessary.

------------------------------------------------------------------------
ANS2515I

No additional information is available for this virtual machine. The
virtual machine was deleted or it has been renamed



Explanation:

Information about the virtual machine cannot be found on the ESXi host.
The virtual machine might have been previously deleted or renamed.

System action:

None.

User response:

Use the vSphere Client to determine what happened to this virtual
machine. If the virtual machine was renamed, make sure that it is
running without errors before you clean up the temporary resources, by
using the Restore VM command with the -VMRESToretype=VMCLEANUP option.

------------------------------------------------------------------------
ANS2516E

VMware storage vMotion operation failed. Restart the storage vMotion
operation manually, by using the vSphere web client, to finish the
restore operation. Refer to the documentation to get details about the
manual recovery process.



Explanation:

IBM Spectrum Protect Changes to the restored VM might not be permanently
saved.

System action:

IBM Spectrum Protect Automatic cleanup cannot be performed for the
failed vMotion operation.

User response:

Examine the event logs to determine the cause for the failure. Fix any
problems and restart the storage vMotion operation manually, by using
the vSphere web clien, to finish the restore operation. Refer to the
vMotion documentation to get details about the manual recovery process.

------------------------------------------------------------------------
ANS2517E

Cannot query the IBM Spectrum Protect server to get instant restore
information



Explanation:

The server did not respond to the query for instant restore information.

System action:

The virtual machine clean up operation stops.

User response:

Examine the dsmerror.log file and the IBM Spectrum Protect server
activity logs to determine the cause of this error.

------------------------------------------------------------------------
ANS2519E

The disk \"diskname\" is an iSCSI device with an inactive path. Powering
off the virtual machine will cause the ESXi server to hang. The clean up
operation has been stopped to prevent this. Use the Query VM command
with the -detail option to obtain detailed status information about the
virtual machine. Correct the path so that the iSCSI state is active and
then try running the VMFULLCleanup operation again.



Explanation:

A running virtual machine that has an inactive iSCSI device cannot be
cleaned up.

System action:

The virtual machine full clean up (VMRESTORType=VMFULLCLeanup) operation
stops.

User response:

For information about troubleshooting inactive iSCSI resources, search
the VMware support pages by using a search string like "troubleshooting
iSCSI" or "inactive iSCSI".

------------------------------------------------------------------------
ANS2520E

The disk \"diskname\" is not a physical device. An instant restore clean
up was stopped because vMotion could not restore all virtual machine
data.. Use the Query VM command with the -detail option to obtain
information about state of the specified disk. Use vMotion to manually
migrate the virtual machine devices and then try the clean up operation
again.



Explanation:

An instant restore clean up operation (-VMRESToretype=VMCLeanup) cannot
complete because vMotion could not restore all of the virtual machine
resources.

System action:

The virtual machine clean up operation stops.

User response:

Use the VMware documentation to determine how to use vMotion to migrate
the virtual machine. Then, try the clean up operation again by using the
Restore VM command with the -VMRESToretype=VMCLeanup option. If you do
not want to restore this virtual machine, use the Restore VM command
with the -VMRESTORType=VMFULLCLeanup option to remove the virtual
machine and all of its resources.

------------------------------------------------------------------------
ANS2521E

Instant restore operations require valid licenses for both vMotion and
storage vMothion.



Explanation:

Instant restore works only when the ESXi host has a valid license for
both vMotion and storage vMotion

System action:

The instant restore operation is stopped.

User response:

Obtain the necessary license from VMware and assign the license to the
ESXi host.

------------------------------------------------------------------------
ANS2522W

A user canceled the 'operationType' operation .



Explanation:

A user canceled the restore/backup operation .

System action:

The operation is stopped

User response:

No response is required.

------------------------------------------------------------------------
ANS2523E

The virtual machine named vm cannot not be restored to the same
configuration it had when it was backed up. IBM Spectrum Protect will
reconfigure the virtual machine to include only the most essential
configuration information and retry the restore operation.



Explanation:

The restore operation failed to restore the virtual machine to its
original configuration. This error can occur if there is incompatibility
between the hardware that the virtual machine was on when it was backed
up, and the hardware on the physical host where it was restored. IBM
Spectrum Protect will reconfigure the virtual machine to eliminate all
but most necessary configuration information (video and virtual disks)
and retry the restore operation.

System action:

The restore operation continues, using the reconfigured virtual machine
information.

User response:

When the restore completes, reconfigure the restored virtual machine to
your requirements.

------------------------------------------------------------------------
ANS2524E

An attempt to mount a snapshot of VM 'disk' from disk 'vm' failed. The
volume might be mounted from another operation and cannot be remounted.



Explanation:

An attempt to mount a snapshot of VM 'disk' from disk 'vm' failed. The
volume might be mounted from another operation and cannot be remounted..

System action:

The mount operation stops.

User response:

Dismount the volume by running a mount cleanup operation, then run the
mount operation again.

------------------------------------------------------------------------
ANS2525E

The created virtual machine cannot be powered on.



Explanation:

The hypervisor is unable to power on the created virtual machine.

System action:

The operation will be rolled back and stopped.

User response:

Check the dsmerror.log file for more information. Check the hypervisor
log to determine what error occurred during the power-on process of the
virtual machine.

------------------------------------------------------------------------
ANS2526W

The VM_DONT_QUIESCE_ON_SNAPSHOT testflag is deprecated for full VM
backups. Use the INCLUDE.VMSNAPSHOTATTEMPTS option to attempt snapshots
with "VMware Tools file system quiescing and application (VSS) quiescing
disabled".



Explanation:

The VM_DONT_QUIESCE_ON_SNAPSHOT testflag overrides the
INCLUDE.VMSNAPSHOTATTEMPTS option. As a result, all snapshot attempts
are with VMware Tools file system quiescing and application (VSS)
quiescing disabled.

System action:

Use the INCLUDE.VMSNAPSHOTATTEMPTS option to specify snapshot attempts
with VMware Tools file system quiescing and application (VSS) quiescing
disabled.

User response:

See the INCLUDE.VMSNAPSHOTATTEMPTS documentation for information about
how to set this option.

------------------------------------------------------------------------
ANS2527I

The login request started.



Explanation:

The user submitted a request to log in to the file restore interface.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2528I

The login request was completed successfully. VM-OS=os
Data-Center=datacenter



Explanation:

The user successfully logged into the file restore interface.

System action:

None.

User response:

No action is required.

------------------------------------------------------------------------
ANS2529I

The login request failed.



Explanation:

An error occurred while logging into the file restore interface.

System action:

None.

User response:

Review the log for related login and authentication errors.

------------------------------------------------------------------------
ANS2530I

The log out request started.



Explanation:

The user either logged out of the file restore interface or the file
restore interface timed out due to inactivity.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2531I

The log out request was completed successfully.



Explanation:

The user was successfully logged out of the file restore interface.

System action:

None.

User response:

No action is required.

------------------------------------------------------------------------
ANS2532I

The log out request failed.



Explanation:

An error occurred while logging out of the file restore interface.

System action:

Log out processing was completed with errors.

User response:

Review the log for related log out errors.

------------------------------------------------------------------------
ANS2533I

The mount request started. Backup-ID=backupId



Explanation:

The user selected a backup to load.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2534I

The mount request was completed successfully. Backup-Date=backupDate
Mount-ID=mountId



Explanation:

The backup was successfully mounted.

System action:

None.

User response:

No action is required.

------------------------------------------------------------------------
ANS2535I

The mount request failed. Backup-Date=backupDate Mount-ID=mountId



Explanation:

An error occurred while mounting the backup.

System action:

Mount processing stops.

User response:

Review the log for related mount errors.

------------------------------------------------------------------------
ANS2536I

The dismount request started. Backup-ID=backupId Backup-Date=backupDate
Mount-ID=mountId



Explanation:

The user either selected another backup to load or logged out of the
file restore interface.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2537I

The dismount request was completed successfully. Backup-ID=backupId
Backup-Date=backupDate Mount-ID=mountId



Explanation:

The backup was successfully dismounted.

System action:

None.

User response:

No action is required.

------------------------------------------------------------------------
ANS2538I

The dismount request failed. Backup-ID=backupId Backup-Date=backupDate
Mount-ID=mountId



Explanation:

An error occurred while dismounting the backup.

System action:

Dismount processing stops.

User response:

Review the log for related dismount errors.

------------------------------------------------------------------------
ANS2539I

The restore request started. Selection-Size=selectionSize
Alt-Destination=altDestination



Explanation:

The user submitted a request to restore files, directories, or both from
a backup.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2540I

The restore request was completed successfully.



Explanation:

The restore request was successfully submitted.

System action:

None.

User response:

No action is required.

------------------------------------------------------------------------
ANS2541I

The restore request failed.



Explanation:

An error occurred during the restore request.

System action:

Restore processing stops.

User response:

Review the log for related restore errors.

------------------------------------------------------------------------
ANS2542I

The final restore processing statistics are available. Total
Objects=totalObjects Total Restored=totalRestored Total
Failed=totalFailed Total Bytes=totalBytes Completion Code=completionCode



Explanation:

The restore processing statistics contain completion codes that indicate
the state of the restore operation.

*  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.



System action:

None.

User response:

If the completion code is not 0, review the logs for related restore
errors.

------------------------------------------------------------------------
ANS2543E

A status of 'state' is returned because the Microsoft iSCSI Initiator
Service is not running.



Explanation:

The Microsoft iSCSI Initiator Service is not running.

System action:

Operation cannot continue.

User response:

Start the Microsoft iSCSI Initiator Service.

------------------------------------------------------------------------
ANS2544E

A status of 'state' is returned because the Microsoft iSCSI Initiator
Service is not installed.



Explanation:

The Microsoft iSCSI Initiator Service is not installed.

System action:

Operation cannot continue.

User response:

Install the Server Role 'File and iSCSI Services'

------------------------------------------------------------------------
ANS2545I

A crash consistent snapshot is created for the backup of virtual machine
'VM name'.



Explanation:

A crash consistent snapshot is created for the backup of the virtual
machine.

System action:

The virtual machine backup continues.

User response:

If an application consistent backup was requested but failed, check the
dsmerror.log file and the Hyper-V event logs for the reason for the
failure.

------------------------------------------------------------------------
ANS2546W

An incorrect disk location label 'location label' is specified with
option 'option name'



Explanation:

The disk location label must begin with 'SCSI' or 'IDE' followed by the
controller number and device location number.

System action:

The specified disk location label is ignored.

User response:

Verify that the disk location label is correctly specified. Check the
disk location label format. Ensure that the label begins with 'SCSI' or
'IDE', and is followed by the controller number and device location
number, which are expressed as digital numbers. For example, 'SCSI 0 0'
or 'IDE 0 1'.

------------------------------------------------------------------------
ANS2547E

The Hyper-V role is not installed on the specified Windows server host
'host'.



Explanation:

Hyper-V is a feature of the Windows server that needs to be explicitly
enabled by installing the Hyper-V role.

System action:

Processing stops.

User response:

Install the Hyper-V role on the Windows server host. Alternatively,
specify another Hyper-V host.

------------------------------------------------------------------------
ANS2548E

The status query for Hyper-V on the host 'host' failed due to lack of
privileges.



Explanation:

The User ID running this command does not have the necessary privileges
to access Hyper-V information on the host.

System action:

Processing stops.

User response:

Ensure that the current User ID is granted the necessary privileges.
Alternatively, try another user or specify another host.

------------------------------------------------------------------------
ANS2549E

The connection to Hyper-V on host 'host' failed with rc= rc.



Explanation:

The connection to the Hyper-V host failed with a system specific error.

System action:

Processing stops.

User response:

Ensure that the network is configured correctly. Ensure that the Hyper-V
host is connected to the network, is configured correctly, and is
powered on.

------------------------------------------------------------------------
ANS2550W

The virtual machine backup operation will skip physical (pass-through)
disk 'drive name' on drive number 'drive number'



Explanation:

Physical disks cannot be backed up during virtual machine backup
operations using Resilient Change Tracking (RCT).

System action:

The virtual machine backup operation continues without backing up the
physical disks.

User response:

Identify the physical disks and back them up by using another method.

------------------------------------------------------------------------
ANS2551W

Cannot remove recovery checkpoint for virtual machine 'VM-name'.



Explanation:

IBM Spectrum Protect cannot remove the recovery checkpoint that was
created during backup.

System action:

The virtual machine backup continues.

User response:

Remove the recovery checkpoint manually after backup.

------------------------------------------------------------------------
ANS2552E

Backup of a virtual machine that has a shared virtual hard disk is not
supported.



Explanation:

IBM Spectrum Protect does not support backup of a virtual machine that
has a shared virtual hard disk.

System action:

The backup will not occur.

User response:

Use alternative backup method, such as in-guest backup.

------------------------------------------------------------------------
ANS2553W

Resilient Change Tracking (RCT) has been turned off for disk 'drive
name'. Instead of an incremental backup, a full backup is run on this
disk.



Explanation:

RCT has been turned off for the disk. If disk RCT is disabled, no
changes will be tracked after it is disabled, and existing change
tracking data will be lost. Therefore, an incremental backup cannot run.

System action:

Instead of an incremental backup, a full backup will run for this disk.
RCT will be turned on automatically for this disk during the backup.

User response:

No action is required.

------------------------------------------------------------------------
ANS2554W

No previous backups are found for disk 'drive name'. Instead of an
incremental backup, a full backup is run for this disk.



Explanation:

No backups are found for the disk on the IBM Spectrum Protect server.
Therefore, an incremental backup cannot run.

System action:

Instead of an incremental backup, a full backup will run for this disk.

User response:

No action is required.

------------------------------------------------------------------------
ANS2555W

The incremental backup operation was changed to a full backup for
virtual machine 'vmname' because no previous backups are found on the
IBM Spectrum Protect server.



Explanation:

No backups are found for the VM on the IBM Spectrum Protect server, so
an incremental backup cannot be run. A full backup will be run instead.

System action:

A full backup operation will proceed for the VM.

User response:

No user action is required.

------------------------------------------------------------------------
ANS2556E

The cluster operating system is in the process of a rolling upgrade and
working in mixed-OS mode. Virtual machine 'vm_name' cannot be backed up
until the upgrade completes.



Explanation:

The cluster operation system is using rolling upgrade, including working
in mixed-OS mode. The backup cannot run during this upgrade operation.

System action:

The rolling upgrade continues, but the virtual machine is not backed up.

User response:

Wait for the rolling upgrade to complete, then start the virtual machine
backup again.

------------------------------------------------------------------------
ANS2557E

The virtual machine 'VM-name' contains one or more physical
(pass-through) disks. Backups are not supported in this configuration.
Specify the 'vmprocessvmwithphysdisks=yes' option to exclude these disks
from the backup.



Explanation:

Physical disks are not included in Resilient Change Tracking (RCT)
backup operations so they cannot be backed up by the IBM Spectrum
Protect client.

System action:

The virtual machine is not backed up.

User response:

Turn off the virtual machine and change the physical disks to virtual
mode or remove them from the virtual machine. Alternatively, specify the
'vmprocessvmwithphysdisks=yes' option to exclude these disks from backup
operations.

------------------------------------------------------------------------
ANS2558E

The virtual machine 'VM-name' contains one or more physical
(pass-through) disks. However, these physical disks are not all
available during the restore operation and the restore failed. Specify
the 'vmskipphysdisks=yes' option to exclude these disks from the
restore.



Explanation:

Physical disks are not all available during restore operations so the
IBM Spectrum Protect client does not restore the virtual machine
successfully.

System action:

The restore operation failed.

User response:

Check the physical disks and make sure that they are available.
Alternatively, specify the 'vmskipphysdisks=yes' option to exclude these
disks from restore operations.

------------------------------------------------------------------------
ANS2559E

The remote attach operation failed.



Explanation:

An error occurred while trying to attach the IBM Spectrum Protect
virtual volume snapshot to the mount proxy. The restore operation cannot
continue.

System action:

Processing stops.

User response:

Check the mount proxy dsmerror.log file for information about how to
resolve this issue.

------------------------------------------------------------------------
ANS2560W

The remote detach operation failed.



Explanation:

An error occurred while trying to detach the IBM Spectrum Protect
virtual volume snapshot from the mount proxy virtual machine. The
restore operation will continue.

System action:

Processing continues.

User response:

Check the mount proxy dsmerror.log file for information about how to
resolve this issue and manually remove resources that remain after the
failed detach operation.

------------------------------------------------------------------------
ANS2561I

The snapshot for virtual machine 'vmname' failed due to a temporary
condition. The snapshot will be retried.



Explanation:

The snapshot for the virtual machine failed due to a temporary
condition. The snapshot will automatically be retried.

System action:

Processing continues to the next virtual machine.

User response:

No action is required.

------------------------------------------------------------------------
ANS2563I

Starting retry snapshot number retryCount for virtual machine 'vmname'.



Explanation:

The previous snapshot of the virtual machine finished with an error.
Another snapshot for of the virtual machine will be attempted.

System action:

Another snapshot attempt of the virtual machine is started.

User response:

No action is required.

------------------------------------------------------------------------
ANS2564I

Gathering virtual machine information...



Explanation:

The client is beginning the process of gathering information about the
virtual machines to be processed. This length of time needed depends
upon the number of virtual machines in the backup.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2565I

Creating virtual machine snapshot...



Explanation:

The client is beginning the process of creating a snapshot for the
virtual machines in the backup. This length of time needed depends upon
the number of virtual machines in the backup.

System action:

Processing continues.

User response:

No action required.

------------------------------------------------------------------------
ANS2566E

The snapshot of virtual machine 'vmname' failed after the maximum number
of retries (retryCount) was reached.



Explanation:

Several attempts to take a snapshot failed. Because the maximum number
of retries was reached, the operation will not be retried.

System action:

The snapshot of the virtual machine finished with an error. Processing
continues to the next virtual machine..

User response:

Check the Windows event log for the reason for the failure. Resolve the
problem, and run the backup operation again.

------------------------------------------------------------------------
ANS2567E

The backup of vm-name failed because another backup is currently in
progress on the Hyper-V manager host machine.



Explanation:

There is a concurrent backup going on the Hyper-V manager host machine.

System action:

The backup operation stops.

User response:

Try the backup operation again after the current backup ends.
Alternatively, if no other backups are in progress, there might be a
recovery checkpoint created by a previous failed backup. In that case,
remove the checkpoint with the Remove-VMCheckPoint cmdlet, and try the
backup operation again.

------------------------------------------------------------------------
ANS2568I

The backup request for VM 'vmName' started.



Explanation:

The user submitted a request to back up a VM.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2569I

The backup request was completed successfully.



Explanation:

The backup request was successfully submitted.

System action:

None.

User response:

No action is required.

------------------------------------------------------------------------
ANS2570I

The backup request failed.



Explanation:

An error occurred during the backup request.

System action:

Backup processing stops.

User response:

Review the log for related backup errors.

------------------------------------------------------------------------
ANS2572I

The restore request started for vm 'VmName'.



Explanation:

The user submitted a request to restore vm.

System action:

Processing continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2573I

The maximum number of restore sessions specified by the
VMMAXRESTORESESSIONS option may not be sufficient for the restore
operation. Each virtual machine restored in parallel must be allocated
at least one session per disk restored in parallel.



Explanation:

The value of the VMMAXRESTORESESSIONS option must be at least the value
of the VMRESTOREMAXPARALLELVMS option multiplied by the value of the
VMMAXRESTOREPARALLELDISKS option. This ensures that at least one session
may be allocated for each disk being restored.

System action:

The maximum number of sessions available to the restore operations is
set to the value of the VMMAXRESTOREPARALLELDISKS option multiploed by
the VMMAXRESTOREPARALLELVMS option. Orocessing continues.

User response:

None.

------------------------------------------------------------------------
ANS2574I

The maximum number of sessions available to the restore operation has
been adjusted to adjusted_value. At least one session must be allocated
for each disk being restored.



Explanation:

The value of the VMMAXRESTORESESSIONS option is less than value of the
VMMAXRESTOREPARALLELVMS option multiplied by the value of the
VMMAXRESTOREPARALLELDISKS option. This may not be sufficient for the
restore operation.

The value of VMMAXRESTORESESSIONS is adjusted so that each virtual
machine restored in parallel has at least one available session per disk
restored in parallel.

System action:

Maximum session value has been adjusted.

User response:

None.

------------------------------------------------------------------------
ANS2575I

The process to collect the system logs is started in background.
Depending on the size of the log files, this might take some time to
complete. As soon as this process is complete, you will be prompted by
your browser to download the following file: file name



Explanation:

The user requested system log files for problem determination. The logs
will be collected and provided for download.

System action:

The logs are collected and the download will start soon.

User response:

Wait for the download to complete. Locate the file where the browser
stores downloaded files.

------------------------------------------------------------------------
ANS2576I

The process to collect the system logs is still running in background.
Depending on the size of the log files, this might take some time to
complete. As soon as this process is complete, you will be prompted by
your browser to download the following file: file name



Explanation:

The user has already requested system log files for problem
determination, but the process to collect the system logs is still
running. The logs will be provided for download once ready.

System action:

The download of system logs will start soon.

User response:

Wait for the download to complete. Locate the file where the browser
stores downloaded files.

------------------------------------------------------------------------
ANS2577I

The download of system logs is currently disabled. You can ask the
system administrator to enable it by setting the option 'option name and
value' in the 'configuration file name' configuration file. Please note
that you have to sign in again for the option to take effect.



Explanation:

The download of system logs is disabled.

System action:

The request has been canceled.

User response:

In order to download the logs files the system administrator needs to
enable the option by editing the FR API configuration file specified in
the message text. User need to sign out and sign in again for the option
to take effect. A restart of the Liberty server is not required.

------------------------------------------------------------------------
ANS2580E

The query for Hyper-V information on host 'host' failed with rc= rc.



Explanation:

The query for Hyper-V status information failed with a system specific
error.

System action:

Processing stops.

User response:

Verify the health and configuration of the specified host.

------------------------------------------------------------------------
ANS2581E

The Hyper-V host is reporting issues that prevent it from proceeding
with the operation.



Explanation:

Issues have been detected on the specified Hyper-V host. The system
cannot support the intended operation.

System action:

Processing stops.

User response:

Verify that the installation and configuration of the Hyper-V host
system is correct. Check the dsmerror.log file for additional
information, and contact the IBM Spectrum Protect administrator with the
information in the messages that have been sent.

------------------------------------------------------------------------
ANS2582E

The Hyper-V host 'host' is faulty: EnabledState = EnabledState
(expected: 2), HealthState = HealthState (expected: 5),
OperationalStatus = OperationalStatus (expected: 2).



Explanation:

A faulty state has been detected for the specified Hyper-V host.

System action:

Processing stops.

User response:

Verify the health and configuration of the specified host.

------------------------------------------------------------------------
ANS2583E

The restore target path 'state' does not have enough free space for the
restore operation.



Explanation:

The space on the selected restore target path is not sufficient for the
restore operation.

System action:

Processing stops.

User response:

Increase the free space to at least 50 MB in the restore target path, or
choose a different path.

------------------------------------------------------------------------
ANS2584E

The restore target path 'state' could not be found, or the path has not
been created.



Explanation:

The selected restore target path could not be found, or the path could
not be created.

System action:

Processing stops.

User response:

Create the restore target path manually or choose a different path.

------------------------------------------------------------------------
ANS2585E

num_discovered iSCSI devices were discovered on the Hyper-V host
Microsoft iSCSI Initiator, while num_mounted were expected.



Explanation:

The logged in iSCSI targets in the Microsoft iSCSI Initiator do not
match the amount of expected logged in iSCSI targets.

System action:

Operation cannot continue.

User response:

Verify that the IBM Spectrum Protect mount is configured to use the
correct Hyper-V host IP. To clean the environment, you must run the
cleanup process.

------------------------------------------------------------------------
ANS2586E

The application consistent snapshot of virtual machine 'vmname' failed
because the volume shadow copy requestor integration service is not
enabled on the guest virtual machine.



Explanation:

The volume shadow copy requestor integration service must be enabled on
the guest virtual machine in order to take application consistent
snapshots.

System action:

The snapshot of the virtual machine finished with an error. Processing
continues to the next virtual machine.

User response:

Contact the Hyper-V administrator to turn on the volume shadow copy
requestor integration service of the Hyper-V virtual machine. When the
service is enabled, run the VM backup operation again.

------------------------------------------------------------------------
ANS2587E

The application consistent snapshot of virtual machine 'vmname' failed,
possibly because the volume shadow copy requestor integration service is
not installed or is not running on the guest virtual machine.



Explanation:

The volume shadow copy requestor integration service must be installed
and enabled on the guest virtual machine in order to take an application
consistent snapshot.

System action:

The snapshot of the virtual machine finished with an error. Processing
continues to the next virtual machine.

User response:

Contact the Hyper-V administrator to install and configure the volume
shadow copy requestor integration service on the Hyper-V virtual
machine. When the service is installed and enabled, run the VM backup
operation again. Alternatively, perform a crash consistent snapshot of
the virtual machine.

------------------------------------------------------------------------
ANS2600S

Browser trying to establish connection to client; received socket
exception: exception-name



Explanation:

The browser received the exception when trying to connect to the IBM
Spectrum Protect client computer.

System action:

The operation ends.

User response:

Validate that the LAN is up and that you are trying to connect to the
correct port number.

Check the error logs for any additional information: dsmerror.log,
dsmwebcl.log, or dsmj.log. The default location of these logs is the
installation directory of the backup-archive client.

Ensure that the command line client runs without problems. Test the
command line client with a command like "dsmc q sess".

------------------------------------------------------------------------
ANS2601S

The browser tried to connect to the client and received unknown host
exception: exception-name



Explanation:

The browser received the exception when trying to connect to the IBM
Spectrum Protect client machine.

System action:

The operation ends.

User response:

Try the operation again. If it persists, determine what might be causing
this kind of problem. For example, determine if your LAN went down, or
verify if you are trying to connect to the correct IBM Spectrum Protect
client machine.

------------------------------------------------------------------------
ANS2602S

The browser tried to connect to the client and received I/O exception:
exception-name



Explanation:

The browser received the exception when trying to connect to the IBM
Spectrum Protect client machine.

System action:

The IBM Spectrum Protect operation ends.

User response:

Determine what might be causing this kind of exception. Try the
operation again, and check if the LAN is down.

------------------------------------------------------------------------
ANS2603S

The browser tried to connect to the client and received exception:
exception-name



Explanation:

The browser received the exception when trying to connect to the IBM
Spectrum Protect client machine.

System action:

The IBM Spectrum Protect operation ends.

User response:

Determine what might be causing this kind of an exception. Determine if
the LAN is down, or if the IBM Spectrum Protect client acceptor on the
IBM Spectrum Protect machine is up and running.

------------------------------------------------------------------------
ANS2604S

The Web client agent was unable to authenticate with the server.



Explanation:

The Web client agent was unable to authenticate with the IBM Spectrum
Protect server.

System action:

The operation ends.

User response:

One possible solution is to run the command line client so that the
client password can be re-entered. Another approach is to check the
error log on the IBM Spectrum Protect Web client agent system for any
relevant messages.

------------------------------------------------------------------------
ANS2605S

Browser could not re-establish connection to client; received protocol
error.



Explanation:

The browser received a protocol error trying to re-connect to the client
machine.

System action:

The operation ends.

User response:

Determine what might be causing this kind of an error. Determine if the
browser and the IBM Spectrum Protect client code might be out of sync.

------------------------------------------------------------------------
ANS2606S

An invalid password was sent to the server.



Explanation:

The password that was sent to the IBM Spectrum Protect server was
invalid.

System action:

The operation ends.

User response:

Make sure that you have the correct password. Also make sure that it is
valid, for example it is not too short.

------------------------------------------------------------------------
ANS2607S

Browser could not establish connection to client.



Explanation:

The browser could not connect to the IBM Spectrum Protect client
machine.

System action:

The operation ends.

User response:

Determine what might be causing this kind of a problem. Determine if the
LAN is down, or if the IBM Spectrum Protect client acceptor on the IBM
Spectrum Protect machine is up and running.

------------------------------------------------------------------------
ANS2609S

TCP/IP communications failure between the browser and the client
machine.



Explanation:

This error can occur due to any of the following:

*  The LAN connection to the IBM Spectrum Protect client machine went
   down.

*  You are trying to connect to the IBM Spectrum Protect client machine
   using the wrong port number.

*  The client acceptor on the IBM Spectrum Protect client machine is not
   up and running and accepting connections.

System action:

The IBM Spectrum 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 Spectrum Protect client machine, and that it is
listening on the correct port number.

------------------------------------------------------------------------
ANS2610S

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



Explanation:

An attempt to connect to the server using TCP/IP communications failed.
This can be a result of incorrect TCP/IP option settings in your client
options file. This error can also occur if the LAN connection went down
or if your system administrator canceled a backup operation.

System action:

The IBM Spectrum Protect client ends.

User response:

Retry the operation and make sure the LAN is up. Make sure that both the
IBM Spectrum Protect server and the IBM Spectrum Protect client are up
and running.

------------------------------------------------------------------------
ANS2611S

An unknown error occurred in the browser.



Explanation:

An unknown error occurred in the applet running in the browser.

System action:

The IBM Spectrum Protect operation ends.

User response:

Retry the operation. If the problem persists, turn on tracing and see if
the trace to the browser console gives the reason for the error.

------------------------------------------------------------------------
ANS2612S

An unknown error occurred in the client Please check the IBM Spectrum
Protect error eog for any additional information



Explanation:

An unknown error occurred in the IBM Spectrum Protect client.

System action:

The IBM Spectrum Protect client ends.

User response:

Retry the operation. If the problem persists, check the IBM Spectrum
Protect error log for any additional information.

------------------------------------------------------------------------
ANS2613S

A communications protocol error occurred between the web browser and the
client.



Explanation:

None.

System action:

The operation ends.

User response:

Try the operation again. If the problem occurs again, verify that the
IBM Spectrum Protect web client is installed and configured correctly,
and make sure you are using a supported browser. Flush the browser
cache. Then try the operation again. If the problem persists, enable
SERVICE traces on the web client on the target machine and the IBM
Spectrum Protect Java applet, then reproduce the problem. Collect the
traces and contact IBM for further assistance.

------------------------------------------------------------------------
ANS2614S

A protocol error occurred in communications between the client and the
server.



Explanation:

A protocol error happened between the IBM Spectrum Protect client and
the IBM Spectrum Protect server.

System action:

The IBM Spectrum Protect client ends.

User response:

Retry the operation. If the problem persists, check the IBM Spectrum
Protect error log for any additional information. Verify that you are
running the correct applet with the appropriate level of the client.

------------------------------------------------------------------------
ANS2615S

The user ID entered does not match the node name configured on the
client machine.



Explanation:

The user ID that was entered is not the same as the node name on this
IBM Spectrum Protect client.

System action:

The IBM Spectrum Protect operation ends.

User response:

Verify that the node name entered is configured correctly on the IBM
Spectrum Protect client.

------------------------------------------------------------------------
ANS2616I

The machine must be rebooted for the changes to take effect



Explanation:

The machine must be started for the restored registry changes to take
effect.

System action:

None

User response:

Reboot the machine

------------------------------------------------------------------------
ANS2617S

The destination directory specified is invalid.



Explanation:

The user specified a destination target directory for restore or
retrieve which is invalid.

System action:

The IBM Spectrum Protect operation ends.

User response:

Retry the operation specifying a valid directory name.

------------------------------------------------------------------------
ANS2619S

The client acceptor was unable to start the Remote Client Agent.



Explanation:

The IBM Spectrum Protect client acceptor could not start the IBM
Spectrum Protect Remote Client Agent.

System action:

The IBM Spectrum Protect operation ends.

User response:

Check the error log on the IBM Spectrum Protect Web client agent for any
relevant messages. Then correct the problem and retry.

------------------------------------------------------------------------
ANS2620W

The expand entire branch operation may take a long time, and cannot be
canceled once it has started. Are you willing to wait for the operation
to complete?



Explanation:

The expand entire branch operation could take a long time and cannot be
canceled once it is started.

System action:

Processing stopped; waiting for user intervention.

User response:

Answer 'Yes' to start the expand entire branch operation. If you answer
'No', the current operation will be canceled.

------------------------------------------------------------------------
ANS2622S

An invalid ID or password submitted.



Explanation:

Either the ID is not registered on the IBM Spectrum Protect server, or
the password for the ID is incorrect.

System action:

The operation ends.

User response:

Verify that the ID you are using exists on the IBM Spectrum Protect
server to which the remote client node connects. The ID must have
sufficient privileges to access the remote client node's data. Also make
sure that you have the correct password for the ID. If the ID does not
exist or if the password is unknown, contact your IBM Spectrum Protect
administrator. If the ID does not exist, then the IBM Spectrum Protect
administrator can use the REGISTER ADMIN and GRANT AUTHORITY commands to
register an ID that can access the remote client node's data. If the
password is unknown, the IBM Spectrum Protect administrator can use the
UPDATE ADMIN command to reset the password.

------------------------------------------------------------------------
ANS2623S

Web Client applet level is out of sync with Web Client agent.



Explanation:

The Web Client applet and Web Client agents are at incompatible levels.

System action:

The operation ends.

User response:

Verify that you have the correct level of the applet installed with the
client, and that an incorrect level of the applet was not placed in the
install directory.

------------------------------------------------------------------------
ANS2624E

This operation requires client owner authority.



Explanation:

Your user ID has insufficient authority to perform this operation.

System action:

Processing continues, but the user is not allowed to do this operation.

User response:

Do not perform this operation, or get a higher authority level for your
user ID in order to perform this operation.

------------------------------------------------------------------------
ANS2625E

Node does not support this image operation.



Explanation:

Node does not support or is not configured to perform this image
operation.

System action:

Processing continues, but the user is not allowed to do this operation.

User response:

Verify whether this image related operation is supported or configured
on the target platform.

------------------------------------------------------------------------
ANS2626E

The Include-Exclude statement: ieStatement contains invalid characters.



Explanation:

The specified Include-Exclude statement has invalid characters.

System action:

IBM Spectrum Protect will not add the specified Include-Exclude
statement to the list.

User response:

Retry the operation with another statement that has valid characters.

------------------------------------------------------------------------
ANS2627W

The NTFS security attributes for object 'full-name' could not be set.
Windows system error code: error; reason: 'error-reason'. Default NTFS
security attributes have been set.



Explanation:

IBM Spectrum Protect was unable to set the NTFS security attributes of
the file. The error information captured indicates the reason for the
failure. Default NTFS security attributes have been set.

System action:

Processing continues.

User response:

Check the reason field for the code which explains why the NTFS security
attributes have not been set. Correct the condition causing the error
and try the operation again. If the problem persists, contact your
system administrator or IBM Spectrum Protect administrator for further
help.

------------------------------------------------------------------------
ANS2628W

Failed to create named stream of object
'file_space_namepath_namefile_name'.



Explanation:

The process was unable to create named stream.

System action:

The named stream is not restored/retrieved.

User response:

The object is restored without named stream, the object should be
examined to verify that it is usable. Check the client error log for
ANS5250E error message that should have been logged when this message
was written, take the corrective action and try the operation again. If
the problem persists, contact your system administrator or IBM Spectrum
Protect administrator for further help.

------------------------------------------------------------------------
ANS2629I

Migration: The filespace will be migrated to the Incremental Forever
model.



Explanation:

The first time an Incremental Forever Incremental (IFIncr) backup is
performed against a virtual machine that was previously backed up using
the Periodic Full model, and the latest backup is an incremental backup,
then backup chain will be migrated to the Incremental Forever model.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS2630E

The Java runtime library for the vCloud Suite plug-in library failed to
load or initialize.



Explanation:

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

User response:

For Linux operating system, verify that a link named 'jre', referencing
the 'jre' directory under your Java installation path, exists in the
backup-archive client installation directory. If a link does not exist,
create the link (e.g. ln -s /opt/ibm/java-x86_64-70/jre
/opt/tivoli/tsm/client/ba/bin/jre). Alternatively, modify
LD_LIBRARY_PATH to include the path to libjvm.so (e.g. export
LD_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 that the JRE directory exists under
the client installation directory. Reinstall the backup-archive client
if necessary.

------------------------------------------------------------------------
ANS2631E

The vCloud Suite plug-in library cannot be initialized.



Explanation:

The vCloud Suite plug-in library failed to initialize. This issue might
be caused by the Java runtime not being installed.

System action:

vCloud Suite operations cannot be performed.

User response:

Verify that Java is installed.

------------------------------------------------------------------------
ANS2632E

The vCloud Suite plug-in library cannot attach to the Java runtime.



Explanation:

The vCloud Suite plug-in library failed attach to the JVM runtime. This
issue might be caused by the Java runtime being corrupted or an
incomplete installation.

System action:

vCloud Suite operations cannot be performed.

User response:

Verify that Java is installed and functioning properly.

------------------------------------------------------------------------
ANS2633E

The vCloud Suite plug-in runtime library failed to log into the Platform
Services Controller on 'psc-host' with user name 'user-name':
authentication failed.



Explanation:

The vCloud Suite single sign-on credentials specified in the VMCUSER and
VMCPW options were rejected by the Platform Services Controller.

System action:

vCloud Suite operations cannot be performed.

User response:

Update the VMCUSER and VMCPW options with valid credentials for the
targeted Platform Services Controller.

------------------------------------------------------------------------
ANS2634E

The vCloud Suite plug-in runtime library failed to log into the Platform
Services Controller on 'psc-host'.



Explanation:

A connection cannot be established to the Platform Services Controller
using the VMCHOST option.

System action:

vCloud Suite operations cannot be performed.

User response:

Verify that the value of the VMCHOST option is correct, network
connectivity to the host exists, and that the Platform Services
Controller service is running. Enable VCLOUD tracing in the option file
for any additional messages that might be related to this problem.

------------------------------------------------------------------------
ANS2635E

The vCloud Suite plug-in runtime library encountered an internal error.



Explanation:

The vCloud Suite plug-in library encountered an unexpected internal
error that was not caught.

System action:

vCloud Suite operations cannot be performed.

User response:

Check the dsmerror.log file for any additional messages that might be
related to this problem, enable VCLOUD tracing in the option file.

------------------------------------------------------------------------
ANS2636E

The vCloud Suite plug-in library is uninitialized.



Explanation:

The vCloud Suite plug-in library is uninitialized. This issue might be
caused by an error loading or initializing the plug-in library.

System action:

vCloud Suite operations cannot be performed.

User response:

Check the dsmerror.log file for any additional messages that might be
related to this problem, enable VCLOUD tracing in the option file.

------------------------------------------------------------------------
ANS2640I

The virtual machine 'VM-name' is configured with the 'exclude-category'
category and the 'exclude-tag' tag, which excludes the virtual machine
from the backup operation.



Explanation:

The client option 'VMTAGDATAMOVER' is enabled so that IBM categories and
tags can be applied to virtual machines.

System action:

The virtual machine is excluded from the scheduled backup operation.

User response:

Remove the tag if the virtual machine should be included in scheduled
backups, run an on-demand backup of the virtual machine, or set the
'VMTAGDATAMOVER' option to 'No' in the client options file.

------------------------------------------------------------------------
ANS2641E

The client failed to load the VMware vCloud Suite plug-in library
'piVcloudSuiteJNI'.



Explanation:

The VMware vCloud Suite plug-in library 'piVcloudSuiteJNI' could not be
found or could not be loaded. This issue might be caused by the library
being corrupted or an incomplete installation.

System action:

The operation cannot be completed without the VMware vCloud Suite
plug-in library.

User response:

Verify that the VMware vCloud Suite plug-in library 'piVcloudSuiteJNI'
is in the 'plugins' folder in the client installation folder or disable
the clinet option 'VMTAGDATAMOVER'.

------------------------------------------------------------------------
ANS2642E

The VMware vCloud Suite plug-in library could not find a required Java
class or method.



Explanation:

The VMware vCloud Suite plug-in library failed to find a required Java
class or method. This issue might be caused by an incomplete
installation, missing VMware vCloud Suite plug-in JAR
'piVcloudSuiteJwrapper.jar' file or the JAR files are not in the Java
classpath.

System action:

The operation cannot be completed without the VMware vCloud Suite
plug-in library.

User response:

Verify that the VMware vCloud Suite plug-in library JAR
'piVcloudSuiteJwrapper.jar' is in the 'plugins' and the other JAR files
are in 'plugins/sdk' in the client installation folder or disable the
clinet option 'VMTAGDATAMOVER'.

------------------------------------------------------------------------
ANS2643I

An on-demand backup of the virtual machine 'VM-name' is running. The
virtual machine is configured with the 'exclude-category' category and
the 'exclude-tag' tag.



Explanation:

The client option 'VMTAGDATAMOVER' is enabled so that IBM categories and
tags can be applied to virtual machines, but the on-demand backup
overrides the tag setting for exclusion.

System action:

The backup operation continues.

User response:

No action is required.

------------------------------------------------------------------------
ANS2644I

The virtual machine 'VM-name' is not configured with a
'exclude-category' tag and can only be backed up by a default data
mover. The virtual machine will be excluded from the scheduled backup
operation.



Explanation:

The client option 'VMTAGDATAMOVER' is enabled so that IBM categories and
tags can be applied to virtual machines. The active data mover is not
the default data mover so its unable to perform the backup operation.

System action:

The virtual machine is excluded from the scheduled backup operation.

User response:

If you want to include the virtual machine in schedule backups, assign a
data mover tag to the virtual machine or make sure a data mover is set
up as a default data mover by using the VMTAGDEFAULTDATAMOVER option.

------------------------------------------------------------------------
ANS2649E

A Schedule name was not provided.



Explanation:

An error occurred while processing. Either the option TAGSCHEDULE was
missing or the value of the parameter was incorrect.

System action:

The rebalance processing ended.

User response:

Provide a valid schedule with the TAGSCHEDULE option and try the
operation again.

------------------------------------------------------------------------
ANS2650E

The process does not have the VMTAGDATAMOVER option specified.



Explanation:

An error occurred while processing. The option VMTAGDATAMOVER must be
present in the option file.

System action:

The rebalance processing ended.

User response:

To use this feature, employ a datamover configured as a tagged
datamover.

------------------------------------------------------------------------
ANS2651E

The ASNODENAME option must be provided to rebalance a VMware schedule.



Explanation:

An error occurred while processing. There was a problem processing the
ASNODENAME option or it was not provided to the command.

System action:

The rebalance processing ended.

User response:

To use this feature, employ a datamover configured as a proxy agent for
a datacenter.

------------------------------------------------------------------------
ANS2659I

datamover_count data movers are assigned to schedule sched-name.



Explanation:

Since less than two data movers are assigned to this schedule,
assignment of datamover tags was not possible.

System action:

None.

User response:

Use the vCenter GUI to manually assign a data mover to this schedule.

------------------------------------------------------------------------
ANS2666S

Either the ource or target volumes are duplicated. The same volume is
mounted on more volume paths.



Explanation:

This error can occur when a source volume is mapped on more volume
paths, for example, a drive letter and one or more mount point
directories. Because IBM Spectrum Protect uses the volume path to keep
track of backup information in its internal backups database, it cannot
back up the same volume with a duplicate volume path. See addition
information in the error log.

System action:

IBM Spectrum Protect cannot select the volume.

User response:

Delete the last snapshots created as they are not managed by IBM
Spectrum Protect. Unmount the duplicate volume path in order to have a
single mount point to the same source volume. Restart IBM Spectrum
Protect and retry the operation.

------------------------------------------------------------------------
ANS2667I

Scan operation was successful.



Explanation:

The virtual machine was scanned successfully.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2668E

Scan operation failed with an unexpected error.



Explanation:

An unexpected error occurred during guest scan operations.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Check the client error log for additional information.

------------------------------------------------------------------------
ANS2669I

Guest operating system platform is not supported.



Explanation:

The operating system of the virtual machine was not supported by the
scan operation.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2670I

Remote directory in guest is being used by another application.



Explanation:

The scan operation was unable to copy files to the remote directory
because the directory is in use by another application.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Ensure that the remote directory is unlocked. Then, reschedule the scan
operation.

------------------------------------------------------------------------
ANS2671I

Virtual machine name was not found on the VMware server.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2672W

Hostname could not be found for the specified virtual machine name.



Explanation:

This issue might be caused by the virtual machine not running and not
having a static IP address.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Make sure the guest is properly configured. Then, reschedule the scan
operation.

------------------------------------------------------------------------
ANS2673I

Duplicate virtual machine name was detected.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2674I

The virtual machine is not connected to ESX server.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2675E

Proxy Rejected: Proxy authority has not been granted to the specified
data mover node.



Explanation:

The scan of the virtual machine failed.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

The IBM Spectrum Protect server administrator must grant proxy authority
for this node. See the administrator command "Grant Proxynode".

------------------------------------------------------------------------
ANS2676W

The guest operating system credential was not found.



Explanation:

The guest scan operation requires a valid operating system credential.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Ensure the guest operating system credential is set. Then, reschedule
the scan operation.

------------------------------------------------------------------------
ANS2677W

The guest operating system credential is invalid.



Explanation:

The guest scan operation requires a valid operating system credential.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Ensure a valid guest operating system credential is set. Then,
reschedule the scan operation.

------------------------------------------------------------------------
ANS2678I

Guest machine is powered off.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2679I

VMware Tools on the guest machine is not running.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2680I

VMware Tools version on the guest machine is not current.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2681W

ESX host or vCenter version is not supported.



Explanation:

The ESX host or vCenter is a down level version.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Refer to the product documentation for supported ESX and vCenter
versions.

------------------------------------------------------------------------
ANS2682I

The guest credential has insufficient permissions.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2683W

Cannot communicate with the remote host.



Explanation:

This communication issue is caused by network errors or by the host not
responding.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Ensure that the network and host connection are configured correctly.
Then, reschedule the scan operation.

------------------------------------------------------------------------
ANS2684I

The guest operation agent could not be contacted.



Explanation:

None

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2685I

The VM is a template.



Explanation:

VM templates are not supported by the scan operation.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

None

------------------------------------------------------------------------
ANS2686E

VM scan initialization error.



Explanation:

The vm scan operation encountered an error during initialization.

System action:

The scan process stops for the virtual machine. The next virtual machine
in the data center will be processed.

User response:

Check the client error log and trace for additional information.

------------------------------------------------------------------------
ANS2687W

The virtual machine 'VM-name' contains one or more disks that exceed the
maximum size set by the VMMAXVIRTUALDISKS option. You can use the
VMMAXVIRTUALDISKS option to change the maximum size or specify the
'-VMSKIPMAXVIRTUALDISKS=yes' option to exclude these disks from the
backup.



Explanation:

The IBM Spectrum Protect client does not back up VMDKs that are larger
than the maximum size.

System action:

The virtual machine is not backed up.

User response:

Use the VMMAXVIRTUALDISKS option to change the maximum size or specify
the '-VMSKIPMAXVIRTUALDISKS=yes' option to exclude these disks from the
backup.

------------------------------------------------------------------------
ANS2688E

The restore of a Hyper-V virtual machine that was backed up using
incremental forever backup is not allowed on a Windows 2008 or Windows
2008 R2 host. The restore operation must be completed on a Windows 2012
or later Hyper-V host



Explanation:

A Hyper-V virtual machine that was backed up with the incremental
forever backup type can only be restored on a Windows 2012 or later
Hyper-V host.

System action:

The restore operation does not start.

User response:

Try the operation again with a Windows 2012 or later Hyper-V host.

------------------------------------------------------------------------
ANS2689E

A Hyper-V command subcommand command was specified, but the Hyper-V role
is not enabled on the host system



Explanation:

The Hyper-V role must be enabled on the host system where the Hyper-V
operation occurs. The current system does not have the Hyper-V role
enabled.

System action:

The operation does not start.

User response:

Try the operation again from a host that has the Hyper-V role enabled.

------------------------------------------------------------------------
ANS2690E

A Hyper-V BACKUP VM command with mode IFFULL or IFINCR was specified but
the Data Protection for Microsoft Hyper-V license file does not exist or
is not valid



Explanation:

The Data Protection for Microsoft Hyper-V license file is required to
issue Hyper-V BACKUP VM commands with mode IFFULL or IFINCR. Make sure
the Data Protection for Microsoft Hyper-V file is installed.

System action:

The backup does not start.

User response:

Try the operation again from a host that has the Data Protection for
Microsoft Hyper-V license file installed. Or, issue the BACKUP VM
command and specify mode FULL.

------------------------------------------------------------------------
ANS2691E

A Hyper-V BACKUP VM command with mode FULL was specified but the Data
Protection for Microsoft Hyper-V license file exists. Mode IFFULL or
IFINCR must be specified



Explanation:

Hyper-V BACKUP VM commands with mode FULL are not allowed on hosts where
the Data Protection for Microsoft Hyper-V license file is installed.
Instead, issue the BACKUP VM command using mode IFFULL or IFINCR.

If you must issue the BACKUP VM command with mode FULL, you must
uninstall the Data Protection for Microsoft Hyper-V license file.
However, uninstalling the license file invalidates the IFINCR backup
chain. As a result, an IFFULL is performed if the Data Protection for
Microsoft Hyper-V license file is reinstalled.

System action:

The backup does not start.

User response:

Try the operation again and specify mode IFFULL or IFINCR.

------------------------------------------------------------------------
ANS2692E

An error occurred while registering the filespace for virtual machine
(VM_name).



Explanation:

An error occurred while registering the filespace for the specified
virtual machine.

System action:

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

User response:

Check the error log for information about how to resolve this issue.

------------------------------------------------------------------------
ANS2693E

An error occurred while registering the filespace for virtual machine
(VM_name). There is a filespace with the same name that is currently
being deleted.



Explanation:

An error occurred while registering the filespace for the specified
virtual machine. A filespace with the same name is currently being
deleted on the IBM Spectrum Protect server

System action:

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

User response:

Wait for the delete filespace to finish and run the backup command
again.

------------------------------------------------------------------------
ANS2694W

Application protection is enabled for virtual machine 'VM-name';
however, this virtual machine contains one or more disks that exceed the
maximum size of 2 TB allowed for application protection operations.
Application protection needs to be disabled in order to backup this
virtual machine.



Explanation:

The IBM Spectrum Protect client does not back up VMDKs that are larger
than 2 TB when application protection is being used.

System action:

The virtual machine is not backed up.

User response:

Application protection must be disabled in order to backup the specified
virtual machine.

------------------------------------------------------------------------
ANS2695W

The periodic full backup mode is being used; however, the virtual
machine 'VM-name' contains one or more disks that exceed the maximum
size of 2 TB allowed for the periodic full backup mode. You can use the
'-VMSKIPMAXVIRTUALDISKS=yes' option to exclude these disks from the
backup, or change to the incremental forever backup mode.



Explanation:

The IBM Spectrum Protect client does not back up VMDKs that are larger
than 2 TB when the periodic full backup mode is being used.

System action:

The virtual machine is not backed up.

User response:

Use the '-VMSKIPMAXVIRTUALDISKS=yes' option to exclude these disks from
the backup, or change to the incremental forever backup mode.

------------------------------------------------------------------------
ANS2696E

Control or data files were found to be compressed but not deduplicated
for vm vm name.



Explanation:

During a verify operation, the data mover detected that one or more
control or data files on the server are compressed, but not
deduplicated. This is an invalid state because data that is compressed,
but not deduplicated, cannot be recovered. An incremental forever full
backup of the VM is needed before incremental forever incremental
backups can resume.

System action:

The backup operation for this VM continues based on the VMVERIFYIFAction
option.

User response:

Perform a full VM backup for this virtual machine or specify the
VMVERIFYAction option to force a full VM backup.

------------------------------------------------------------------------
ANS2697E

The virtual machine cannot be restored because the datastore named
'datastore' does not exist or is inactive.



Explanation:

The datastore referenced by virtual machine when it was backed up does
not exist or is inactive on the ESX/ESXi that you are restoring the
virtual machine to.

System action:

The virtual machine cannot be restored.

User response:

Find the missing datastore or specify the -datastore option on the
Restore VM command to specify an existing datastore to restore the
virtual machine files to.

------------------------------------------------------------------------
ANS2698E

Snapshot operation failed.



Explanation:

If you are performing a VSS or LVSA snapshot based operation, it is
possible that the snapshot was not large enough to contain all the
changes made to the file system after the snapshot was created. This
could cause the snapshot to become invalid thereby preventing the IBM
Spectrum Protect client from reading the snapshot.

System action:

The requested operation stopped.

User response:

Examine the client error log for additional messages related to this
error. Perform corrective actions indicated by the messages, then try
the operation again.

------------------------------------------------------------------------
ANS2699W

Importing VM 'vm name' failed for vApp 'vapp name'.



Explanation:

The import VM from vSphere to a vCloud vApp operation failed.

System action:

Restore processing for the vApp continues.

User response:

Check the dsmerror.log file for information about why the VM was not
imported. Then, try the operation again. If the problem persists, visit
the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2700E

Restoring VM 'vm name' of vApp 'vapp name' is not possible. There is no
VM backup data.



Explanation:

During the vApp restore, a VM that exists in the restored vApp version
could not be restored, 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 any messages that might be indicate on
the reason for the specified VM's backup failure. Contact IBM Spectrum
Protect technical support if further assistance is required.

------------------------------------------------------------------------
ANS2701E

The attempted database operation was unsuccessful, check the error log
for any additional information.



Explanation:

Processing stops.

System action:

Reserved.

User response:

Check the error log for information regarding failure and take further
action.

------------------------------------------------------------------------
ANS2704E

Error: The vCenter server version is at a lower level than the ESX host
version, or the user ID specified by the VMCUser option does not have
sufficient permission to perform the operation.



Explanation:

The vCenter returned an error indicating there is a problem with the
license. This error can occur when the vCenter server version is at a
lower level than the ESX host version. The vCenter server version must
be at the same (or later) level as the ESX host version. This error can
also occur when the user ID specified by the VMCUser option does not
have sufficient permission to perform the operation or the permissions
are not applied at the vCenter server level.

System action:

Processing stops.

User response:

Verify the vCenter server is at the correct level, and verify that the
user ID specified by the VMCUser option has sufficient permission to
perform the operation.

------------------------------------------------------------------------
ANS2705S

No Db2 UDB partitions are available for restore.



Explanation:

No Db2 UDB partitions are available on the IBM Spectrum Protect server
for restore. This is most likely due to a previous backup that was
aborted before the backup completed. The Db2 UDB database and selected
partitions cannot be restored.

System action:

Processing stops.

User response:

Issue the IBM Spectrum Protect client command QUERY DB2UDB command with
the -DETAIL parameter using the same database, file, and date criteria
to see if any database partitions are available for restore.
Alternatively restore the Db2 UDB database from a different backup.

------------------------------------------------------------------------
ANS2706E

The option VMBACKUPLOCATION=value is not allowed with restore type
operation 'type'.



Explanation:

Operation failed.

System action:

Processing stopped.

User response:

Remove option VMBACKUPLOCATION from the command line and try again.

------------------------------------------------------------------------
ANS2707W

The VMBACKUPLOCATION option value BOTH was specified. The local backup
for virtual machine 'VM-name' failed, but the backup to the server
completed.



Explanation:

The local backup failed. Only the server backup was successful.

System action:

Processing completed.

User response:

Contact your system administrator to resolve issues that cause the local
backup to fail.

------------------------------------------------------------------------
ANS2708E

One or more disks of the virtual machine 'VM-name' are not in a virtual
volumes datastore. Local backup is not allowed. If the VMBACKUPLOCATION
option value BOTH was specified, the backup to the server will continue.



Explanation:

Local backup is only supported for virtual machines that are in a
virtual volumes datastore.

System action:

Processing continues if VMBACKUPLOCATION=BOTH was specified.

User response:

If you want local backup, contact your system administrator to
reconfigure the virtual machine and then try the backup again.

------------------------------------------------------------------------
ANS2709E

The snapshot of virtual machine 'VM-name' was removed after the backup.



Explanation:

The virtual machine snapshot was removed by another application or
process after the backup. This removal corrupted the backup and it
cannot be restored or mounted.

System action:

Processing stopped.

User response:

Delete the local backup from the IBM Spectrum Protect server for this
virtual machine.

------------------------------------------------------------------------
ANS2710E

The virtual machine 'VM-name' was removed from the inventory.



Explanation:

The virtual machine was removed from the inventory. This removal
invalidates all local backups.

System action:

Processing stopped.

User response:

Delete all the local backups from the IBM Spectrum Protect server for
this virtual machine.

------------------------------------------------------------------------
ANS2711E

The snapshot of virtual machine 'VM-name' was removed during the backup.



Explanation:

The virtual machine snapshot was removed by another application or
process during the backup. This removal corrupts the backup and it
becomes unusable.

System action:

The virtual machine is not backed up.

User response:

Ensure that another application or process does not remove or modify the
virtual machine during the backup.

------------------------------------------------------------------------
ANS2712W

The virtual machine 'name' has a VMware Tools running, but VMware Tools
is out of date.



Explanation:

A supported version of VMware Tools must be installed, running and
current to complete a virtual machine backup.

System action:

The backup operation fails.

User response:

Verify that a supported version of VMware Tools is installed, current
and running. Then, try the backup operation again.

------------------------------------------------------------------------
ANS2713E

The virtual machine 'VM-name' is in an invalid connection state 'state'.
As a result, it cannot be backed up.



Explanation:

To back up a virtual machine it must be in the 'connected' state to be
accessed.

System action:

The virtual machine is not backed up.

User response:

Return the virtual machine to the 'connected' state and try the backup
again.

------------------------------------------------------------------------
ANS2714W

The management class 'mc' specified for the 'dest' backup destination is
invalid. The default management class will be used.



Explanation:

None.

System action:

Processing continues.

User response:

Contact the IBM Spectrum Protect administrator to run the configuration
utility for DB2 UDB and specify a valid management class.

------------------------------------------------------------------------
ANS2715E

The virtual machine 'VM-name' is configured as a fault tolerant virtual
machine. As a result, it cannot be backed up.



Explanation:

vSphere does not allow for the snapshot or backup of fault tolerant
virtual machines with vStorage API for Data Protection.

System action:

The virtual machine is not backed up.

User response:

To back up a fault tolerant virtual machine with vStorage API for Data
Protection, first disable fault tolerant. Then, after the backup
completes, enable fault tolerant.

------------------------------------------------------------------------
ANS2716E

A background copy process is still pending on local hardware. A restore
operation cannot be initiated until the background copy process is
completed.



Explanation:

None.

System action:

Processing stops.

User response:

Wait until the background copy process completes and retry the restore
operation.

------------------------------------------------------------------------
ANS2717E

The multi-node definition does not have permission to delete its own
backup files from the server.



Explanation:

All DB2 UDB commands require that the multi-node definition has
permission to delete its own backup files from the server in order to
properly reconcile the local backup repository with the server backup
repository.

System action:

Processing stops.

User response:

Have the IBM Spectrum Protect administrator update the multi-node
definition so that it has permission to delete its own backup files from
the server. For example, on the IBM Spectrum Protect administrative
command-line client:. dsmadmc update node <multi-node name>
backdelete=yes

------------------------------------------------------------------------
ANS2718W

The virtual machine 'VM-name' requires snapshot consolidation.



Explanation:

Snapshot consolidation is required when a snapshot is deleted but its
associated disk is not committed back to the base disk. If consolidation
is not completed, snapshot disks might grow and eventually fill the data
store.

System action:

The virtual machine backup continues.

User response:

Consolidate the virtual machine snapshots according to instructions
provided in the appropriate VMware vSphere documentation.

------------------------------------------------------------------------
ANS2719E

A previous backup started on 'datetime', is using the resources needed
for new backup is still pending.



Explanation:

A new backup can not be done until previous backup completes.

System action:

Processing stops.

User response:

Wait until previous backup completes before starting another local
backup. Alternatively, use different copyType value to perform a local
backup. IBM Spectrum Protect local backup policy only allows one
incremental and one full background copy to be pending at any time,
before local backup resources are reused for a new backup version. A new
local backup would result in a backup with background copy in pending
state.

------------------------------------------------------------------------
ANS2720W

Failed to execute the command 'command'.



Explanation:

IBM Spectrum Protect Failed to execute a command. The possible reason -
the command interpreter cannot be found. Verify the ComSpec and PATH
environment variables that locate the command interpreter. Either
ComSpec or PATH is not defined, or it is not correctly defined.

System action:

The command does not run. Otherwise processing will attempt to continue.

User response:

Correct the ComSpec and PATH environment variable that locate the
command interpreter. Contact your system administrator if you are not
sure how to make this correction.

------------------------------------------------------------------------
ANS2721E

The virtual machine is in an invalid connection state. As a result, it
cannot be backed up.



Explanation:

One or more virtual machine backups failed because of an invalid
connection state. A virtual machine must be in the 'connected' state to
be accessed for backup.

System action:

Processing stops for this virtual machine

User response:

Check the console output and error logs for information about why the
connection state was invalid. Correct any issues and try backing up the
failed virtual machines.

------------------------------------------------------------------------
ANS2722E

There is not enough space in the local repository to complete this
backup.



Explanation:

This space available in the local repository is not enough to perform
snapshot for this backup operation. It could happen if there is more
number of local versions kept by the management class than there is
space allocated in the local repository at configuration time or
application configuration has changed such that previously allocated
space is not enough.

System action:

None.

User response:

Please validate IBM Spectrum Protect configuration by running the
configuration wizard.

------------------------------------------------------------------------
ANS2723E

A value of UNDEF for the REAdstartsrecall option is not valid when the
HSMBACKENDMODE option is set to IBM Spectrum Protect.



Explanation:

A value of UNDEF for the REAdstartsrecall option is valid only when the
HSMBACKENDMODE option is set to TSMFREE.

System action:

The operation stops. The file is skipped.

User response:

If the HSMBACKENDMODE option is set to IBM Spectrum Protect, set the
REAdstartsrecall option to YES or NO.

------------------------------------------------------------------------
ANS2725E

IBM Spectrum Protect application protection could not register the IBM
Spectrum Protect VSS provider on the guest VM 'VM'.



Explanation:

The guest vm credentials speficied on the datamover do not have the
correct required Windows permissions for application protection.

System action:

The application protection vm backup processing stops.

User response:

Make sure that the credentials specified for the guest VM have the
correct required Windows permissions for application protection type vm
backups. The user guide outlines the correct permissions that are
required for backuping and restoring application data for Microsoft
Exchange and Microsoft SQL Servers.

------------------------------------------------------------------------
ANS2729E

Operating system command 'command' failed; rc=rc.



Explanation:

None.

System action:

Process stops.

User response:

Check the return code from the operating system for more information
about the failure. Issue the failing command manually to see if the same
failure occurs.

------------------------------------------------------------------------
ANS2730E

The dsmmigrate command is unable to get a list of IBM Spectrum Scale
nodes.



Explanation:

The dsmmigrate command is unable to get a list of IBM Spectrum Scale
nodes due to an unexpected internal error.

System action:

Processing stopped.

User response:

Contact your system administrator for more information.

------------------------------------------------------------------------
ANS2731E

The BACKUP VM command failed because the Data Protection for VMware
license file does not exist or is not valid.



Explanation:

The Data Protection for VMware license file is required for the BACKUP
VM command.

System action:

The command is not processed.

User response:

Install Data Protection for VMware or the license file for Data
Protection for VMware, and retry the command. Or retry the operation
from a host that has the Data Protection for VMware license file
installed.

------------------------------------------------------------------------
ANS2732E

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



Explanation:

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

System action:

The command is not processed.

User response:

Install Data Protection for Microsoft Hyper-V or the license file for
Data Protection for Microsoft Hyper-V, and retry the command. Or retry
the operation from a host that has the Data Protection for Microsoft
Hyper-V license file installed.

------------------------------------------------------------------------
ANS2733E

An operation requiring the Windows Management Instrumentation (WMI)
service has failed with the error 'errorstring'. IBM Spectrum Protect
has been denied access to a WMI system due to insufficient privileges.



Explanation:

Windows denied access to a Windows Management Instrumentation (WMI)
resource, object, or operation. This program has insufficient
permissions to perform the requested operation.

System action:

Performing an operation requiring the Windows Management Instrumentation
service.

User response:

Raise the permissions assigned to IBM Spectrum Protect and retry the
operation.

------------------------------------------------------------------------
ANS2734E

An operation requiring the Windows Management Instrumentation (WMI)
service has failed with the error 'errorstring'. The application
interface does not exist.



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.

User response:

Register the Windows Management Instrumentation classes of the
appropriate Windows feature.

------------------------------------------------------------------------
ANS2735W

All selective and transparent recalls are blocked due to the
HSMOPTIMIZEDRECALLONLY option. This message will not be reissued for the
next 24 hours.



Explanation:

If the HSMOPTIMIZEDRECALLONLY option is set to YES, only optimized
recalls are allowed.

System action:

Recall is blocked.

User response:

Disable the HSMOPTIMIZEDRECALLONLY option and restart the HSM daemons.

------------------------------------------------------------------------
ANS2736E

An unexpected response was received from a remote IBM Spectrum Protect
file system agent. verb : verb remote host : host return code : rc
reason code : rs msg. string : msg-string



Explanation:

None.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS2737W

No disks from VM are mounted because all disks were excluded during the
backup.



Explanation:

No disks from VM can be mounted because all disks were excluded during
backup or the VM did not contain any disks.

System action:

The operation stops.

User response:

If files from the affected file systems or volumes must be recovered,
ensure that at least one disk is included in the backup.

------------------------------------------------------------------------
ANS2738W

'filename' cannot be recovered because it is being used by process.



Explanation:

Another process, dsmmigrate or dsmrecalld, is using the file.

System action:

The file is not included for recovery.

User response:

Wait until the file is closed and retry recovery if necessary.

------------------------------------------------------------------------
ANS2739W

'filename' cannot be recovered because either a migration process or a
recall process on node node-ID is accessing the same file.



Explanation:

The migration process may be run on another node.

System action:

The file is not included for recovery.

User response:

Run the recovery on another node.

------------------------------------------------------------------------
ANS2740E

The vApp restore operation failed.



Explanation:

The vApp restore operation failed. Check the error log for details on
why the operation failed.

System action:

Processing stops

User response:

Review the console output and error logs for the details on the problem.
Fix any issues and restart the operation.

------------------------------------------------------------------------
ANS2741E

Recovery of object 'file-name' failed.



Explanation:

An error occurred when dsmmigrate tried to recover the file.

System action:

The file is not included for recovery.

User response:

Examine the client error log for additional messages related to this
error.

------------------------------------------------------------------------
ANS2742W

File 'file-name' is not included for recovery.



Explanation:

The file is not included for recovery because: 1) It is a resident file.
2) The migration/recall process is currently running and using the file.
3) Crash-recovery information was not found and the file cannot be
recovered. 4) Crash-recovery information was found on different IBM
Spectrum Scale nodes and it is unclear which crash-recovery information
to use.

System action:

The file is not included for recovery.

User response:

None.

------------------------------------------------------------------------
ANS2744I

TESTFLAG Db2 enabled with the value of 'value'.



Explanation:

None.

System action:

This message is informational.

User response:

None.

------------------------------------------------------------------------
ANS2745E

An assigned virtual disk to Hyper-V Virtual Machine 'virtualmachinename'
cannot be found.



Explanation:

The IBM Spectrum Protect client detected that a Virtual Machine has
assigned a disk that is unreachable. The disk may have been moved or
deleted. A snapshot cannot be taken while the disk cannot be found.

System action:

The IBM Spectrum Protect could not find a virtual disk at the assigned
path.

User response:

Check that the virtual disk has not been moved or deleted and update the
virtual machine configuration to match any changes to the file system.

------------------------------------------------------------------------
ANS2746E

An assigned virtual disk to Hyper-V virtual machine 'virtualmachinename'
is a VHD or invalid format. Only virtual disks in VHDX format can be
backed up.



Explanation:

The IBM Spectrum Protect client detected that a virtual machine has
assigned a disk that is in the VHD format or is in an unrecognisable or
unsupported format. If the disk is in VHDX format it may be corrupted.

System action:

The IBM Spectrum Protect found a virtual disk in VHD or unrecognisable
format while preparing for a backup of a virtual machine.

User response:

If the virtual disk is in VHD format there are several options: Remove
the VHD from the virtual machine, convert the virtual disk from VHD
format to VHDX format, or adjust DOMAIN.VMFULL to skip the virtual
machine from backup. If the disk is in VHDX format, check that the disk
has not been corrupted.

------------------------------------------------------------------------
ANS2747E

An assigned AVHDX virtual disk to Hyper-V virtual machine
'virtualmachinename' cannot find the parent disk. Snapshots can be taken
only if the parent can be found.



Explanation:

The AVHDX format specifies an internal field that points to a parent
AVHDX or VHDX file. If the parent cannot be found the disk is invalid
and a snapshot will fail.

System action:

The process discovered an AVHDX attached to a virtual machine and
attempted to find the parent AVHDX or VHDX file.

User response:

Check that the parent AVHDX or VHDX file still exists and has not been
moved or deleted. Return the parent AVHDX and/or VHDX file.

------------------------------------------------------------------------
ANS2748E

An assigned virtual disk to Hyper-V virtual machine 'virtualmachinename'
exceeds the maximum capacity limit. The IBM Spectrum Protect client
cannot backup virtual machines with disks that exceed the limit of two
terabytes.



Explanation:

The IBM Spectrum Protect client detected that a Virtual Machine has
assigned a disk whose capacity exceeds two terabytes. Virtual disks that
exceed 2 terabytes are currently not supported by incremental forever
backups.

System action:

The IBM Spectrum Protect found a virtual disk whose capacity exceeds two
terabytes on a virtual machine scheduled for back up.

User response:

There are several options available: Remove the disk from the virtual
machine, shrink the disk to under two terabytes, copy the data to
virtual disk with a capacity under two terabytes. Even though
incremental backup is not available, the always full backup type is
compatible with disks over two terabytes.

------------------------------------------------------------------------
ANS2749E

See Microsoft Technote KB2771882. An assigned virtual disk to Hyper-V
Virtual Machine 'virtualmachinename' contains files that are on a
Cluster Shared Volume and local volumes. A snapshot of a Virtual Machine
in this configuration cannot be taken.



Explanation:

The IBM Spectrum Protect client detected that a Virtual Machine has
files involved in the snapshot on both local volumes and Cluster Shared
Volumes. Attempting to snapshot a virtual machine in this configuration
always results in failure. This error is documented in Microsoft
Technote KB2771882.

System action:

The IBM Spectrum Protect client discovered the virtual machine has files
on local volumes and cluster shared volumes prior to taking a snapshot.

User response:

Check that all of the disks and the configuration files are all on local
volumes or cluster shared volumes. If necessary, perform a storage
migration to move the disks and/or configuration files.

------------------------------------------------------------------------
ANS2750E

The Hyper-V Virtual Machine 'virtualmachinename' is currently undergoing
one of the following operations: * Creating Local Snapshot * Applying
Local Snapshot * Deleting Local Snapshot * Exporting Virtual Machine *
Migrating Virtual Machine * Volume Snapshot Service (VSS) Snapshot *
Restore * Merging Differencing Disks The above operations prevent a
Hyper-V VSS snapshot from taking place. Wait for the operation to finish
or cancel to perform a backup.



Explanation:

Some virtual machine management tasks interfere with a virtual machine
VSS snapshot. One of these operations was detected during a back up
request.

System action:

The IBM Spectrum Protect client discovered the virtual machine is
currently undergoing an operation that will prevent a Volume Snapshot
Service snapshot from occuring.

User response:

Cancel or wait for the current virtual machine management task to finish
and then retry the back up.

------------------------------------------------------------------------
ANS2751E

The RESTORE VM command failed because the Data Protection for VMware
license file does not exist or is not valid.



Explanation:

The Data Protection for VMware license file is required for the RESTORE
VM command.

System action:

The command is not processed.

User response:

Install Data Protection for VMware or the license file for Data
Protection for VMware, and retry the command. Or retry the operation
from a host that has the Data Protection for VMware license file
installed.

------------------------------------------------------------------------
ANS2752E

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



Explanation:

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

System action:

The command is not processed.

User response:

Install Data Protection for Microsoft Hyper-V or the license file for
Data Protection for Microsoft Hyper-V, and retry the command. Or retry
the operation from a host that has the Data Protection for Microsoft
Hyper-V license file installed.

------------------------------------------------------------------------
ANS2753I

Establishing inter-client communication with node node(s).



Explanation:

None.

System action:

This message is informational.

User response:

None.

------------------------------------------------------------------------
ANS2785I

Gathering current Db2 configuration for 'type' restore.



Explanation:

None.

System action:

This message is informational.

User response:

None.

------------------------------------------------------------------------
ANS2790E

Error Accessing Storage Virtual Machine 'svm_name' on NetApp Filer
'filer_name'.



Explanation:

The specified Storage Virtual Machine could not be accessed on the
specified filer. Make sure that the storage virtual machine exists and
is running on the specified filer and that the storage virtual machine
has been correctly associated with the filer with the SET NETAPPSVM
command.

System action:

Processing stops.

User response:

Make sure that the storage virtual machine is running on the specified
filer and that the association between the filer and the storage virtual
machine has been defined correctly with the dsmc set netappsvm command.

------------------------------------------------------------------------
ANS2798E

Unable to start a session from client node 'nodename' multi-node
'multi-node' to client at address 'ip-address:ip-port'. The return code
is rc.



Explanation:

None.

System action:

This message is informational.

User response:

None.

------------------------------------------------------------------------
ANS2799E

An error was encountered during a session with another client. Check the
error log for any additional information



Explanation:

This message is reserved for DB2 UDB.

System action:

Reserved.

User response:

This message is reserved for DB2 UDB.

------------------------------------------------------------------------
ANS2800W

No IBM Spectrum Protect processes were found.



Explanation:

The QUERY PIDS command was unable to identify any known IBM Spectrum
Protect processes running on the system. If the -FILTER option was used,
no processes matching the filter specification were found.

System action:

None.

User response:

If you need to use dsmtrace to enable or disable tracing for a running
client process, make sure that the client is already running. If you
used the -FILTER option, try the command again with a different filter
specification. You can use -FILTER=* to display all processes running on
the system.

------------------------------------------------------------------------
ANS2801E

The dsmtrace utility was unable to connect to the specified process.



Explanation:

This message typically occurs when the specified process ID is not
active.

System action:

None.

User response:

If you need to use dsmtrace to enable or disable tracing for a running
client process, make sure that the client is already running. Use the
dsmtrace QUERY PIDS command to identify running client processes, then
try the command again.

------------------------------------------------------------------------
ANS2802I

Tracing has been disabled.



Explanation:

None.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS2803E

Tracing could not be disabled.



Explanation:

A problem occurred while trying to disable tracing for the specified
process. This message is usually accompanied by other, more specific
messages immediately preceding or following this message.

System action:

No changes are made to the trace status of the specified process.

User response:

Review the messages that immediately precede or follow this message for
further information about this error.

------------------------------------------------------------------------
ANS2804W

Tracing is already enabled. -TRACEFILE, -TRACEMAX, and -TRACESEGSIZE are
ignored.



Explanation:

When tracing is already enabled for a client process, only the
-TRACEFLAGS option has any effect.

System action:

The -TRACEFLAGS options are set on the client process. -TRACEFILE,
-TRACEMAX, and -TRACESEGSIZE are ignored.

User response:

If you need to modify the -TRACEFILE, -TRACEMAX, or -TRACESEGSIZE
settings, you must first use the dsmtrace DISABLE command to disable
tracing for the client process. Then run the dsmtrace ENABLE command to
configure the desired trace settings. If it is not necessary to modify
these settings, then this message may be ignored.

------------------------------------------------------------------------
ANS2805I

Tracing has been enabled.



Explanation:

None.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS2806E

Tracing could not be enabled.



Explanation:

A problem occurred while trying to enable tracing for the specified
process. This message is usually accompanied by other, more specific
messages immediately preceding or following this message.

System action:

No changes are made to the trace status of the specified process.

User response:

Review the messages that immediately precede or follow this message for
further information about this error.

------------------------------------------------------------------------
ANS2807E

An incorrect number of parameters was specified for the command-name
command.



Explanation:

The specified command was invoked with too few or too many parameters.

System action:

The command is not processed.

User response:

Try the command again with the correct number of parameters. Run
\"dsmtrace help\" for additional information on dsmtrace command syntax.

------------------------------------------------------------------------
ANS2808W

Incremental by snapshot difference backup did not locate the registered
base snapshot 'regbase-name' on NetApp/N-Series filer volume
'volume-name'. Snapshot 'olderbase-name' is used as the base snapshot.



Explanation:

Incremental by snapshot difference backup did not locate the specified
registered base snapshot on the specified NetApp/N-Series filer volume.
The most recent existing snapshot which is older than the registered
base snapshot is used as the current base snapshot.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS2809E

The backupid 'backupid:' in the input file does not match the vmname
'vmname:' being restored.



Explanation:

There is a discrepency between the backupid and vmname specified in the
input file

System action:

The virtual machine cannot be restored.

User response:

Confirm that the backupid specified matches the vmname you are
attempting to restore by re-running the inquire_detail command and make
any necessary corrections before attempting the restore again.

------------------------------------------------------------------------
ANS2810E

The IBM Spectrum Protect for Virtual Environments Input File 'input
file:' appears to be empty.



Explanation:

While processing the Input File no items were found to operate on.

System action:

The operation cannot continue with an empty list.

User response:

Confirm that the input file is not empty and has valid input. If the
file is not empty it may be that an error occurred while reading the
file, please check the error log for any errors found during the reading
of the file. If errors are found make the necessary corrections before
attempting the operation again.

------------------------------------------------------------------------
ANS2811E

The IBM Spectrum Protect for Virtual Environments could not find a
suitable datamover agent for the DataCenter Node 'datacenter nodename'.



Explanation:

While processing Proxy relationships with the DataCenter Node specified,
no appropriate datamover matches detected

System action:

The operation cannot continue without a valid datamover.

User response:

Work with your IBM Spectrum Protect Administrator to ensure that your
DataCenter Nodes have granted proxy authority to your DataMover Nodes.

------------------------------------------------------------------------
ANS2812E

The IBM Spectrum Protect for Virtual Environments could not find
Datamover node named 'datamover nodename' on the IBM Spectrum Protect
Server.



Explanation:

While processing Proxy relationships with the DataCenter node and
DataMover node specified, no appropriate Datamover node name matches
detected.

System action:

The operation cannot continue without a valid Datamover Node name.

User response:

Make sure the Datamover node name specified is a valid IBM Spectrum
Protect node name and that the node has the proper proxy relationships
established.

------------------------------------------------------------------------
ANS2813E

The IBM Spectrum Protect Server returned an empty network address or
port number for 'datamover nodename'.



Explanation:

While querying the IBM Spectrum Protect Server for the Datamover network
address and port number, the Server returned zero for one of the values.

System action:

The operation cannot continue without a valid Datamover network address
and port number.

User response:

This is usually the result of a Datamover Node not being started. Log on
to the Datamover host and start or restart the DSMCAD service and retry
the IBM Spectrum Protect for Virtual Environments command again. If the
problem persists, work with your IBM Spectrum Protect Server
Administrator to inspect the IBM Spectrum Protect Server activity log to
identify the issue.

------------------------------------------------------------------------
ANS2814E

IBM Spectrum Protect for Virtual Environments detected an error while
parsing the Input File 'input file'. The 'specifier' appears to be empty
or invalid.



Explanation:

While parsing the Input File an error occurred.

System action:

The operation cannot continue without valid virtual machine
specifications.

User response:

This is usually the result of an empty virtual machine name or other
identifier. Please check that the syntax of the Input File is correct
for all entries and that virtual machine names are not empty and retry
the operation.

------------------------------------------------------------------------
ANS2815E

IBM Spectrum Protect for Virtual Environments detected an error while
parsing 'read in line' from the Input File 'input file'.



Explanation:

While parsing the Input File an error occurred.

System action:

The operation cannot continue without valid specifications in the Input
File.

User response:

This may be the result of an empty virtual machine name or other
identifier. Please check that the syntax of the Input File is correct
for all entries and that virtual machine names are not empty and retry
the operation.

------------------------------------------------------------------------
ANS2816E

IBM Spectrum Protect for Virtual Environments detected that the IBM
Spectrum Protect Server IP address was not 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
IBM Spectrum Protect Server.

User response:

This may be a result of the VMCLI profile having an empty
VE_TSM_SERVER_NAME entry. Please check that the VMCLI profile is
configured correctly specifying the IBM Spectrum Protect Server address.

------------------------------------------------------------------------
ANS2817E

IBM Spectrum Protect for Virtual Environments detected that the vCenter
Command-Line interface node name was not specified.



Explanation:

While parsing the command line options, an empty vCenter Command-Line
interface node name was detected.

System action:

The operation cannot continue without a valid vCenter Command-Line
interface node name.

User response:

This may be a result of the VMCLI profile having an empty
VE__TSMCLI_NODE_NAME entry. Please check that the VMCLI profile is
configured correctly specifying the vCenter Command-line interface node
name.

------------------------------------------------------------------------
ANS2818E

IBM Spectrum Protect for Virtual Environments detected that the IBM
Spectrum Protect Server port was not specified.



Explanation:

While parsing the command line options, an empty IBM Spectrum Protect
Server port was detected.

System action:

The operation cannot continue without a valid IBM Spectrum Protect
Server port.

User response:

This may be a result of the VMCLI profile having an empty
VE_TSM_SERVER_PORT entry. Please check that the VMCLI profile is
configured correctly specifying the IBM Spectrum Protect Server port.

------------------------------------------------------------------------
ANS2820E

An interrupt has occurred. The current operation will end and the client
will shut down.



Explanation:

This message is issued when the process is interrupted by a break signal
such as CTRL-BREAK or CTRL-C.

System action:

The operation and process are ended immediately.

User response:

Restart the operation if desired.

------------------------------------------------------------------------
ANS2821E

The CAD service is not running for data mover node named 'datamover
nodename'.



Explanation:

The CAD service is not running for the data mover.

System action:

The operation cannot continue without a connection to the data mover CAD
service.

User response:

Make sure the data mover CAD service is running and that the node has
the proper proxy relationships established.

------------------------------------------------------------------------
ANS2822E

The data mover is unable to connect to the IBM Spectrum Protect server.



Explanation:

There is no connection the specified IBM Spectrum Protect server.

System action:

The operation cannot continue without a connection to the server.

User response:

Possible causes are that the server name is spelled incorrectly in the
dsm.opt or dsm.sys file; an incorrect server is being used; a
communications failure or firewall issue occurred; or the network cable
is unplugged.

------------------------------------------------------------------------
ANS2824E

IBM Spectrum Protect for Virtual Environments detected that the node
name representing the vCenter is not specified.



Explanation:

While parsing the command line options, an empty vCenter node name was
detected.

System action:

The operation cannot continue without a valid vCenter node name.

User response:

This may be a result of the VMCLI profile having an empty
VE_VCENTER_NODE_NAME entry. Please check that the VMCLI profile is
configured correctly specifying the vCenter node name.

------------------------------------------------------------------------
ANS2825E

IBM Spectrum Protect for Virtual Environments detected that the node
name representing the Datacenter is not specified.



Explanation:

While parsing the command line options, an empty datacenter node name
was detected.

System action:

The operation cannot continue without a valid datacenter node name.

User response:

This is a result of the -d DataCenter Node Name not being passed in to
the Command-line. Re-try the operation making sure to pass the -d
Datacenter Node Name to the command-line call.

------------------------------------------------------------------------
ANS2826E

IBM Spectrum Protect for Virtual Environments detected that the node
name representing the vCenter Datamover is not specified.



Explanation:

While parsing the command line options, an empty Datamover node name was
detected.

System action:

The operation cannot continue without a valid Datamover node name.

User response:

This is a result of the -o Datamover Node Name not being passed in to
the Command-line. Re-try the operation making sure to pass the -o
Datamover Node Name to the command-line call.

------------------------------------------------------------------------
ANS2827E

IBM Spectrum Protect for Virtual Environments detected that the input
file 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 without a valid input file name.

User response:

This is a result of the -I Inputfile name not being passed in to the
Command-line. Re-try the operation making sure to pass the -I input file
name to the command-line call.

------------------------------------------------------------------------
ANS2828E

Image operations are not supported for the specified file system.



Explanation:

Image backup and restore are not supported for the specified file
system.

System action:

The requested image operation is not performed.

User response:

Choose another object.

------------------------------------------------------------------------
ANS2829E

Image operations are not supported for GPFS.



Explanation:

Image backup and restore are not supported for GPFS volumes.

System action:

The requested image operation is not performed.

User response:

Choose another object.

------------------------------------------------------------------------
ANS2830E

An incorrect number of parameters was specified.



Explanation:

The specified command was invoked with too few or too many parameters.

System action:

Processing stops.

User response:

Try the command again with the correct number of parameters.

------------------------------------------------------------------------
ANS2831E

Incremental by snapshot difference cannot be performed on 'volume-name'
as it is of type 'type' and is not a NetApp/N-Series 'fsType' volume.



Explanation:

The volume specified cannot be used for performing NetApp/N-Series
snapshot difference incremental operation. The volume does not
correspond to the NFS mount point or the CIFS shared drive for a Network
Appliance or N-Series NAS volume. One possible reason for this failure
is that snapshot difference incremental backups can only be performed
against NetApp/N-Series NFS volumes on AIX/Linux platforms, or CIFS
volumes on Windows platforms.

Another possible reason for this failure is that the qtree security
style for the volume was incorrectly selected. If the CIFS volume is
mapped on Windows, ensure that the security style is set to NTFS. If the
volume is mounted as NFS, ensure that the security style is set to UNIX.

System action:

Processing stops.

User response:

Try the command again with a NetApp/N-Series NFS or CIFS volume with the
correct security style.

------------------------------------------------------------------------
ANS2832E

Incremental by snapshot difference failed for filespace name. See the
error log for details.



Explanation:

Failed to perform NAS NFS/CIFS Incremental by snapshot difference
operation.

System action:

Processing stops.

User response:

Take appropriate action based on the information in the error log. If
the problem persists please contact your IBM Spectrum Protect
administrator.

------------------------------------------------------------------------
ANS2834E

You have to be a root user in order to perform incremental backup using
snapshot difference.



Explanation:

Failed to perform NAS NFS/CIFS incremental backup operation using
snapshot difference as the user was non root.

System action:

Processing stops.

User response:

Please retry the operation as root user.

------------------------------------------------------------------------
ANS2835E

Incremental backup using snapshot difference is not supported on this
platform.



Explanation:

NetApp NFS/CIFS incremental backup operation using snapshot difference
is only supported on Linux and Windows platforms.

System action:

Processing stops.

User response:

Retry the incremental operation without the snapdiff option.

------------------------------------------------------------------------
ANS2836E

Incremental backup operation using snapshot difference is only available
for full volumes. is a partial volume or qtree.



Explanation:

Cannot perform NAS NFS/CIFS incremental backup operation using snapshot
difference on the mounted or mapped volume due to one of the following
reasons: 1) The volume is actually a qtree. 2) The volume is not a full
volume, it is not mounted or mapped to the root of the volume.

System action:

Processing stops.

User response:

Retry the incremental backup operation by specifying an entire NAS NFS
or CIFS volume.

------------------------------------------------------------------------
ANS2837E

Unable to access the required stored NetApp filer credentials (user id
and password) for filer ''. Make sure the SET PASSWORD -TYPE=FILER
command was specified correctly to store the credentials.



Explanation:

The user id and password for the specified NetApp Filer have been either
not configured or have been specified incorrectly.

System action:

Processing stops.

User response:

Use the 'set password -type=filer' command to define the user id and
password for the specified NetApp Filer and retry the snapshot
differential backup operation.

------------------------------------------------------------------------
ANS2838W

The file path 'filename' exceeds HSM maximaum path length.



Explanation:

A file that you tried to migrate has a path name that is too long.

System action:

File skipped from migration.

User response:

Place files into a shorter path to make them available for migration.

------------------------------------------------------------------------
ANS2839E

Failed with ONTAPI error 'error_code' while connecting to NetApp Filer
'filer_name' using user id 'id_name'. You might have provided
credentials incorrectly for this Filer.



Explanation:

The user ID and password have been configured incorrectly for the
specified Filer.

If you are using the snapdiffhttps option, ensure that you are not
specifying vFiler volumes as vFiler does not support the HTTPS transport
type.

System action:

Processing stops.

User response:

Make sure that the credentials you have specified for the Filer are the
correct ones. Use the dsmc set password command to specify the correct
credentials for your Filer and try the command again.

------------------------------------------------------------------------
ANS2840E

Incremental backup using snapshot difference is not supported for NetApp
file server 'file-server-name' at Data ONTAP version
'version.modification.submodification'.



Explanation:

The file server specified is not at the Data ONTAP version that supports
snapshot difference API. Current supported versions of Data ONTAP are
7.3 - 9.8.

System action:

Processing stops.

User response:

Upgrade the file server to supported Data ONTAP version and retry the
operation.

------------------------------------------------------------------------
ANS2841E

Incremental by snapshot difference is only supported on AIX 64 bit and
Linux 86 bit clients.



Explanation:

Incremental backup using snapshot difference feature is only available
on IBM Spectrum Protect AIX 64 bit and Linux 86 clients.

System action:

Processing stops.

User response:

Try the command again with an IBM Spectrum Protect AIX 64 bit or Linux
86 client.

------------------------------------------------------------------------
ANS2842E

IBM Spectrum Protect for Virtual Environments detected an error with the
createsnap: keyword. createsnap:yes is specified while also specifying
vmsnapname:VMWare Snapshot Name.



Explanation:

While parsing the Input File for FlashCopy Manager for VMWare offload
backup, an error condition was detected with VM Ware snapshot handling.
Specifying a VMWare Snapshot name while specifying createsnap:yes is not
allowed.

System action:

The operation cannot continue without specifying the correct createsnap:
and vmsnapname: combination.

User response:

This is a result of the -I Inputfile containing conflicting input for
createsnap: and vmsnapname: keywords. If you intend to have IBM Spectrum
Protect for Virtual Environments use a VMWare Snapshot created by
FlashCopy Manager then specify createsnap:no with a valid VMWare
Snapshot for the vmsnapname: keyword.

------------------------------------------------------------------------
ANS2850E

Error Creating Snapshot: Volume NAS volume is a snapmirror destination
volume.



Explanation:

An attempt was made to create a snapshot on a read only snapmirror
destination volume.

System action:

Processing stops.

User response:

Rety the operation using the USEEXISTINGBASE and DIFFSNAPSHOT=latest
options.

------------------------------------------------------------------------
ANS2851E

Snapshot Processing Error: .



Explanation:

An error occurred due to the reason specified in the message

System action:

Processing stops.

User response:

Ensure that the specified volume is online and allows write access.

------------------------------------------------------------------------
ANS2855W

IBM Spectrum Protect for Virtual Environments detected an error while
parsing the Input File 'input file'. The 'specifier' should not be
specified when using 'specifier'. Option will be ignored.



Explanation:

While parsing the Input File an error occurred.

System action:

The operation will continue ignoring this parameter.

User response:

This is usually the result of an identifier used with the wrong option.
Please check that the options in the Input File matches the requested
operation and retry the operation.

------------------------------------------------------------------------
ANS2856E

IBM Spectrum Protect for Virtual Environments detected that the node
name representing the vCloud is not specified.



Explanation:

A node name that represents the vCloud is not specified in the VMCLI
profile.

System action:

The operation cannot continue without a valid vCloud node name.

User response:

Specify the vCloud node name in the VE_VCENTER_NODE_NAME parameter in
the VMCLI profile. Then, try the operation again.

------------------------------------------------------------------------
ANS2857E

IBM Spectrum Protect for Virtual Environments 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 missing from the input file.

System action:

The operation stops.

User response:

This may be the result of a missing option or identifier. Verify that
the syntax of the command and the syntax of the values in the input file
are correct. Then, try the operation again.

------------------------------------------------------------------------
ANS2858E

Failed to get the list of available VMs for backup



Explanation:

Failed to get the entire list of VMs in order to choose ones that needed
to be backed up.

System action:

The operation was stopped

User response:

Verify that configuration parameters for connection to vCenter.

------------------------------------------------------------------------
ANS2859E

Failed to locate the Organization VDC node that is used to store the
backed up data.



Explanation:

The Organization VDC node that stores the backed up vApp data was not
located. This node must be mapped to the Provider VDC node. This issue
might be caused by invalid mapping between the Provider VDC node and the
Organization VDC node.

System action:

The operation was stopped

User response:

Go to the Configuration page and click 'Run the Configuration Wizard' to
verify that mapping information for the Provider VDC node is valid.

------------------------------------------------------------------------
ANS2860E

The PRESNAPSHOTCMD command failed. The snapshot differential backup will
not be executed.



Explanation:

The command specified by the PRESNAPSHOTCMD option must complete
successfully in order to execute the snapshot differential backup. If
the command completed with a return code of 0 (zero), it is considered
to have completed successfully. If the command completed with any other
return code, it is considered to have failed. If the command failed then
the snapshot differential backup is not executed.

System action:

The client does not execute the snapshot differential backup operation.

User response:

Identify and repair the problem that caused the command to fail. If a
non-zero return code is normal for this command, then consider wrapping
the command in a script that always exits with a return code of zero.

------------------------------------------------------------------------
ANS2861W

The POSTSNAPSHOTCMD command failed.



Explanation:

If the command specified by the POSTSNAPSHOTCMD option completed with a
non-zero return code, the snapshot differential backup operation
continues. The operation continues with a warning-level result. The
result of the POSTSNAPSHOTCMD command does not supersede a higher result
from the snapshot differential backup command. For example, if the
snapshot differential backup command completed with code 12, a lower
return code from the POSTSNAPSHOTCMD command does not alter the return
code.

System action:

The snapshot differential 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.
Consider wrapping the command in a script that always exits with a
return code of zero.

------------------------------------------------------------------------
ANS2862E

No entry found for the specified Storage Virtual Machine.



Explanation:

The SVM does not exist in the registry or password file.

System action:

No operation is performed.

User response:

The user should register the SVM using the Set NetAppSVM command.

------------------------------------------------------------------------
ANS2863E

The backup-archive client failed to load the vCloud protection runtime
library.



Explanation:

vCloud protection runtime library is not loaded by the backup-archive
client.

System action:

The operation is stopped

User response:

Verify that the vCloud runtime library exist in the 'plugins' folder
under the client installation folder.

------------------------------------------------------------------------
ANS2864E

A Hyper-V operation was attempted, but the Hyper-V role was not detected
on the host system.



Explanation:

The Hyper-V role must be enabled on the host system where the Hyper-V
operation occurs. The current host system either does not have the
Hyper-V role enabled or does not support Hyper-V.

System action:

The operation does not start.

User response:

If the host system supports Hyper-V then enable the Hyper-V role.
Otherwise, try the operation again from a host system that supports
Hyper-V and has the Hyper-V role enabled.

If you want to process VMware virtual machines, go to the IBM Spectrum
Protect window, and click Edit > Client Preferences > VM Backup. Click
VMWare Full VM or VMWare File Level. Then, click OK.

------------------------------------------------------------------------
ANS2865E

An error occurred creating or accessing a virtual disk for virtual
machine 'VM-name'.



Explanation:

An error occurred creating or accessing a virtual disk while restoring a
virtual machine.

System action:

The virtual machine is not restored.

User response:

See the client error log for more detailed information about the error.

------------------------------------------------------------------------
ANS2866E

An error occurred creating virtual machine 'VM-name'.



Explanation:

An error occurred creating the virtual machine during the restore
operation.

System action:

The virtual machine is not restored.

User response:

See the client error log for more detailed information about the error.

------------------------------------------------------------------------
ANS2867E

An error occurred querying virtual machine 'VM-name'.



Explanation:

An error occurred querying the virtual machine during the restore
operation.

System action:

The virtual machine is not restored.

User response:

See the client error log for more detailed information about the error.

------------------------------------------------------------------------
ANS2868E

An error occurred removing virtual machine 'VM-name'.



Explanation:

An error occurred removing the virtual machine during the restore
operation.

System action:

The virtual machine is not restored.

User response:

See the client error log for more detailed information about the error.

------------------------------------------------------------------------
ANS2869E

A virtual machine on the hypervisor has a different name but the same ID
as virtual machine to restore 'VM-name' has. Restore not allowed.



Explanation:

A virtual machine with a different name and the same ID than the virtual
machine being restored exists on the hypervisor.

System action:

The virtual machine is not restored.

User response:

Choose a different virtual machine to restore to or delete the existing
virtuual machine.

------------------------------------------------------------------------
ANS2870W

An incremental backup of virtual machine 'vmname' was requested, but the
virtual machine lacks an existing recovery snapshot. A full backup will
be taken to prevent data loss.



Explanation:

Removal of the recovery snapshot of a virtual machine does not reset the
last successful backup time maintained internally. The lack of a reset
creates an inconsistency between the backup time and the hard disk
configuration of the virtual machine. A full backup fixes the ambiguity
and prevent data loss.

System action:

An inconsistency in the virtual machine configuration was detected.

User response:

Avoid deleting the recovery snapshot between back up operations.

------------------------------------------------------------------------
ANS2872E

The process was unable to restore a virtual disk user metadata entry of
virtual machine 'vmname' to disk 'diskpath'.



Explanation:

An attempt to restore a user metadata entry of a disk failed. The user
metadata of the disk may inaccessible or unreachable.

System action:

A restore of a virtual disk.

User response:

Check the user privileges include access to virtual disk writes or move
the disk to an accessible location.

------------------------------------------------------------------------
ANS2873I

Virtual machine 'vmname' was successfully restored. If this virtual
machine was restored to a cluster, ensure that the cluster settings
enable the restored virtual machine to operate in high availability
mode. High availability settings, and the preferred set of hypervisor
nodes that can operate in high availability mode, might not be set
automatically.



Explanation:

The specified virtual machine has been restored, but the restore process
does not alter Microsoft Failover Clustering High Availability settings.
If you restored a virtual machine that you previously deleted, or if you
restored a virtual machine to a new name and location, the restored
virtual machine might not be enabled as a high availability resource.
Enable high availability for this virtual machine by using Microsoft
Failover Cluster Manager, System Center Virtual Machine Manager, or by
using PowerShell cmdlets.

System action:

Processing continues.

User response:

Use Microsoft Failover Cluster Manager, System Center VM manager, or
PowerShell to configure the cluster to allow this virtual machine to
perform in a high availability configuration.

------------------------------------------------------------------------
ANS2876E

Unable to access the required stored NetApp Management Filer credentials
(user id and password) for filer '' associated with storage virtual
machine '' . Make sure the SET PASSWORD -TYPE=FILER command was
specified correctly to store the credentials.



Explanation:

The user id and password for the specified NetApp management filer
associated with the specified storage virtual machine have been either
not configured or have been specified incorrectly.

A storage virtual machine is associated with management filer using the
SET NETAPPSVM command. Credentials for a management filer are stored
with the SET PASSWORD -TYPE=FILER command.

System action:

Processing stops.

User response:

Use the 'set password -type=filer' command to define the user id and
password for the specified NetApp Management Filer. Use the 'set
netappsvm' command to associated a storage virtual machine with a
management filer. Ensure that both of these commands were specified
correctly and retry the snapshot differential backup operation.

------------------------------------------------------------------------
ANS2877I

Restart action for cluster resource 'resourceName' is changed from
'oldValue' to 'newValue'



Explanation:

The specified virtual machine is configured for high availability, but
must be deleted before it is restored. To prevent the cluster service
from attempting a failover of the virtual machine to another cluster
node, IBM Spectrum Protect sets the RestartAction policy of the
indicated cluster resource to "ClusterResourceDontRestart". After the
restore is finished, IBM Spectrum Protect sets the RestartAction to its
original value.

System action:

Processing continues.

User response:

Usually no further user action is required. However, if the restore
operation is interrupted and subsequently restarted, then after the
restore is finished, the RestartAction policy of the resource must be
manually updated to its original value. In that case, use the
information in this message to update the RestartAction policy to the
original value.

------------------------------------------------------------------------
ANS2878E

Failed to change restart action for cluster resources 'resourceName'
from 'oldValue' to 'newValue'



Explanation:

IBM Spectrum Protect was unable to alter the "RestartAction" policy of
the specified cluster resource. The specified virtual machine is
configured for high availability, but must be deleted before it is
restored. To prevent the cluster service from attempting a failover of
the virtual machine to another cluster node, IBM Spectrum Protect tries
to set the RestartAction policy of the indicated resource to
"ClusterResourceDontRestart". After the restore is finished, IBM
Spectrum Protect tries to set the RestartAction to its original value.
However, an attempt to alter the RestartAction policy was unsuccessful.

System action:

Processing continues.

User response:

After the restore is finished, the RestartAction policy of the resource
must be manually changed to its original value. Use the information in
this message to update the RestartAction policy to its original value.

------------------------------------------------------------------------
ANS2888E

Backup VM Full VM Incremental is unable to run. A valid IBM Spectrum
Protect for Virtual Environments license file (license-file) cannot be
located.



Explanation:

The license file was not found, or cannot be opened because of
permissions, or the file is corrupted.

System action:

The system returns to the calling procedure.

User response:

Check permissions on file. See if the license file is in the correct
place.

------------------------------------------------------------------------
ANS2889I

The vApp 'vapp name' was successfully restored under the name 'new vapp
name'



Explanation:

The restore operation was succesful in restoring the vApp into the
specified name.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS2890E

The file to restore already exist and the number of copies with same
backup date has been reached on the specified target location!



Explanation:

On the specified target location the file to restore already exist, a
copy of the file with appended the backup date exist and the number of
files with same backup date has been reached.

System action:

The file is skipped.

User response:

Check on the target location if copies of the same file can be removed
or restore the file to a different location.

------------------------------------------------------------------------
ANS2891W

The vApp 'vapp name' was successfully restored. However, failed vms num
out of existing vms num VMs were not restored.



Explanation:

Although the vApp restore operation on the vCloud completed
successfully, one or more VMs were not restored.

System action:

The operation completed successfully. However, some VMs were not
restored.

User response:

Check the dsmerror.log file for information about why the VMs were not
restored. Then, try the operation again. If the problem persists, visit
the IBM Support Portal for additional information at
http://www.ibm.com/support/entry/portal/.

------------------------------------------------------------------------
ANS2900E

IBM Spectrum Protect for Virtual Environments detected that the scan
domain was not specified.



Explanation:

While parsing the command line options, no scan domain was detected.
This error occurred because the -domain option was not specified.

System action:

The operation cannot continue without a valid scan domain.

User response:

Run the operation again and specify the -domain option.

------------------------------------------------------------------------
ANS2901E

IBM Spectrum Protect for Virtual Environments detected that the domain
user was not specified.



Explanation:

While parsing the command line options, no domain user was detected.
This error occurred because the -user option was not specified.

System action:

The operation cannot continue without a valid domain user.

User response:

Run the operation again and specify the -user option.

------------------------------------------------------------------------
ANS2902E

Save domain password failed in function func-name with return code
return-code.



Explanation:

An unexpected write access error occurred when the function tried to
save the domain password. Write access does not exist to either the
registry or to the IBM Spectrum Protect for Virtual Environments on
Linux installation folder where the password file is saved.

System action:

The operation ends.

User response:

Grant write access to either the registry or to the IBM Spectrum Protect
for Virtual Environments on Linux installation folder and try the
operation again.

------------------------------------------------------------------------
ANS2903E

Read domain password failed in function func-name with return code
return-code.



Explanation:

An unexpected error occurred when the function tried to read the domain
password.

System action:

The operation ends.

User response:

On Windows, verify that the password exists in the registry. On Linux,
verify that the password exists in the password file. Try the operation
again.

------------------------------------------------------------------------
ANS2998I

The option 'option' that was found in the include/exclude file
'file-name' at the line number: number is not supported and will be
ignored by the client.



Explanation:

The specified option is valid but not supported on the current platform
and will be ignored by the client.

System action:

Processing continues.

User response:

You can ignore the message or remove the option from the include/exclude
file.

------------------------------------------------------------------------
ANS3000I

communication-type communications available on port port-number.



Explanation:

The specified communications are available on the specified port number.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS3001W

The default locale, English (United States), is used because the
selected locale "locale" is not supported. The supported locales are as
follows: supportedLocales



Explanation:

The locale on the user's system or browser is not supported.

System action:

The system defaults to the English (United States) locale.

User response:

Use the default locale or switch to one of the supported locales.

------------------------------------------------------------------------
ANS3002I

Session started for user userid (communication-method address).



Explanation:

A session was started for the specified user.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS3003I

The new password is case sensitive.



Explanation:

Your account has been updated to use case sensitive password.

System action:

None

User response:

Make sure to remember the new password as you enter it, including
character casing. For more details, contact your IBM Spectrum Protect
administrator.

------------------------------------------------------------------------
ANS3004E

Session for user userid terminated - invalid password entered.



Explanation:

A session was terminated for the specified user because an invalid
password was entered.

System action:

The session with the specified user is terminated.

User response:

Re-start the remote client and enter the correct password for the
specified user.

------------------------------------------------------------------------
ANS3005I

Session for user userid terminated - idle for idle-minutes minutes.



Explanation:

A session was terminated for the specified user because there was no
activity on the session for the specified number of minutes.

System action:

The session with the specified user is terminated.

User response:

Re-start the remote client to begin a new session.

------------------------------------------------------------------------
ANS3006I

Processing request for the IBM Spectrum Protect Web Client (ip-address).



Explanation:

A request for the Web Client is being processed.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS3007I

IBM Spectrum Protect client-name terminating - idle for idle-minutes
minutes.



Explanation:

The specified client is terminating because it has been idle for the
specified time. It will be automatically started when it is needed.

System action:

The client program stops.

User response:

None.

------------------------------------------------------------------------
ANS3008E

Too many symbolic links were detected while resolving name 'file_name'



Explanation:

While trying to resolve the file name, too many symbolic links were
found.

System action:

File skipped.

User response:

Ensure that you do not have a looping symbolic link for the file.

------------------------------------------------------------------------
ANS3009E

The Logical Volume Snapshot Agent plugin library was not found.



Explanation:

The Logical Volume Snapshot Agent (LVSA) plugin library should have been
installed when the client was installed, but it cannot be found.

System action:

The selected operation is not performed.

User response:

Try the operation again. If the problem recurs, re-install the IBM
Spectrum Protect client software. If the problem persists, contact IBM
technical support for further assistance.

------------------------------------------------------------------------
ANS3010E

The snapshot wizard operation failed.



Explanation:

The snapshot wizard operation failed with a non-zero return code. Check
the error log for additional information.

System action:

The selected operation is not performed.

User response:

Review the error log for any error messages, and then retry the
operation after correcting the cause for failure.

------------------------------------------------------------------------
ANS3011E

Previous changes have not been commited. The machine must be rebooted
before this operation can be performed



Explanation:

A previous operation required the machine to be rebooted for the changes
to take effect, but the machine has not been rebooted. The machine must
be rebooted before this selected operation can be performed.

System action:

The selected operation is not performed.

User response:

Reboot the machine and then retry the operation.

------------------------------------------------------------------------
ANS3012E

The Logical Volume Snapshot Agent is not installed. Use the Setup Wizard
to configure either Online Image or Open File support and choose the
Logical Volume Snapshot Agent as the snapshot provider.



Explanation:

The selected operation requires the Logical Volume Snapshot Agent, but
it is not installed. Use the Setup Wizard to install the LVSA.

System action:

The selected operation is not performed.

User response:

Retry the operation after installing the Logical Volume Snapshot Agent.

------------------------------------------------------------------------
ANS3013E

The specified snapshot provider is not supported on this version of the
operating system.



Explanation:

The specified snapshot provider is not supported on the version of the
operating system you are currently running. If another snapshot provider
is available, select it and retry the operation.

System action:

The selected operation is not performed.

User response:

If another snapshot provider is available, select it and retry the
operation.

------------------------------------------------------------------------
ANS3014E

Expose snapshot failed for backup document 'xml-backup-doc-file'.



Explanation:

Expose snapshot failed.

System action:

Processing stops

User response:

See the dsmerror.log file for further details.

------------------------------------------------------------------------
ANS3015I

communication-type communications not available on port port-number due
to port being in use. Select the unique port in the options file.



Explanation:

The specified communications not available on the port number being in
use.

System action:

The acceptor service stopped. Define the unique port number. Restart the
Acceptor service.

User response:

Define the unique port numbers for every service.

------------------------------------------------------------------------
ANS3016W

Journaled file system filespace is no longer available to the journal
service. Changes to this file system are not journaled until the file
system is brought online. Check the the system to determine why the file
system is not available.



Explanation:

The journal service periodically checks that the file system is still
available. The frequency of the check is determined by the
DeferRetryInterval setting in the tsmjbbd.ini file. This message is
displayed when the journal service loses the connection to the disk.

System action:

The journal service periodically checks if the disk comes back online.
The frequency of the check is determined by the DeferRetryInterval
setting in the tsmjbbd.ini file.

User response:

Check the system to determine why the file system is unavailable. Next
actions depend why the disk is unavailable. For example, if the disk was
quickly removed and then reinserted, no further action might be
necessary. If the disk was replaced or reformatted, you might need to
restore the disk before resuming backup operations.

------------------------------------------------------------------------
ANS3017W

Attempting to restart the file system monitor for filesystem.



Explanation:

The journal service tries to restart the file system monitor for a file
system that unexpectedly became unavailable.

System action:

The journal service tries to restart the file system monitor for a file
system that unexpectedly became unavailable.

User response:

Check the system to determine why the file system is unavailable. Next
actions depend why the disk is unavailable. For example, if the disk was
quickly removed and then reinserted, no further action might be
necessary. If the disk was replaced or reformatted, you might need to
restore the disk before resuming backup operations.

------------------------------------------------------------------------
ANS3018I

Journaled file system filespace is online.



Explanation:

The journal service periodically checks that the file system is still
unavailable. The frequency of the check is determined by the
DeferRetryInterval setting in the tsmjbbd.ini file. This message is
displayed when the journal service get the connection to the disk again.

System action:

None.

User response:

Check the system to determine why the file system was unavailable. Next
actions depend why the disk was unavailable. For example, if the disk
was quickly removed and then reinserted, no further action might be
necessary. If the disk was replaced or reformatted, you might need to
restore the disk before resuming backup operations.

------------------------------------------------------------------------
ANS3019W

Multiple Snapshots found with same GUID. GUID:guid.



Explanation:

During a VSS Query operation, multiple snapshots with the same GUID were
found. Its likely one is a orpahan

System action:

Operation continues

User response:

Use a tool such as VssAdmin to inspect the snapshots on your server.
Remove any that are invalid.

------------------------------------------------------------------------
ANS3100E

Unable to get the iSCSI initiator name. The Windows error is (error)



Explanation:

The iSCSI initiator name is not configured on the system.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation about how to configure the
iSCSI initiator name.

------------------------------------------------------------------------
ANS3101E

The mount operation for virtual machine 'vmname' failed with rc =
return-code. For more details, check the Recovery Agent logs.



Explanation:

An error occurred during the mount operation. See the output from the
previous operation to identify the cause of the error.

System action:

Processing stops.

User response:

Review the recovery agent logs for information about how to resolve this
issue.

------------------------------------------------------------------------
ANS3102I

'VMNAME' mounted successfully and is ready



Explanation:

The mount operation for the specified virtual machine completed
successfully. As a result, the virtual machine is ready for a file
restore operation.

System action:

None.

User response:

None

------------------------------------------------------------------------
ANS3103E

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.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation about how to install the
dynamic link library (iscsidsc.dll).

------------------------------------------------------------------------
ANS3104E

A target was not found on the iSCSI portal The missing target is
'target'



Explanation:

The iSCSI portal is unable to discover all of the targets that were
created by the IBM Spectrum Protect Recovery Agent command-line
interface.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation about how to correct this
iSCSI portal issue. Search
http://technet.microsoft.com/en-US/windowsserver for iSCSI
troubleshooting information.

------------------------------------------------------------------------
ANS3105E

Unable to connect all targets on the iSCSI Portal The target that is not
connected is 'target'. Windows error is (error)



Explanation:

The iSCSI portal is unable to connect all discovered targets that were
created by the IBM Spectrum Protect Recovery Agent command-line
interface.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation about how to correct this
iSCSI portal issue. Search
http://technet.microsoft.com/en-US/windowsserver for iSCSI
troubleshooting information.

------------------------------------------------------------------------
ANS3106E

Windows Configuration Manager is unable to scan for new hardware.
Windows error is (error)



Explanation:

The new iSCSI disk connection cannot be detected by the Windows
Configuration Manager.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation about how to correct this
hardware scan issue.

------------------------------------------------------------------------
ANS3107E

The attempt to retrieve information for disk 'disk' failed with Windows
error (error).



Explanation:

A Windows API call failed to retrieve the disk information.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3108W

The disk with label='label' is not mounted because it was excluded
during the backup (Reason: 'reason').



Explanation:

The disk cannot be mounted because it was excluded during backup. It is
not possible to recover files from any of the file systems or volumes
that use this disk. Possible reasons for the disk exclusion are: - The
disk was explicitly excluded by using the 'exclude.vmdisk' option. - The
disk is an independent disk, which cannot be backed up. The virtual
machine (VM) was backed up by using the 'vmprocessvmwithindependent yes'
option, which backs up normal disks while excluding independent disks. -
The disk contains one or more raw device mapping volumes that are
provisioned in physical compatibility mode (pRDM), which cannot be
backed up. The virtual machine was backed up by using the
'vmprocessvmwithprdm yes' option, which backs up normal disks while
excluding pRDM disks.

System action:

The operation continues.

User response:

- If the data is on a normal disk, then ensure that the disk is included
in the backup. - If the data is on an independent or pRDM disk, recreate
the disk on the restore machine. The data on the disk cannot be restored
because it was not backed up. - If a volume was striped across both
normal and independent disks, use a full virtual machine restore rather
than a file-level restore. Note that the data on the striped volume will
not be intact if all or part of the volume was striped across
independent disks, which are not part of the VMware snapshot. - If files
from the affected file systems or volumes must be recovered, ensure that
the disk is included in the backup.

------------------------------------------------------------------------
ANS3109E

The mount cannot be retrieved because the following mount ID cannot be
found: mountID



Explanation:

An error occurred while retrieving the mount with the mount ID that is
specified.

System action:

Processing stops.

User response:

No response is required.

------------------------------------------------------------------------
ANS3110E

Unable to communicate with Windows device 'device'. The Windows error is
(error)



Explanation:

A Windows API call failed to open a Windows device.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3111E

Unable to mount the same dynamic disks mutliple times. The disk 'disk'
signature is the same as the disk signature of another disk that is
online.



Explanation:

It is not possible to attach a second disk to the system with the same
disk signature.

System action:

The operation stops.

User response:

The other disk with the identical disk signature must be dismounted
before you can attempt the operation again.

------------------------------------------------------------------------
ANS3112E

Windows Virtual Disk Service is not able to detect all new devices.



Explanation:

The Virtual Disk Service VDS is unable to access all iSCSI targets. Some
targets are missing or not working.

System action:

The operation will be rolled back and stopped.

User response:

Determine why the data mover cannot access some iSCSI targets. Determine
that the IBM Spectrum Protect server is working correctly. Determine
that the iSCSI service is running. Search the Windows event log for
problems with the missing devices.

------------------------------------------------------------------------
ANS3113E

The virtual machine 'name' has at least one mirror or RAID5 volume.
Mirror and RAID5 support is disabled!



Explanation:

During the mount operation it was detected that the virtual machine has
a mirror or RAID5 volumes. The support for such volumes were diabled by
the Administrator.

System action:

The operation stops.

User response:

Contact the Administrator for more information.

------------------------------------------------------------------------
ANS3114E

The attempt to retrieve information for volume 'volume' failed with
Windows error (error).



Explanation:

A Windows API call failed to retrieve the volume information.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3115E

The attempt to bring disk 'disk' online failed with Windows error
(error).



Explanation:

A Windows API call failed to bring the disk online.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3116E

The attempt to create directory 'dir' failed with Windows error (error).



Explanation:

A Windows API call failed to create the directory.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3117E

The mount volume attempt at directory 'dir' failed with Windows error
(error).



Explanation:

A Windows API call failed to mount the specified volume.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3118E

Unable to determine the operating system type of the VM to be restored.



Explanation:

The operating system type of the VM to be restored cannot be determined.
This issue can occur when the restore parameter -VMOSType is not
specified or it specifies an incorrect operating system type.

System action:

The operation stops.

User response:

Use the -VMOSType parameter to specify the correct operating system type
of the VM to be restored.

------------------------------------------------------------------------
ANS3119W

Operating system type "name1" is detected but operating system type
"OSname" is specified.



Explanation:

The operating system type of the detected VM does not match the type
specified with the restore parameter -VMOSType. Inconsistent operating
system types might negatively impact the mount operation. The operation
will continue using "OSname" as the operating system type.

System action:

The operation continues.

User response:

If the mount operation fails, try the operation again and use automatic
detection or specify the correct operating system.

------------------------------------------------------------------------
ANS3121I

The TCP/IP V4 is not available for interprocess communication, V6 will
be used.



Explanation:

The commmethod option is V6Tcpip but for interprocess communication IBM
Spectrum Protect uses both methods. Initialization of the TCP/IP V4
failed so the TCP/IP V6 communication method will be used.

System action:

Process continues

User response:

None

------------------------------------------------------------------------
ANS3122E

The Microsoft iSCSI Initiator Service encountered an error. The Windows
error is (error).



Explanation:

The Microsoft iSCSI Initiator Service encountered an error during an
iSCSI operation. This error caused the operation to stop.

System action:

The operation stops.

User response:

See the Microsoft iSCSI Initiator Service error message to determine the
cause of the error. If necessary, see the appropriate Microsoft
Documentation for information about how to resolve this iSCSI Initiator
error.

------------------------------------------------------------------------
ANS3123E

Unable to read or write the local VM file restore data. filename File
cannot be accessed or is damaged.



Explanation:

For VM file restore operations, data must be stored on the local data
mover in a directory that the user running the restore can access. The
data file might also be damaged.

System action:

Processing stops.

User response:

To store the VM file restore data, the data mover application requires
read and write access to the C:\Documents and
Settings\AllUsers\Application Data\Tivoli\TSM\ or
C:\ProgramData\Tivoli\TSM folder. Set the access rights to this
directory so that your user has the correct rights. If the file was
damaged it can be helpful to replace the current version with the .bak
file.

------------------------------------------------------------------------
ANS3124E

The user session cannot be retrieved because the context ID cannot be
found



Explanation:

An error occurred while retrieving the current user session. The error
might be caused by a session that timed out.

System action:

Processing stops.

User response:

If the session timed out, log in again.

------------------------------------------------------------------------
ANS3125E

The local data for file restore mount with the ID: id and virtual
machine name 'name' cannot be found!



Explanation:

The local data set for the specified mount ID or virtual machine name
cannot be found.

System action:

The operation stops.

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.

------------------------------------------------------------------------
ANS3126E

The node name of the mount proxy partner could not be found.



Explanation:

An error occurred while querying the IBM Spectrum Protect server for the
mount proxy partner. The node could not be found. Communication with the
mount proxy partner is required to perform the restore operation.

System action:

Processing stops.

User response:

Check the mount proxy partner node configuration and ensure that the
node is correctly configured and running.

------------------------------------------------------------------------
ANS3127E

The IP address or port of the mount proxy partner could not be found.



Explanation:

An error occurred while querying the IBM Spectrum Protect server for the
mount proxy partner. The IP address or port of that partner could not be
found. The address and port are required to process file restores.

System action:

Processing stops.

User response:

Check the node configuration and ensure that the mount proxy partner is
correctly configured and running. Verify that the client acceptor daemon
on the mount proxy partner is running and able to connect to the IBM
Spectrum Protect server.

------------------------------------------------------------------------
ANS3128E

The node name of the Windows mount proxy does not comply with IBM
Spectrum Protect naming conventions.



Explanation:

An error occurred while querying the IBM Spectrum Protect server for
Linux mount proxy partner. The name of the Windows mount proxy does not
comply the naming convention. A correct name is required for processing
of Linux VMs.

System action:

Processing stops.

User response:

Check the node configuration and ensure that the mount proxy name is
correct. Use the web based configuration wizard to set up the
configuration.

------------------------------------------------------------------------
ANS3129I

The mount cleanup of VM 'VMNAME' completed.



Explanation:

The mount cleanup operation for the specified virtual machine completed.

System action:

None.

User response:

None

------------------------------------------------------------------------
ANS3130E

The mount cleanup operation for virtual machine 'vmname' failed with rc
= return-code



Explanation:

An error occurred during the mount cleanup operation. See the output
from the previous operations to identify the cause of the error.

System action:

Processing stops.

User response:

Check the dsmerror.log file for information about how to resolve this
issue.

------------------------------------------------------------------------
ANS3131E

The operation to disconnect the iSCSI targets from the Windows data
mover failed.



Explanation:

An error occurred during the mount cleanup operation while disconnecting
the iSCSI targets. See the output from the previous operations to
identify the cause of the error.

System action:

Processing stops.

User response:

Open the Windows iSCSI Initiator Tool and disconnect the targets and
remove the target portal. Try the operation again. The tool can be found
in "Administrative Tools" -> "iSCSI Initiator"

------------------------------------------------------------------------
ANS3132E

The Windows iSCSI Service is unable to get a list of all currently
running sessions. The Windows error is (error)



Explanation:

The iSCSI Service could not get a list of all connected targets and the
corresponding sessions.

System action:

The operation stops.

User response:

See the Microsoft documentation for information to correct this iSCSI
issue. Try the operation again. Search
http://technet.microsoft.com/en-US/windowsserver for iSCSI
troubleshooting information.

------------------------------------------------------------------------
ANS3133E

The target 'target' could not be disconnected by the iSCSI portal. The
Windows error is (error)



Explanation:

The iSCSI portal is unable to disconnect all the connected targets that
were created by the recovery agent command-line interface.

System action:

The operation stops.

User response:

See the Microsoft documentation for information to correct this iSCSI
portal issue. Try the operation again. Search
http://technet.microsoft.com/en-US/windowsserver for iSCSI
troubleshooting information.

------------------------------------------------------------------------
ANS3134E

The Windows iSCSI Service is unable to get list of all currently
available portals. The Windows error is (error)



Explanation:

The iSCSI Service has a problem getting a list of all available portals.

System action:

The operation stops.

User response:

See the Microsoft documentation for information to correct this iSCSI
portal issue. Try the operation again. Search
http://technet.microsoft.com/en-US/windowsserver for iSCSI
troubleshooting information.

------------------------------------------------------------------------
ANS3135E

The removal of iSCSI Portal 'target' failed with a Windows error of
(error)



Explanation:

The iSCSI Service cannot remove the iSCSI Portal.

System action:

The operation stops.

User response:

See the Microsoft documentation for information to correct this iSCSI
portal issue. Try the operation again. Search
http://technet.microsoft.com/en-US/windowsserver for iSCSI
troubleshooting information.

------------------------------------------------------------------------
ANS3136E

The mount ID was not specified in the cleanup operation.



Explanation:

The -MOUNTID parameter must be specified to perform a 'mountcleanup'
operation.

System action:

The operation stops.

User response:

Use the query "dsmc q vm <name> -vmrestoretype=mount" command to get the
correct mount ID for the cleanup

------------------------------------------------------------------------
ANS3137W

'VMNAME' mount completed with errors.



Explanation:

The mount operation for the specified virtual machine completed with
errors. Only a subset of the virtual machine's disks are ready for a
file restore operation.

System action:

The VM disks that failed were reported in previous messages.

User response:

Review the previous error messages for the cause of each failure.

------------------------------------------------------------------------
ANS3138E

The unmount of the volumes failed during the cleanup operation of mount
ID mountid



Explanation:

An error occurred during the mount cleanup operation while unmounting
the volumes.

System action:

Processing stops.

User response:

See the output from the previous operations to identify the cause of the
error.

------------------------------------------------------------------------
ANS3139E

The attempt to unmount the disk failed with Windows error (error).



Explanation:

The Windows API call failed to unmount the disks.

System action:

The operation stops.

User response:

See the Microsoft documentation for information to correct this issue;
search the documentation for this Windows error.

------------------------------------------------------------------------
ANS3140E

The connection to the following iSCSI targets failed: 'target_list'.



Explanation:

The iscsiadm command-line interface was not able to connect to the
specified iSCSI targets, from the Linux mount proxy machine.

System action:

The operation stops.

User response:

If the target is already connected on the Linux mount proxy machine, log
out from the target, for example: iscsiadm -m node -T targetname
--logout Also, verify that the iSCSI server address is correctly
specified.

------------------------------------------------------------------------
ANS3141W

Mounting the following devices failed: 'device_list'.



Explanation:

It was not possible to mount the specified devices on the Linux mount
proxy machine.

System action:

The operation continues to mount the other devices.

User response:

Perform a cleanup, or try to manually unmount the devices on the Linux
mount proxy machine.

------------------------------------------------------------------------
ANS3142E

The Windows Virtual Disk Service encountered an error. The Windows error
is (error)



Explanation:

The Windows Virtual Disk Service is not working correctly.

System action:

The operation stops.

User response:

See the Microsoft documentation for information to correct this issue.
Search http://technet.microsoft.com/en-US/windowsserver for Virtual Disk
Service troubleshooting information.

------------------------------------------------------------------------
ANS3143W

The ISCSI service is not running. Its state 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.

------------------------------------------------------------------------
ANS3144W

The ISCSI service is not running. File restore mount and instant access
operations will not work.



Explanation:

The ISCSI Service is not running. This service is required on the
Windows and Linux mount proxy for file restore mount operations. This
service is also required for full VM instant access operations.

System action:

Mount operations for file restore cannot continue. Instant access
operations cannot continue.

User response:

Start the ISCSI service if you want to perform a file restore operation
or instant access operation.

------------------------------------------------------------------------
ANS3145E

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 more information.

------------------------------------------------------------------------
ANS3146E

The cleanup operation to unmount the volume volume failed. The mounted
file system is busy.



Explanation:

An error occurred during the mount cleanup operation while unmounting
the volumes on the Linux mount proxy machine.

System action:

Processing stops.

User response:

Ensure the file system is not in use and then try the cleanup operation
again, or manually unmount the volume on the host.

------------------------------------------------------------------------
ANS3147W

The iSCSI Target 'iscsi_target'was disconnected successfully, but the
attempt to delete the target failed.



Explanation:

It was not possible to delete the object after the target was
disconnected.

System action:

The operation continues.

User response:

Try to manually delete the object on the Linux machine. For example:
iscsiadm -m node -T targetname -o delete

------------------------------------------------------------------------
ANS3148W

The iSCSI Target 'iscsi_target' was already connected.



Explanation:

The target was already connected on the Linux mount proxy machine. This
error can occur if a cleanup was not perfomed, or if the cleanup was
only partially successful.

System action:

The operation continues.

User response:

The Linux mount proxy machine tried to reuse the already connected
targets. If the volumes are not correctly mounted, manually disconnect
the targets on the Linux mount proxy machine. For example: iscsiadm -m
node -T targetname --logout; iscsadm -m node -T targetname -o delete

------------------------------------------------------------------------
ANS3149E

The iSCSI target 'target' failed to disconnect from the Linux machine.
The message from the iscsiadm command-line interface is: message_output



Explanation:

The iscsiadm command-line interface was unable to disconnect the
specified iSCSI target from the Linux machine.

System action:

The operation stops.

User response:

See if the target is already disconnected on the Linux machine, or try
to manually disconnect it. For example, iscsadm -m node -T targetname
--logout Verify that the iSCSI server address is correctly specified.

------------------------------------------------------------------------
ANS3150W

The block device 'block_device' of type 'device_type' failed to mount.
The system message is:'system_message'



Explanation:

It was not possible to mount one or more devices on the Linux machine.

System action:

The operation continues to mount the other devices.

User response:

Perform a cleanup, or try to manually unmount the devices on the Linux
machine.

------------------------------------------------------------------------
ANS3151E

The initiator.iscsi file does not exist or cannot be opened.



Explanation:

The file does not exist or cannot be opened.

System action:

Operations cannot continue.

User response:

The ISCSI service may not be installed.

------------------------------------------------------------------------
ANS3152E

The initiator.iscsi file does not have a valid initiator id entry.



Explanation:

No ISCSI Initiator ID exists.

System action:

Operations cannot continue.

User response:

The ISCSI servoce may not be installed.

------------------------------------------------------------------------
ANS3153E

The mount cleanup completed with error for mount ID 'mountid' of virtual
machine 'VMNAME'; Error log 'errlog' is available on 'machinename'.



Explanation:

An error occurred during the mount cleanup operation while unmounting
the volumes. The mounted file systems may be busy. See the error log to
identify the cause of the error.

System action:

Processing stops.

User response:

Ensure the file systems are not in use and the cleanup or manually
unmount the volumes on the host.

------------------------------------------------------------------------
ANS3154E

The ISCSI service is not installed.



Explanation:

The ISCSI Service is not installed.

System action:

Operations cannot continue.

User response:

Install the ISCSI service for your platform.

------------------------------------------------------------------------
ANS3155I

The Windows data mover is 'name' (ip)



Explanation:

The DNS name and the IP of the Windows data mover.

System action:

None.

User response:

This information can be used to determine if hostname and IP of the
Windows data mover are correctly resolved. The information can help if
the iSCSI connection is not working as expected.

------------------------------------------------------------------------
ANS3156I

The iSCSI server address used is 'ip'



Explanation:

This message returns the IP address of the iSCSI server.

System action:

None.

User response:

This information can be used to determine if the IP address of the iSCSI
server address is correctly resolved. The information might help you
troubleshoot problems if the iSCSI connection is not working as
expected.

------------------------------------------------------------------------
ANS3157I

The Linux data mover is 'name' (ip)



Explanation:

The DNS name and the IP address of the Linux data mover.

System action:

None.

User response:

This information can be used to determine if hostname and IP of the
Linux data mover are correctly resolved. The information might help you
troubleshoot problems if the iSCSI connection is not working as
expected.

------------------------------------------------------------------------
ANS3158W

The attempt to create the Windows share failed with Windows error
(error). The share is not created.



Explanation:

The creation of the Windows share failed with the given user/group name.

System action:

The Windows share is not created. The operation continues.

User response:

One common reason for failures is that the specified user/group does not
exist. Ensure that the Windows user or group name exists and is
accessible on the Windows data mover. If this is a domain user or group,
the Windows data mover has to be part of that domain. If this does not
resolve the problem, see the appropriate Microsoft Documentation for
information about this error code.

------------------------------------------------------------------------
ANS3159E

The attempt to remove the Windows Share failed with Windows error
(error).



Explanation:

A Windows API call failed to remove the Windows Share.

System action:

The operation stops.

User response:

See the appropriate Microsoft Documentation for information about how to
resolve this Windows API call issue.

------------------------------------------------------------------------
ANS3160W

The attempt to export Linux file system failed with error: NFS service
is not running.



Explanation:

exportfs command failed to make the directory on the Linux mount proxy
available for NFS clients to mount.

System action:

The operation continues without creating the NFS export.

User response:

Resolve the error on the Linux mount proxy. Manually export the
directory.

------------------------------------------------------------------------
ANS3161E

The attempt to unexport Linux file system failed with error: NFS service
is not running.



Explanation:

exportfs command failed to unexport the directory on the Linux mount
proxy.

System action:

The operation stops.

User response:

Resolve the error on the Linux mount proxy. Manually unexport the
directory.

------------------------------------------------------------------------
ANS3162I

The Mount cleanup of VM 'VMNAME' with mount id 'Id' and snapshot date
'date time' completed.



Explanation:

The mount cleanup operation for the specified virtual machine completed.

System action:

None.

User response:

None

------------------------------------------------------------------------
ANS3163W

The Linux Operating System is not at the minimum level. Mount operations
may not complete successfully.



Explanation:

The Linux Operating System is not at the minimum level.

System action:

Mount operations may not complete successfully.

User response:

Upgrade the Linux operating system to at least the minimum level.

------------------------------------------------------------------------
ANS3164W

The minimum level for 'os' is 'level'. Your current level is 'actual'.



Explanation:

The Linux Operating System is not at the minimum level.

System action:

Mount operations may not complete successfully.

User response:

Upgrade the Linux operating system to at least the minimum level.

------------------------------------------------------------------------
ANS3165W

A Package installed on the Linux Operating System is not at the minimum
level. Mount operations may not complete successfully.



Explanation:

A Package installed on the Linux Operating System is not at the minimum
level.

System action:

Mount operations may not complete successfully.

User response:

Upgrade the package to at least the minimum level.

------------------------------------------------------------------------
ANS3166W

The minimum level for package 'package' is 'level'. Your current level
is 'actual'.



Explanation:

A Package installed on the Linux Operating System is not at the minimum
level.

System action:

Mount operations may not complete successfully.

User response:

Upgrade the package to at least the minimum level.

------------------------------------------------------------------------
ANS3167E

IBM Spectrum Protect Recovery Agent service is not installed.



Explanation:

IBM Spectrum Protect Recovery Agent service is not installed.

System action:

Operations cannot continue.

User response:

Ensure that IBM Spectrum Protect Recovery Agent is correctly installed
and configured.

------------------------------------------------------------------------
ANS3168E

IBM Spectrum Protect Recovery Agent service is not running.



Explanation:

IBM Spectrum Protect Recovery Agent service is not running.

System action:

Operations cannot continue.

User response:

Start IBM Spectrum Protect Recovery Agent service. The Recovery Agent
can be started using "net start RecoveryAgent" or by referencing IBM
Spectrum Protect Recovery Agent in services.msc.

------------------------------------------------------------------------
ANS3169E

The mount proxy's operating system must be Windows Server 2012 or newer
operating system.



Explanation:

The Windows operating system is not at the minimum level.

System action:

Processing stops.

User response:

Upgrade the Windows mount proxy to a supported operating system.

------------------------------------------------------------------------
ANS3170W

The attempt to export Linux file system failed with error: exportfs
command failed.



Explanation:

exportfs command failed to make the directory on the Linux mount proxy
available for NFS clients to mount.

System action:

The operation continues without creating the NFS export.

User response:

Resolve the error on the Linux mount proxy. Manually export the
directory.

------------------------------------------------------------------------
ANS3171E

The attempt to unexport Linux file system failed with error: exportfs
command failed.



Explanation:

exportfs command failed to unexport the directory on the Linux mount
proxy.

System action:

The operation stops.

User response:

Resolve the error on the Linux mount proxy. Manually unexport the
directory.

------------------------------------------------------------------------
ANS3172T

Restoring virtual machine 'source' to new VM with name 'destination'.



Explanation:

The specified virtual machine will be restored as a new vm with a new
name.

System action:

None

User response:

None.

------------------------------------------------------------------------
ANS3173E

The Linux devices failed to mount correctly.



Explanation:

The Linux devices failed to mount correctly.

System action:

Mount operations did not not complete successfully.

User response:

Verify that the Linux mount proxy server can communicate with the IBM
Spectrum Protect server.

------------------------------------------------------------------------
ANS3174E

The virtual machine mount failed.



Explanation:

An error occurred during the mount operation.

System action:

Processing stops.

User response:

Check the command-line output for the messages that specify what
problems were encountered during the operation.

------------------------------------------------------------------------
ANS3175E

The VM mount cleanup failed.



Explanation:

An error occurred during the mount cleanup operation.

System action:

Processing stops.

User response:

Check the command-line output for the messages that specify what
problems were encountered during the operation.

------------------------------------------------------------------------
ANS3176W

Unable to locate the Windows user or group named 'name'. The share is
not created.



Explanation:

IBM Spectrum Protect was unable to map the specified user or group name
to a Windows security identifier.

System action:

The Windows share is not created. The operation continues.

User response:

One common reason for this message is that the specified user or group
does not exist. Ensure that the Windows user or group name exists and is
accessible on the Windows data mover. If this is a domain user or group,
the Windows data mover has to be part of that domain.

This message can also indicate that the Windows data mover is not able
to access the active directory domain server. Ensure that network
problems are not preventing the Windows data mover from communicating
with the active directory domain server.

------------------------------------------------------------------------
ANS3177E

No iSCSI target was connected. Check your iSCSI options for
backup-archive client.



Explanation:

No iSCSI target was found or connected on the Linux mount proxy machine.

System action:

The operation is rolled back.

User response:

Check that iSCSI is setup correctly on your Windows as well as your
Linux mount proxy. One common reason for a failure is that the
VMISCSIServeraddress option is not specified or is set incorrectly in
the options file of the Windows data mover.

------------------------------------------------------------------------
ANS3178E

Volume 'volume' of type 'file_system_type' has not been unmounted.
System message:'system_message'



Explanation:

An error occurred during the mount cleanup operation while unmounting
the volumes on the Linux mount proxy machine.

System action:

Processing stops.

User response:

Ensure the file system is not in use and then try the cleanup operation
again, or manually unmount the volume on the Linux mount proxy.

------------------------------------------------------------------------
ANS3179W

Another folder share with the same name 'name' already exists.



Explanation:

IBM Spectrum Protect was unable to create a folder share with the
specified name because a share with that name already exists.

System action:

The folder share is not created. The operation continues and the VM
disks are mounted for file restore on the mount proxy.

User response:

Use operating system commands to create the share of the folder with a
unique name and delete it before running the dismount operation.

------------------------------------------------------------------------
ANS3180W

The parameter 'name' contains characters that are not allowed and have
been removed. Resulting value is 'new'



Explanation:

Some characters cannot be used on multi platform environments. To solve
compatibly problems only a limited set of characters are allowed on this
specific 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 on Windows at
[a-z][A-Z][0-9][ ][-][_][\][@]

Parameter "-EXPORTParameter" is restricted on Linux at
[a-z][A-Z][0-9][.][:]

System action:

The operation continues with modified parameter.

User response:

None

------------------------------------------------------------------------
ANS3181E

The registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy
is set to an other value than 3.



Explanation:

If the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy
is set to an other value than 3 it can be that the machine hangs during
a mount operation. Change the value to 3 and reboot the machine.

System action:

The operation stops.

User response:

The registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy
is not documented by Microsoft. Sometimes this key is set to a value
other than 3 what can lead to problems with the mount operation. Set the
value to 3 and reboot the machine.

------------------------------------------------------------------------
ANS3182E

The mount cleanup operation timed out waiting minutes minutes for
response from Linux Mount Proxy.



Explanation:

The Windows Mount Proxy didn't receive any response from Linux Mount
Proxy within the given timeout. The Linux Mount Proxy is possible in
hanging state.

System action:

Processing stops.

User response:

Check the status of Linux Mount Proxy machine and mount proxy trace file
for more details. In the case of a complete system hang on umount, a
reboot followed by manual mount cleanup of the Linux mount proxy machine
may be required.

------------------------------------------------------------------------
ANS3183E

Failed to revert volume mounted at .



Explanation:

The volume revert operation failed. Try to mount the volume manually.
Find it's snapshot and attempt the revert operation.

System action:

The restore stops.

User response:

Check IBM Spectrum Protect error log, Windows Event logs for more
information.

------------------------------------------------------------------------
ANS3184W

A duplicate device UUID has been found during the LVM activation phase
of mount operation. The 'vgimportclone' system command was not able to
generate a new UUID for the LVM device 'LVMdeviceName' resulting in a
duplicated UUID with the device 'LVMdeviceName2' of the mount proxy
machine. The device 'LVMdeviceName3' has been excluded from the list of
volumes to be mounted on the mount proxy. On some Linux distributions
this device could still be present after the iSCSI disconnect phase and
a manual cleanup could be required e.g. by using the 'dmsetup remove
device_name' command.



Explanation:

The 'vgimportclone' command was not able to generate a new UUID for this
LVM device, resulting in a duplicated UUID.

System action:

The device of the target VM is skipped and not mounted. The operation
continues.

User response:

This problem has been observed on some Linux distributions where the
'vgimportclone' command was not able to generate a new UUID. In such
case the 'iscsiadm -m node -T ... --logout' command may not able to
remove such devices and a manual cleanup could be required e.g. by using
the 'dmsetup remove device_name' command. Note that such situation could
be also a signal that the target VM was cloned from same template as the
mount proxy. To resolve the duplicated devices introduced due to a VM
machine clone, check the block devices of the target VM by using the
'blkid' command and make sure that no duplicate UUIDs are present with
the mount proxy machines. If a duplicate device belongs to the target VM
and it is used, you need to assign it a new UUID or remove such device.

------------------------------------------------------------------------
ANS3185W

A duplicate device UUID is found on the mount proxy after the targets
were connected. The device 'new_device_name' with the UUID
'new_device_uuid' of type 'new_device_type' is excluded from the list of
volumes to be mounted on the mount proxy.



Explanation:

The Linux operating system cannot to mount devices of this type when the
UUID already exists on the system. This situation occurs because the
target virtual machine was cloned from the same template as the mount
proxy.

System action:

The device for the target virtual machine is not mounted. The operation
continues.

User response:

To resolve the duplicated devices that were introduced because of a
virtual machine clone, check the block devices for the target virtual
machine by using the 'blkid' command and make sure that no duplicate
UUIDs are present for the mount proxy machines. If a duplicate device
belongs to the target virtual machine and the device is in use, assign
the device a new UUID or remove the device.

------------------------------------------------------------------------
ANS3186W

Opening and creating the block devices failed.



Explanation:

It was not possible to get the list of block devices on the Linux mount
proxy

System action:

The file restore operation stopped.

User response:

Check that the 'blkid' command is working correctly on the Linux mount
proxy machine.

------------------------------------------------------------------------
ANS3187W

Opening and creating the block devices failed.



Explanation:

It was not possible to open the disk and create the block devices on the
Linux mount proxy machine.

System action:

The file restore operation stopped.

User response:

Check that on the Linux mount proxy machine, the number of loop devices
available are at least equal to the number of virtual machine disks to
mount. The advanced VMware transport mode is not supported on the Linux
mount proxy for file restore operations from local backups. Use the
vmvstortransport ndb option in the server stanza of the mount proxy
options file. If you want to use NBDSSL, remove the
/opt/tivoli/tsm/client/ba/bin/lib64/libdiskLibPlugin.so library and use
the vmvstortransport ndbssl option.

------------------------------------------------------------------------
ANS3188W

A duplicate UUID exists for LVM device 'new_device_name'. The device
cannot be mounted. As a result, files from this device will not be
restored.



Explanation:

The operating system cannot mount the device if its Universally Unique
ID (UUID) already exists on the system. This situation usually occurs
because the target virtual machine was cloned from the same template as
the mount proxy.

System action:

The device for the target virtual machine is not mounted. The operation
continues.

User response:

Use the blkid command to scan the block devices on the target virtual
machine for the existence of duplicate UUIDs. If a duplicate device
belongs to the target virtual machine and that device is in use, you
must assign a new UUID to the duplicate device, or remove that device.

------------------------------------------------------------------------
ANS3189W

Original mount points can not be found for guest system.



Explanation:

.

System action:

The operation continues.

User response:

Check if /etc/fstab file exists and is accessible on guest system.

------------------------------------------------------------------------
ANS3401W

The entity name is invalid.



Explanation:

A volume with this name could not be found or is not suitable for
server-free operations.

System action:

Processing stopped.

User response:

Specify the correct name.

------------------------------------------------------------------------
ANS3402W

name: A system call func failed with code rc.



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:

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 technical support
for further assistance.

------------------------------------------------------------------------
ANS3403W

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



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 technical support for further assistance.

------------------------------------------------------------------------
ANS3404W

An error occured reading volume name.



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:

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 technical support for further assistance.

------------------------------------------------------------------------
ANS3405W

File system fs on volume name is unknown.



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.

User response:

Check the error log for any other messages that might indicate a reason
for the failure. Try to correct any indicated problems, then try the
operation again. If the problem persists, contact IBM technical support
for further assistance.

------------------------------------------------------------------------
ANS3406I

Not enough space is available to update the last backup status for
virtual machine 'vm'.



Explanation:

The virtual machine is backed up successfully, but there is insufficient
space available to write the last backup status in the 'Notes' field for
the virtual machine.

System action:

The backup operation completed.

User response:

Free some space in the 'Notes' field for the virtual machine if the the
last backup status is needed.

------------------------------------------------------------------------
ANS3407W

name is not local.



Explanation:

The drive or filesystem is not local and is not suitable for image
backup.

System action:

Processing stopped.

User response:

Specify a volume that is local.

------------------------------------------------------------------------
ANS3408E

System call 'umount' failed for volume 'volume' with errno='error'.
Please take suitable action based on errno and retry the operation.



Explanation:

Umount failed for the specified volume with the indicated errno. Please
take suitable action based on errno and retry the operation.

System action:

Processing stopped.

User response:

Check errno for umount failure and take corrective action before
retrying the operation.

------------------------------------------------------------------------
ANS3409W

An error occurred writing to volume name.



Explanation:

IBM Spectrum Protect could not write to the named volume. Examples of
why this can occur include, but are not limited to: the data being
written is outside the valid range of the volume, or the device is
locked by another application. The operating system 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 technical support for further assistance.

------------------------------------------------------------------------
ANS3410E

The operating system refused a request for memory allocation.



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:

Close all unneeded applications and try the operation again. If the
operation still fails, try dividing the task into serveral smaller
units. For example, if a file specification contains several high level
directories, run the IBM Spectrum Protect task serially for each
directory. If the 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.

------------------------------------------------------------------------
ANS3411E

Invalid arguments were passed to function name.



Explanation:

The named function did not receive correct arguments to proceed. Please
check error log for additional errors following this one for further
explanation.

System action:

Processing stops.

User response:

Retry the operation. If problem persists contant your IBM Spectrum
Protect administrator.

------------------------------------------------------------------------
ANS3412I

DiskMapper does not support name for entity name.



Explanation:

The requested function is not implemented in DiskMapper at this time.
Please report this error to your IBM Spectrum Protect administrator.

System action:

Processing stops.

User response:

Contact your IBM Spectrum Protect administrator.

------------------------------------------------------------------------
ANS3413I

DiskMapper object 'name' type 'name' is not valid.



Explanation:

The named object is not valid on the originating client system.

System action:

Processing stops.

User response:

Retry the operation. If the problem persists, review the client error
log for other messages that might be related to this problem. Contact
your IBM Spectrum Protect administrator for additional help.

------------------------------------------------------------------------
ANS3414I

Disk 'name' is not part of any container defined on the system.



Explanation:

None.

System action:

None. This is informational message.

User response:

None.

------------------------------------------------------------------------
ANS3415W

At least one of the disk containing data for 'name' has bad blocks.



Explanation:

One or more physical disks containing data blocks of the above object
has bad blocks and the requested operation can not continue.

System action:

The system may find a work-around to complete the requested operation,
pleasecheck console log and error log for additional information on
corrective actions taken or suggested user action.

User response:

Depending on the operation the process may suggest an alternate way to
complete the operation. Check your error log, sched log, or console log
for additional information.

------------------------------------------------------------------------
ANS3416E

The volume 'name' is currently in use by other process.



Explanation:

The operation requires exclusive access to the volume. The most likely
cause of this failure is that other process on the system has the volume
opened.

System action:

Processing stopped.

User response:

Check applications running on your system to ensure that volume is not
opened by any if the process and then retry the operation.

------------------------------------------------------------------------
ANS3417W

name: A system call func failed with code rc - strerror



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:

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 technical support
for further assistance.

------------------------------------------------------------------------
ANS3418W

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



Explanation:

IBM Spectrum 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.

------------------------------------------------------------------------
ANS3419W

Failed to mount the VSS snapshot for integrity check on virtual machine
'vmname'. Integrity check is skipped and the Microsoft Exchange Server
transaction logs are not truncated.



Explanation:

The virtual machine snapshot must be mounted to verify the integrity of
the Microsoft Exchange Server database files. The snapshot for the
specified virtual machine was unable to be mounted. As a result, the
operation did not verify the integrity of the Microsoft Exchange Server
database files.

System action:

The backup operation continues without an integrity check and the
Microsoft Exchange Server transaction logs are not truncated.

User response:

To prevent this error, configure a connection from the guest virtual
machine to the ESXi host. Then, try the operation again.

------------------------------------------------------------------------
ANS4000E

Error processing 'filespace-name': file space does not exist.



Explanation:

The specified file space (domain) is incorrect or does not exist on the
workstation. If the message results from the BACKUP IMAGE command with
the -MODE=INCREMENTAL option, it means that you have entered the name of
a raw logical volume. The MODE=INCREMENTAL option is not valid for raw
logical volumes.

System action:

Processing stops.

User response:

Try the operation again, specifying an existing domain (drive letter or
file system name). If the message resulted from improper use of the
MODE=INCREMENTAL option, try the command again, omitting that option.

------------------------------------------------------------------------
ANS4001E

The file space for domain 'filespace-name' could not be found on the IBM
Spectrum Protect server.



Explanation:

The specified file space was expected to be found on the server, but it
no longer exists. It is possible that a command was issued to delete the
file space from the server while the current operation was in progress.

System action:

IBM Spectrum Protect processing stops.

User response:

Try the operation again. If the problem recurs, check the error log for
any other messages that might indicate a reason for the failure. Try to
correct any indicated problems, then try the operation again. If the
problem persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS4002E

Error processing 'filespace-name': volume label does not exist



Explanation:

The selected drive does not have a label.

System action:

IBM Spectrum Protect is unable to do the requested operation without a
drive or label entered.

User response:

If the drive is a floppy drive, place a disk with a volume label in it
and retry the operation. If the disk is a hard drive, ensure the drive
has a volume label, and retry the operation.

------------------------------------------------------------------------
ANS4003E

Error processing 'filespace-name': duplicate volume label encountered



Explanation:

The selected drive has a duplicate volume label. Because IBM Spectrum
Protect uses the volume label to keep track of backup/archive
information, it cannot back up or archive files from a drive with a
duplicate volume label.

System action:

IBM Spectrum Protect cannot select the drive.

User response:

If the volume needs to be available to the system, exit IBM Spectrum
Protect, and assign a volume label to the drive. Restart IBM Spectrum
Protect and retry the operation.

------------------------------------------------------------------------
ANS4004E

Error processing 'filespace namepath-namefile-name': destination file or
directory is write locked



Explanation:

The file or directory being restored or retrieved from the server cannot
be written to because the destination is write locked. Another operation
might have the file open and will not allow it to be updated.

System action:

File skipped.

User response:

Either determine which operation has the file write locked, or restore
the file to another name or location.

------------------------------------------------------------------------
ANS4005E

Error processing 'filespace namepath-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 backed
up, archived or migrated by IBM Spectrum Protect.

System action:

File skipped.

User response:

None.

------------------------------------------------------------------------
ANS4006E

Error processing 'filespace namepath-namefile-name': directory path not
found



Explanation:

The operating system returned a "path not found" status when IBM
Spectrum Protect attempted to access the directory. You either have
specified a directory that does not exist, as shown in the message
(path-name), or the directory being processed no longer exists on the
client because another process deleted it before it could be backed up
or archived by IBM Spectrum Protect.

System action:

The directory is skipped, processing continues

User response:

Recheck all spelling and punctuation, particularly the placement of
directory delimiters (for example, "\"). Correct the syntax if it is
incorrect, then retry the operation. Ensure that the path is specified
correctly and that the directory actually exists. Retry the command with
the corrected path and directory name. If you cannot correct the
directory name, use the Exclude option to exclude the directory from the
operation.

------------------------------------------------------------------------
ANS4007E

Error processing 'filespace namepath-namefile-name': access to the
object is denied



Explanation:

Access to the specified file or directory is denied. You tried to read
from or write to a file and you do not have access permission for either
the file or the directory.

System action:

Processing stopped.

User response:

Ensure that you specified the correct file or directory name, correct
the permissions, or specify a new location. If HSMOPTIMIZEDRECALLONLY is
set on the file system owner node, recall this file via optimized recall
prior to the next backup.

------------------------------------------------------------------------
ANS4008E

Error processing 'filespace namepath-namefile-name': file is temporarily
unavailable



Explanation:

File is temporarily unavailable.

System action:

File skipped.

User response:

Check and see if file is locked by other process. If not, retry the
command.

------------------------------------------------------------------------
ANS4009E

Error processing 'filespace namepath-namefile-name': disk full condition



Explanation:

No more files can be restored or retrieved because the destination disk
is full.

System action:

The client prompts you for action:

*  Retry this object

*  Skip this object

*  Abort the action

User response:

Select the appropriate action for this object. Create some free space on
the destination disk before you retry the operation. Another option is
to restore or retrieve the file to another disk.

------------------------------------------------------------------------
ANS4010E

Error processing 'filespace namepath-namefile-name': stale NFS handle



Explanation:

An NFS file system becomes stale.

System action:

File system skipped.

User response:

Verify that the NFS file system is mounted. If the problem persists,
unmount and remount the file system, then try the operation again.

------------------------------------------------------------------------
ANS4011E

Error processing 'filespace namepath-namefile-name': no file handles
available



Explanation:

All file handles for your system are currently in use. No more are
available.

System action:

Processing stopped.

User response:

Either free some file handles by ending other processes, or modify your
system setup to allow for more files to be open at the same time.

------------------------------------------------------------------------
ANS4012E

'filespace namepath-namefile-name' already exists. It will be skipped.



Explanation:

The client tried to restore or retrieve the specified file, but the file
already existed in the target restore location and the user chose not to
replace the existing file.

System action:

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

User response:

The file was skipped because either REPLACE NO was in effect, causing
all existing files and directories to be skipped, or REPLACE PROMPT was
in effect, and when prompted, the user chose to skip this file or all
existing directories and files. No additional action is necessary if the
decision to skip the file was deliberate. Otherwise the operation can be
retried using either REPLACE ALL REPLACE PROMPT.

------------------------------------------------------------------------
ANS4013E

Error processing 'filespace namepath-namefile-name': invalid file handle



Explanation:

An internal system error occurred. A file operation failed because an
invalid file handle was passed.

System action:

Processing stopped.

User response:

Report the problem to your system administrator, and then retry the
operation.

------------------------------------------------------------------------
ANS4014E

Error processing 'filespace namepath-namefile-name': unknown system
error (error-code) encountered. Program ending.



Explanation:

An unrecognized and unexpected error-code occurred within the client
program. This is a programming failure and the client program ends.

System action:

processing stops.

User response:

Try the operation again. If the problem continues, report the error to
your IBM Spectrum Protect administrator.

------------------------------------------------------------------------
ANS4015E

Error processing 'filespace namepath-namefile-name': unexpected IBM
Spectrum Protect error (error-code) encountered



Explanation:

An unexpected error occurred. This might be a low-level system or
communication error that IBM Spectrum Protect cannot handle or recover
from.

System action:

processing stops.

User response:

Try the operation again. If the problem continues, look for other
indications of system problems to determine where the problem exists.
Most systems have error or event logs which may contain additional
information. See your system administrator or IBM Spectrum Protect
administrator for further help.

------------------------------------------------------------------------
ANS4016E

Error processing 'filespace namepath-namefile-name': file is being
executed; write permission denied



Explanation:

The current file cannot be opened to write to because it is currently
being run by another operation.

System action:

File skipped.

User response:

Stop the operation that is running the file and retry the operation, or
restore or retrieve the file to a different name or directory.

------------------------------------------------------------------------
ANS4017E

Error processing 'filespace namepath-namefile-name': too many symbolic
links were detected while resolving name



Explanation:

While trying to resolve the file name, too many symbolic links were
found.

System action:

File skipped.

User response:

Ensure that you do not have a looping symbolic link for the file.

------------------------------------------------------------------------
ANS4018E

Error processing 'filespace namepath-namefile-name': file name too long



Explanation:

The file name specified is too long to be handled by IBM Spectrum
Protect.

System action:

File is skipped.

User response:

See the appropriate Using the Backup-Archive Client book for the
particular operating system, for the file names that are handled by IBM
Spectrum Protect.

------------------------------------------------------------------------
ANS4019E

Error processing 'filespace namepath-namefile-name': file system is
locked by system



Explanation:

File system cannot be accessed because it is locked by the system.

System action:

IBM Spectrum Protect cannot complete the operation.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS4020E

The data format for object 'filespace namepath-namefile-name' is
unknown. The unknown format usually occurs when the file was backed up
or archived by a later version of IBM Spectrum Protect.



Explanation:

When a file is backed up or archived, IBM Spectrum Protect includes some
additional information about the file. This message is issued if IBM
Spectrum Protect cannot recognize the information during a restore or
retrieve operation. The most likely cause is that the file was backed up
or archived with a newer version of IBM Spectrum Protect. If the file
was backed up from a case-preserving but not case-sensitive file system,
the file name might be displayed with incorrect casing. The incorrect
casing does not otherwise affect processing since 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 operation again with a current version of
the IBM Spectrum Protect client software. If the problem persists,
contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS4021E

Error processing 'filespace namepath-namefile-name': file system not
ready



Explanation:

The file system/drive was not ready for access.

System action:

Processing stopped.

User response:

Ensure that the drive is available to IBM Spectrum Protect, and then
retry the operation.

------------------------------------------------------------------------
ANS4022E

Error processing 'filespace namepath-namefile-name': file system is
invalid.



Explanation:

The drive was not available for access.

System action:

processing stops.

User response:

Ensure that the drive is operational, and then try the operation again.
If this is unsuccessful, check the error log.

------------------------------------------------------------------------
ANS4023E

Error processing 'filespace namepath-namefile-name': file input/output
error



Explanation:

An error was found while reading from or writing to the file.

System action:

File skipped.

User response:

Check your system to ensure that it is operating properly. For OS/2, run
CHKDSK /F for the failing drive which can be found in dsmerror.log.

------------------------------------------------------------------------
ANS4024E

Error processing 'filespace namepath-namefile-name': file write error



Explanation:

An error was found while writing to the file.

System action:

File skipped.

User response:

Check your system to ensure that it is operating properly.

------------------------------------------------------------------------
ANS4025E

Error processing 'filespace namepath-namefile-name': file exceeds user
or system file limit



Explanation:

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)

System action:

File skipped.

User response:

Ensure that the system limits are set properly.

------------------------------------------------------------------------
ANS4026W

Error processing 'filespace namepath-namefile-name': size of 'file-size'
exceeded the maximum file size limit on your system



Explanation:

You tried to restore or retrieve a file that has exceeded the maximum
file size limitation on your system.

System action:

IBM Spectrum Protect cannot restore or retrieve the file.

User response:

Restore or retrieve this file on a system that supports the file size.
See your system administrator.

------------------------------------------------------------------------
ANS4027S

Error processing 'filespace namepath-namefile-name': internal program
message 'value' encountered



Explanation:

An unexpected catastrophic program failure occurred, indicated by value.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, see your system
administrator or service representative.

------------------------------------------------------------------------
ANS4028E

Error processing 'filespace namepath-namefile-name': cannot create
file/directory entry



Explanation:

The directory path for files being restored or retrieved cannot be
created.

System action:

File skipped.

User response:

Ensure that you have the proper authorization to create the directory
for file being restored or retrieved.

------------------------------------------------------------------------
ANS4029E

Error processing 'filespace namepath-namefile-name': unable to build a
directory path; a file exists with the same name as a directory



Explanation:

IBM Spectrum Protect tried to create a directory path, but is unable to
because a file exists that has the same name as a directory.

System action:

Processing stopped.

User response:

Remove the file that has the same name as the directory. Refer to the
last restore/retrieve operation and check all directories along the
path.

------------------------------------------------------------------------
ANS4030E

Error processing 'filespace namepath-namefile-name': disk space limit
for this process reached



Explanation:

The disk space allocated for the client owner is full.

System action:

Processing stopped.

User response:

Free up disk space and retry the restore or retrieve operation.

------------------------------------------------------------------------
ANS4031E

Error processing 'file_space_namepath_namefile_name'. Name exceeds an
internal IBM Spectrum Protect limit.



Explanation:

During a file operation, IBM Spectrum Protect encountered a filename
where at least one component of the file name (file_space_name,
path_name or directory_name or file_name) exceeded an internal IBM
Spectrum Protect maximum. The internal IBM Spectrum Protect limits
should not be confused with the operating system limits for
file_space_name, path_name or directory_name, file_name.

Shown below are the IBM Spectrum Protect internal file name limits for
various platforms.

AIX HP-UX  Solaris
File_space_name               1024
Path_name or directory_name   1023
File_name                      256

Linux
File_space_name               1024
Path_name or directory_name    768
File_name                      256

Windows XP/2000/2003
File_space_name               1024
Path_name or directory_name    248
File_name                      248

System action:

The file is skipped.

User response:

Reduce the size of the filename so that it is smaller that the IBM
Spectrum Protect internal limits.

------------------------------------------------------------------------
ANS4032E

Error processing 'filespace namepath-namefile-name': file is not
compressed.



Explanation:

A file that was flagged as compressed was not compressed, and the system
failed.

System action:

Processing stopped.

User response:

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

------------------------------------------------------------------------
ANS4033E

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



Explanation:

You are trying to restore a file that was backed up and compressed on
another client workstation that had more memory than your client
workstation. You cannot restore this file. When the file is restored, it
is expanded and your workstation does not have enough memory.

System action:

IBM Spectrum Protect canceled the operation.

User response:

Obtain a machine with more memory and retry the operation.

------------------------------------------------------------------------
ANS4034E

Error processing 'filespace namepath-namefile-name': unknown system
error



Explanation:

An unknown error occurred. This might be a low-level system or
communication error that IBM Spectrum Protect cannot handle or recover
from.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, determine where the
problem exists. See your system administrator for further help.

------------------------------------------------------------------------
ANS4035W

File 'filespace namepath-namefile-name' currently unavailable on server.



Explanation:

You tried to restore or retrieve a file that is currently not available
from the IBM Spectrum Protect server.

System action:

IBM Spectrum Protect Cannot restore or retrieve the file.

User response:

Try to restore or retrieve after the file was made available on the
server. See your system administrator.

------------------------------------------------------------------------
ANS4036E

An error occurred saving the registry key.



Explanation:

The active registry key cannot be copied to the ADSM.SYS staging
directory.

System action:

Registry backup operation terminates.

User response:

Check the space available on the Windows boot partition to ensure there
enough space to contain a copy of the Windows registry. This might
require several megabytes of free space. Also check the Windows
permissions on the ADSM.SYS staging directory and ensure that the
Windows user under which you are running IBM Spectrum Protect has full
access to that directory and its contents.

------------------------------------------------------------------------
ANS4037E

Object 'file-namefile-namefile-name' changed during processing. Object
skipped.



Explanation:

The specified file-name was skipped during backup, archive, or migrate
because it was changing during the attempt to process it.

System action:

IBM Spectrum Protect skipped the object.

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
more information on backing up, archiving, or migrating changing
objects, see your system administrator.

------------------------------------------------------------------------
ANS4038E

An error occurred processing file system 'filespace name'.



Explanation:

File system 'filespace name' is corrupted or contains one or more
corrupted directories and cannot be processed.

System action:

File system is skipped.

User response:

Check your system to ensure that it is operating properly. For the
Windows environment, run CHKDSK utility for the failing drive. More
information about corrupted directories can be found in dsmerror.log.

------------------------------------------------------------------------
ANS4039E

Error processing 'filespace namepath-namefile-name': compressed file is
corrupted and cannot be expanded.



Explanation:

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 Spectrum Protect Server.

System action:

File skipped.

User response:

1) The compressed file is corrupted because there is a problem on the
tape. To know if this is the problem, please issue the following command
on the IBM Spectrum Protect Server: audit volume <volume_name> fix=no If
there is any problem reported, you could move the data from that volume
to a new one (see command MOVE DATA) and try again the restore. 2) There
are communications problems between the IBM Spectrum Protect Server and
the IBM Spectrum Protect Client and the results is that the file is
corrupted during the transmission. If you use a gigabit ethernet adapter
on the Server please upgrade the card driver (AIX platform) or add
provided by SUN suggested changes to some system network options which
have resolved this problem (SUN platform). 3) Please verify with your
network support if during the restore there are no any problems between
the IBM Spectrum Protect Client/Server that is originating the file
corruption.

------------------------------------------------------------------------
ANS4040E

Error processing 'filespace namepath-namefile-name': file system
filespace name has exceeded its space management quota.



Explanation:

IBM Spectrum Protect detects that the file system has exceeded its
quota. No more data can be migrated out of this file system.

System action:

IBM Spectrum Protect will not migrate files from this file system.

User response:

Recall some files, or ask the system administrator to increase the quota
for this file system.

------------------------------------------------------------------------
ANS4041E

A Windows Server 2008 or 2008 R2 VMware guest cannot be restored with a
non-Windows data mover.



Explanation:

A Windows data mover must run certain commands to complete the restore
of the Active Directory. Non-Windows data movers do not have the
necessary tools to complete this operation. Windows VMware guests that
are at Windows Server 2012 or higher are not affected by this
restriction.

System action:

Processing stops.

User response:

Use a Windows data mover to complete this action.

------------------------------------------------------------------------
ANS4042E

Object name 'filespace namepath-namefile-name' contains one or more
unrecognized characters and is not valid.



Explanation:

The file name, directory name, or volume label syntax is incorrect.

System action:

The file is skipped.

User response:

Check the disk for errors.

------------------------------------------------------------------------
ANS4044E

Error processing 'filespace-namepath-namefile-name': Case-sensitive name
conflict exists.



Explanation:

While processing the specified file on the workstation, another file
name was encountered with a similar name which only differed in case.
The Backup-Archive client does not allow names which differ only in case
on this platform and cannot guarantee 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 a unique name.

------------------------------------------------------------------------
ANS4045E

Error processing 'filespace-namepath-namefile-name': Case-sensitive name
conflict exists. The directory tree will be skipped.



Explanation:

While processing the specified file on the workstation, another object
name was encountered with a similar name which only differed in case.
The Backup-Archive client does not allow names which differ only in case
on this platform and cannot guarantee the integrity of the file, so the
directory and all of the objects contained within it are skipped.

System action:

This object will be skipped.

User response:

Rename the file in question to a unique name.

------------------------------------------------------------------------
ANS4046E

There is an error processing 'filespace-namepath-namefile-name': the
object is corrupted and unreadable.



Explanation:

You tried to read from or write to a file or directory that is
corrupted. The corrupted file is skipped. If this is a directory, the
objects contained in the directory and its subdirectories are skipped.

System action:

This object will be skipped.

User response:

Check your system to ensure that the filespace is not corrupted by using
system tools like chkdsk (Windows) or fsck (UNIX).

------------------------------------------------------------------------
ANS4047E

There is a read error on 'file-namefile-namefile-name'. The file is
skipped.



Explanation:

The specified file-name was skipped during backup archive because the
file could not be read.

If you are performing a JFS2 snapshot based operation, it is possible
that the snapshot was not large enough to contain all the changes made
to the filesystem after the snapshot was created. This could cause the
snapshot to become invalid thereby preventing IBM Spectrum Protect
client from reading the snapshot.

System action:

IBM Spectrum Protect skipped the file.

User response:

Check your system to ensure that it is operating properly.

If you are performing a JFS2 snapshot based operation, please use the
default snapshotcachesize of 100% and ensure that the volume group has
sufficient disk space to allocate snapshots at least as large as the
file system and retry the operation.

------------------------------------------------------------------------
ANS4048W

LAN-Free connection failed.



Explanation:

ENABLELANFREE option is set to YES for this session, but an attempt to
establish LAN-Free connection failed.

System action:

The IBM Spectrum Protect client will failover to non LAN-Free support.

User response:

Review the IBM Spectrum Protect error.log for LAN-Free failures. Check
your LAN-Free setup and verify that all components are working properly.

------------------------------------------------------------------------
ANS4049I

Established LAN-Free connection.



Explanation:

ENABLELANFREE option is set to YES for this session and the IBM Spectrum
Protect client successfully established LAN-Free connection with server,
after the LAN-Free connection was broken.

System action:

The IBM Spectrum Protect client will communicate with the server via
LAN-Free.

User response:

Review the IBM Spectrum Protect error.log for LAN-Free errors. Check
your LAN-Free setup and verify that all components are working properly.

------------------------------------------------------------------------
ANS4050W

Scheduled action 'schedule-action' did not execute for schedule
'schedule-name' as the IBM Spectrum Protect administrator has been
disabled from executing the scheduled action on the client.



Explanation:

One or more of the client options - schedcmddisabled,
srvprepostscheddisabled, srvprepostsnapdisabled, restretrscheddisabled,
have been set to YES on the client thereby preventing the IBM Spectrum
Protect administrator from executing one of the following scheduled
actions on the client - preschedule, postschedule, presnapshot,
postsnapshot or scheduled operating system commands, restore or retrieve
operations.

System action:

The scheduled operation will not be executed and a message will be
logged to IBM Spectrum Protect Server indicating this.

User response:

None required.

------------------------------------------------------------------------
ANS4051E

Error processing 'filespace namepath-namefile-name': The decryption
option is in effect, but the user ID under which back-up or archive is
being run is not authorized to decrypt this encrypted-file-system (EFS)
file.



Explanation:

The file being processed is encrypted by an encrypted file system (EFS).
The option is specified to back-up or archive the file in decrypted
form. The user ID under which the back-up or archive is being run does
not have decryption rights for this file.

System action:

The file is skipped.

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

------------------------------------------------------------------------
ANS4052E

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



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

------------------------------------------------------------------------
ANS4053E

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



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.

------------------------------------------------------------------------
ANS4054E

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



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.

------------------------------------------------------------------------
ANS4055E

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



Explanation:

The file space on the IBM Spectrum 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.

------------------------------------------------------------------------
ANS4056E

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



Explanation:

The IBM Spectrum 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
   Spectrum Protect client.

*  The object was backed up or archived to a version 5.5 or lower IBM
   Spectrum Protect server.

*  IBM Spectrum Protect client version 6.2 or higher is attempting to
   perform an operation that causes the IBM Spectrum 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 Spectrum 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 Spectrum 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 Spectrum Protect server administrator for further
assistance.

------------------------------------------------------------------------
ANS4057W

Unable to process object 'fs' with nested file system mounted on it
during snapshot based backup.



Explanation:

Snapshot based backup of objects with mounted file systems on them are
not supported.

System action:

The backup operation continues without specified object.

User response:

To prevent this behaviour unmount file system from specified object and
retry the operation.

------------------------------------------------------------------------
ANS4058I

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



Explanation:

A write failure is often a result of insufficient access permissions to
the options file, but could also be caused by the lack of available disk
space. The replication server connection information can not be saved
and failover will not be possible.

System action:

The operation failed.

User response:

Check the local disk for possible causes of the write error, and check
to see that sufficient access to the options file is configured.

------------------------------------------------------------------------
ANS4059I

The option USEREPLICATIONFailover is set to NO. The node will not fail
over to the failover server



Explanation:

This option will prevent the node from connecting to the replication
server in the event of a failure of the primary server.

System action:

The client will not connect to the primary server and processing stops.

User response:

No response is required.

------------------------------------------------------------------------
ANS4061I

Connected to failover server failover server; in fail over mode. Home
server is: home server;



Explanation:

The node is configured for replication and has successfully connected to
the failover server. This message is to notify the server administrator
that a node has connected to the failover server in fail over mode.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS4063W

IBM Spectrum Protect application protection cannot copy the application
metafile 'App-Metadata-File-Name' from the following VM: 'VM-Name'.
Individual database restore from this backup is not supported. Check
health of application writers and databases



Explanation:

The application metafile was not found on the guest machine.

System action:

The operation completes. However, the application metafile was not
copied.

User response:

Make sure that the application VSS writers are running on this guest
machine, and the application database is in the state to allow the
backup. For Exchange check that databases are mounted. For SQL check
databases are online. Then try the operation again.

------------------------------------------------------------------------
ANS4064I

Restoring vCloud Director vApp 'vapp name' from Organization VDC 'org
vdc name' from organization 'org name' Target vApp name is 'restored
vapp name' Restore VAPP command started. Total number of vApps to
process: vapps num to restore



Explanation:

The restore vApp operation completed.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS4065E

Proxy rejected: data mover node 'dm node' has not been granted proxy
authority for target node 'target_node', associated with Organization
vDC 'OVDC name' of Organization 'Org Name'.



Explanation:

The operation requires that a proxy access for the data center node is
granted to the data mover node.

System action:

Operation is canceled for the specified vApp.

User response:

Run configuration wizard or configuration editor to configure proper
nodes relashionship.

------------------------------------------------------------------------
ANS4066I

Snapshot operation attempt x of y for the guest virtual machine 'VM'
failed using "sType" snapshot. Reattempting snapshot with "sType2"
snapshot.



Explanation:

The snapshot operation has failed. A snapshot retry operation has been
scheduled.

System action:

Retrying snapshot.

User response:

Check the error log for any other messages that might indicate a reason
for the failure. Correct any problems and try the operation again.

------------------------------------------------------------------------
ANS4067E

Snapshot operation attempt x of y for the guest virtual machine 'VM'
failed using "sType" snapshot. Backup failed.



Explanation:

All snapshot retry attempts of the guest virtual machine failed.

System action:

Processing stops.

User response:

Check the error log for any messages that indicate a reason for the
failure. Correct any problems and try the operation again. If the
problem persists, search the IBM Spectrum Protect Support web site
(http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html)
for known solutions.

------------------------------------------------------------------------
ANS4068I

Restored virtual machine 'VM' was backed up using a "VMware Tools with
file system quiescing and application quiescing disabled" snapshot. This
is equivalent to a "crash-consistent" backup.



Explanation:

The restored virtual machine was backed up using a "VMware Tools with
file system quiescing and application quiescing disabled" snapshot.
Application Protection feature is not available.

System action:

Restore of the VM continues.

User response:

None

------------------------------------------------------------------------
ANS4069E

The Windows domain credentials cannot be found. Use the Data Protection
for VMware vSphere GUI configuration editor to set the Windows domain
credentials.



Explanation:

The required Windows domain administrator credentials were not set.

System action:

Processing stops.

User response:

Set the Windows domain administrator credentials in the Data Protection
for VMware vSphere GUI configuration editor.

------------------------------------------------------------------------
ANS4070E

Windows domain credentials are incorrect. Verify the credentials and use
dsmc SET PASSWORD -type=DOMAIN 'domain\userid' 'password' to update the
username and password.



Explanation:

The supplied credentials are incorrect. The system failed to
authenticate to the Windows domain using these credentials.

System action:

Processing stops

User response:

Use dsmc SET PASSWORD -type=DOMAIN 'domain\userid' 'password' to update
the username and password. And then retry the operation.

------------------------------------------------------------------------
ANS4071E

'VM-Name' cannot be restored because it was backed up with a newer
version of the client.



Explanation:

The client version that attempted to restore the virtual machine is
earlier than the client version that backed up the virtual machine. The
virtual machine cannot be restored with an earlier client version.

System action:

The virtual machine is not restored. Processing continues with the next
virtual machine.

User response:

Upgrade the client to a version that is compatible with the client
version that backed up the virtual machine.

------------------------------------------------------------------------
ANS4072E

Error processing 'filespace namepath-namefile-name': unable to create
symbolic link; a file or directory exists with the same name as the
symbolic link



Explanation:

IBM Spectrum Protect tried to create a symbolic link, but is unable to
because a file or directory exists that has the same name as the
symbolic link.

System action:

Processing stops.

User response:

Remove the file or the directory that has the same name as the symbolic
link. Refer to the last restore/retrieve operation.

------------------------------------------------------------------------
ANS4073W

Snapshot operation attempt x of y for the guest virtual machine 'VM'
failed using "sType" snapshot. Reattempting snapshot with "sType2"
snapshot.



Explanation:

The snapshot operation has failed. A snapshot retry operation with
different snapshot type has been scheduled.

System action:

Retrying snapshot with different snapshot type.

User response:

Check the error log for any other messages that might indicate a reason
for the failure. Correct any problems and try the operation again.

------------------------------------------------------------------------
ANS4077E

File 'filespace namepath-namefile-name' is encrypted by Microsoft EFS
and contains at least one sparse data stream. The operating system does
not support restore for this file so it is not backed up or restored.



Explanation:

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 Spectrum 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.

------------------------------------------------------------------------
ANS4078E

Content file content.spsig is missing, is damaged or failed the
signature check.



Explanation:

The file content.spsig is missing. Or the file is damaged or the
signature of the file does not match. See client log file for more
information.

System action:

Processing stops.

User response:

Make sure that the data in the Operations Center, such as the client
package or Update Manager package, is correct or download the correct
version in the Operations Center.

------------------------------------------------------------------------
ANS4079E

One or more files failed the signature check.



Explanation:

The signature of one or more files does not match the contents of
content.spsig. See the client log file for more information.

System action:

Processing stops.

User response:

Make sure that the data in the Operations Center, such as the client
package or Update Manager package, is correct or download the correct
version in the Operations Center.

------------------------------------------------------------------------
ANS4081E

Error processing 'filespace-name': file space type is not supported.



Explanation:

The specified file space type is not currently supported by IBM Spectrum
Protect on this platform.

System action:

The unsupported file system is skipped. Processing continues with the
next file system.

User response:

Refer to the documentation for information on what file space types are
supported.

------------------------------------------------------------------------
ANS4083I

New node password has been generated.



Explanation:

The client logged in using administrative id rather than node name. New
random node password has been generated and recorded.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS4084E

Error processing 'filespace-namepath-namefile-name': cannot get file
status.



Explanation:

While processing the file, the lstat() call set EOVERFLOW error code.

System action:

This file will be skipped.

User response:

The file is skipped. Processing continues with the next file.

------------------------------------------------------------------------
ANS4085I

Assigned 'number' objects from previous systemstate backup to the new
systemstate backup.



Explanation:

Objects in the previous System State backup have not changed and were
assigned to the new System State backup.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS4086W

Failed to assign unchanged objects from previous systemstate backup to
the new systemstate backup. Objects will be backed up.



Explanation:

Objects in the previous System State backup have not changed and should
be assigned to the new systemstate backup. Due to error assign operation
failed and objects will be backed up.

System action:

Processing continues.

User response:

Retry the operation. If the problem persists, contact IBM Spectrum
Protect technical support.

------------------------------------------------------------------------
ANS4087E

An attempt to load data for the wizard failed. For more information,
please see the log file.



Explanation:

An attempt to load data for the wizard failed as the remote agent is
probably unavailable.

System action:

Processing stopped.

User response:

Check the log for reason for the failure.

------------------------------------------------------------------------
ANS4089W

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



Explanation:

The file server has been upgraded to a version that supports unicode
file names for incremental backup using snapshot difference. Perform a
full incremental in order to backup any files with unicode names that
may have been skipped by the previous version of the IBM Spectrum
Protect client.

System action:

Processing continues.

User response:

Perform a full incremental by specifying the command line option
createnewbase=migrate with the snapdiff option as soon as possible.

------------------------------------------------------------------------
ANS4090I

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



Explanation:

The file server has been upgraded to a version that supports unicode
file names for incremental backup using snapshot difference. Perform a
full incremental in order to backup any files with unicode names that
may have been skipped by the previous version of the IBM Spectrum
Protect client.

System action:

Processing continues.

User response:

Perform a full incremental backup by specifying the command line option
createnewbase=migrate with the snapdiff option as soon as possible.

------------------------------------------------------------------------
ANS4092E

Data mover platform is not supported for instant access/restore
operations.



Explanation:

The instant access/restore operation failed.

System action:

The instant access/restore operation failed. The reason for the failure
is unsupported platform.

User response:

The instant access/restore operation should be performed from a
supported data mover platform.

------------------------------------------------------------------------
ANS4099E

The system volume cannot be identified. Therefore the system state
cannot be backed up.



Explanation:

The system volume contains the hardware-specific system state files that
are needed to start Windows, such as Ntldr, Boot.ini, Ntdetect.com or
Bootmgr. If the system volume cannot be identified, then these files
cannot be backed up. Therefore it is not possible to back up the system
state.

System action:

Systemstate backup stops.

User response:

Try the operation again. If the problem persists, obtain a service trace
that captures the problem and contact IBM technical support for
additional assistance. Your IBM Spectrum Protect administrator can help
you configure the trace.

------------------------------------------------------------------------
ANS4137E

Error processing 'filespace namepath-namefile-name': exceeded maximum
number of links allowed



Explanation:

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:

Select the appropriate action for this object. Restore or retrieve the
link to another file system.

------------------------------------------------------------------------
ANS4148E

Full VM backup of Virtual Machine 'vmname' failed with RC rc



Explanation:

The Full VM backup of virtual machine failed.

System action:

The full backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4150E

Incremental backup of Virtual Machine 'vmname' failed with RC rc



Explanation:

The incremental backup of virtual machine volumes failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4151E

Failure mounting Virtual Machine 'vmname'. RC=rc



Explanation:

The VMware failed to mount virtual machine disk.

System action:

The backup of the virtual machine can not continue. The next virtual
machine in the vmlist will be processed. Refer to dsmerror.log for
detailed error message for the reason for the failure.

User response:

Refer to dsmerror.log for detailed error message.

------------------------------------------------------------------------
ANS4152E

Failure initializing VMware virtual machine environment. RC=rc. Refer to
IBM Spectrum Protect error log for detailed error messages.



Explanation:

Failure initializing VMware virtual machine environment. Refer to IBM
Spectrum Protect error log for detailed error messages.

System action:

The backup can not continue.

User response:

Refer to IBM Spectrum Protect error log for detailed messages.

------------------------------------------------------------------------
ANS4153E

Hostname could not be found for Virtual Machine 'vmname'



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4154E

Possible cause Virtual Machine is not running and does not have a static
IP address.



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4155E

The virtual machine 'vmname' was not found on the vSphere server.



Explanation:

The backup of the virtual machine failed because the specified virtual
machine name was not found. It is possible that the virtual machine name
was entered incorrectly or contains unsupported characters. Only virtual
machine names that contain 7-bit ASCII characters are supported, and the
operation will fail if the name contains other characters.

System action:

The backup of the virtual machine failed. The next virtual machine in
the vmlist will be processed. Check the client error log for additional
error messages.

User response:

Check the local client error log for reason for the failure.

*  If the virtual machine name was entered incorrectly, try the
   operation again with the correct machine name.

*  If the virtual machine name contains characters other than 7-bit
   ASCII characters, either change the virtual machine name so it
   contains only 7-bit ASCII characters, or do not include the virtual
   machine for backup operations.



------------------------------------------------------------------------
ANS4156E

File level VM backup of virtual machine 'vmname' not supported. File
level VM backup not support on non Windows platform guest OS. Platform
type: 'platform'.



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Back up the virtual machine using the VMBACKUPType=FULLvm option.

------------------------------------------------------------------------
ANS4159E

Backup of Virtual Machine 'vmname' failed. rc=rc.



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4160E

Proxy Rejected: Proxy authority has not been granted to Agent Node:
'agent_node' for Target Node: 'target_node'.



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is the node has not been granted proxy authority to access the
node named by the backup proxy node. The IBM Spectrum Protect
administrator must first grant proxy authority.

User response:

The IBM Spectrum Protect server administrator must grant proxy authority
for this node. See the administrator command "Grant Proxynode".

------------------------------------------------------------------------
ANS4161E

Duplicate virtual machine name 'vmname' was detected in the same backup
operation. Backup of virtual machine 'vmfullname' can not continue
without a unique object name.



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Choose a unique name for the virtual machine.

------------------------------------------------------------------------
ANS4162E

The virtual machine 'virtual-machine-name' has not been previously
backed up.



Explanation:

The specified virtual machine has not been previously backed up, so can
not be specified for restore.

System action:

The specified virtual machine is skipped, and the next virtual machine
in the restore list is processed.

User response:

Verify the virtual machine name to be restored, and re-try the
operation.

------------------------------------------------------------------------
ANS4164W

Compression is currently enabled, but the virtual machine backup for
'virtual-machine-name' is not compressed because client-side
deduplication is not being used.



Explanation:

Compression can only be used with virtual machine CTL and Data files
when the files are stored in a storage pool that is enabled for
client-side deduplication. This message is issued when the client is
configured for compression and virtual machine CTL or Data files are
directed to a storage pool that is not enabled for client-side
deduplication.

System action:

Backup continues, and data is not compressed.

User response:

If you intend to compress virtual machine CTL and Data files, then
update your IBM Spectrum Protect configuration so that both types of
files are directed to storage pools that are enabled for client-side
deduplication. If you intend to compress virtual machine Data files but
not CTL files, then update your IBM Spectrum Protect configuration so
that the Data files are directed to a storage pool that is enabled for
client-side deduplication. Set the VMSKIPCTLCOMPRESSION to YES in your
client options file. If you do not intend to use compression, then set
COMPRESSION NO in your client options file.

------------------------------------------------------------------------
ANS4165E

Creating a Virtual Machine, but the hostname 'virtual-machine-name' was
not found.



Explanation:

The Virtual Machine being creating must have a valid hostname to be
created.

System action:

Check the virtual machine hostname specified for correctness.

User response:

Correct the virtual machine hostname specified and retry the restore.

------------------------------------------------------------------------
ANS4166E

Creating a Virtual Machine, but the datacenter 'virtual-machine-name'
was not found. The name may be incorrect or may be located in a VMware
folder and require the folder name such as vmfolder/dcname.



Explanation:

The Virtual Machine being created must have a valid datacenter to be
created.

System action:

Processing stops.

User response:

Check the virtual machine datacenter specified for correctness. If the
datacenter is contained in a folder then the full datacenter name,
complete with the folder path, must be specified, such as
vmfolder/dcname.

------------------------------------------------------------------------
ANS4167E

Creating a Virtual Machine, but the datastore 'virtual-machine-name' was
not found.



Explanation:

The Virtual Machine being creating must have a valid datastore to be
created.

System action:

Check the virtual machine datastore specified for correctness.

User response:

Correct the virtual machine datastore specified and retry the restore.

------------------------------------------------------------------------
ANS4168E

VMware has reported an error via their SOAP interface. On the Detailed
Status Report panel, view the last error message reported. Also check
the error log for more information about the problem that occurred.



Explanation:

The command to VMware failed to complete. The error returned is
displayed on the Restore or Backup summary panel under the Last Error
Message section.

System action:

An error occurred, and the operation failed.

User response:

Check the reported error and correct the problem. Usually the reason for
the error is a user-supplied value which is not valid for the operation.

------------------------------------------------------------------------
ANS4169E

A write failure occurred on the local disk proxy used to temporarily
store the virtual machine virtual disk information. The write failure
can be caused by the lack of available disk space on the drive used to
store this information. The VMBACKDIR option can be used to assign a
different disk location for this purpose. Check the drive being used and
ensure that there is enough space available for this operation.



Explanation:

There was a write error from the local disk used to store the virtual
machine virtual disk information. Usually the write error is due to lack
of disk space, lack of write permissions, or some similar problem with
the local disk. The VMBACKDIR option can be used to assign a different
disk location if the local drive does not have enough free space for the
operation.

System action:

A disk write error occurred, and the operation failed.

User response:

Check the local disk for possible causes of the write error, and use the
VMBACKDIR option to assign another disk if needed.

------------------------------------------------------------------------
ANS4170E

Can not create a Virtual Machine on VMware release
'release-version-target' which was backed up from VMware release
'release-version-source'.



Explanation:

The Virtual Machine being created was backed up from a version of VMware
which is not compatible with the target VMware release version being
used for the restore.

System action:

Processing stops.

User response:

Restore the Virtual Machine to a VMware system which is compatible with
the level from which the Virtual Machine was backed up.

------------------------------------------------------------------------
ANS4174E

Full VM backup of VMware Virtual Machine 'vmname' failed with RC=rc
mode=full_or_incr, target node name='target_node_name', data mover node
name='data_mover_node_name'



Explanation:

The Full VM backup of virtual machine failed. If the virtual machine
(VM) name contains the word AGGREGATE, the statistics that are shown
represent the total value of all VM guests that are backed up per data
mover.

System action:

The full backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4177E

Full restore of VMware virtual machine 'vmname' failed with RC=rc,
mode='restore_or_revert', target node name='target_node_name', data
mover node name='data_mover_node_name'



Explanation:

The full restore of the virtual machine failed.

System action:

The full restore of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4179I

IBM Spectrum Protect application protection did not truncate the
Microsoft SQL Server logs on VM 'VM'.



Explanation:

The SQL server logs were not truncated because the following option was
specified for this virtual machine: INCLUDE.VMTSMVSS vname
OPTIONS=KEEPSQLLOG

System action:

The operation completes.

User response:

Remove the OPTIONS=KEEPSQLLOG option to enable truncation of the SQL
logs when a backup completes.

------------------------------------------------------------------------
ANS4187W

CPU and Memory Resource Allocation configuration settings cannot be
restored when the IBM Spectrum Protect data mover node is connected
directly to a Virtual Center managed ESX/ESXi host. These settings have
been skipped.



Explanation:

The VMware vStorage APIs do not support the restore of CPU and Memory
Resource Allocation configuration settings when connected directly to an
ESX/ESXi host that is managed by a Virtual Center.

System action:

CPU and Memory Resource Allocation configuration settings are skipped.
Processing continues.

User response:

Virtual machine CPU and Memory Resource Allocation configuration
settings will be restored when the IBM Spectrum Protect data mover node
connects directly to a vCenter Server. Modify the VMCHOST to connect the
IBM Spectrum Protect data mover to a vCenter Server.

------------------------------------------------------------------------
ANS4191E

Restore VM operation failed using 'san' transport mode. In some cases
switching from SAN to network-based VM restores can be successful.



Explanation:

Restore VM operations that fail using SAN transport mode can often be
successful over a LAN path. If a restore vm operation fails using the
'SAN' transport mode, set the client option VMVSTORTRANSPORT to
"nbd:nbdssl" and try the restore 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 VM restores can be successful when using 'nbd' or 'nbdssl'
transport modes. The VMVSTORTRANSPORT option can used to restrict the
IBM Spectrum Protect client to use only the specified transport modes.

------------------------------------------------------------------------
ANS4193E

vApp 'vApp name' cannot be processed because data mover 'dm node' cannot
connect to the target node 'target_node'.



Explanation:

The operation requires that a proxy access for the data center node is
granted to the data mover node.

System action:

Operation is canceled for the specified vApp.

User response:

Look for errors in error log and correct any problems. Run configuration
wizard or configuration editor to ensure proper nodes configuration.

------------------------------------------------------------------------
ANS4194E

Encryption is currently enabled, but is not supported for incremental
forever backups of virtual machines (-MODE=IFFULL or
-MODE=IFINCREMENTAL) .



Explanation:

Client encryption of virtual machine incremental forever backups
(-mode=IFFULL or -mode=IFINCREMENTAL) is not supported. In order to
avoid the unintentional storage of unencrypted data on the server, the
backup operation stops.

System action:

The virtual machine backup stops.

User response:

Remove the encryption options for this operation and run it again. You
can use Secure Sockets Layer (SSL) encryption to encrypt the data over
the network. If the backup data must be encrypted in IBM Spectrum
Protect storage pools, use an alternative backup method such as full and
incremental backups (-mode=FULL and -mode=INCREMENTAL), or in-guest
backups.

------------------------------------------------------------------------
ANS4195E

The target node for Organization VDC 'OrgVDC name' in Organization 'Org
name' was not found. As a result, vApp 'vApp name' cannot be backed up.



Explanation:

Either the IBM Spectrum Protect node for the specified organization VDC
was not found on the IBM Spectrum Protect server, or information about
the Organization VDC node was not found in the Provider 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 all required IBM Spectrum Protect nodes are registered on
the IBM Spectrum Protect server. If required, register a new data mover
node. Make sure that the organization VDC belongs to the provider VDC
that this data mover node protects.

------------------------------------------------------------------------
ANS4199W

File 'file name' is not backed up as part of the system state because
cluster disk 'volume name' is not accessible.



Explanation:

The indicated file or directory was returned by VSS as part of the
backup file list of the writer. However, the cluster disk where the file
is located is not accessible. The reasons for this problem can be that
the cluster disk is offline or belongs to another node.

System action:

The file is not backed up. Processing continues.

User response:

This problem is documented in Microsoft knowledge base topic 980794
http://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 one or more files to be excluded from VSS
enumeration. IBM Spectrum Protect does not back up files that are not
enumerated by VSS. If the volume is brought online to the node
performing the system state backup, then it cannot be backed up. You
must remove the volume from the registry key and restart the system
before you can back up the volume. If you do not want to implement the
hotfix for this problem, IBM Spectrum Protect continues to issue this
message.

------------------------------------------------------------------------
ANS4200E

The virtual machine 'vmname' could not be backed up because the data
usage of datastore 'datastore' exceeded the datastore threshold of
percentused percent.



Explanation:

The data usage of the datastore used by the virtual machine exceeds the
threshold set by the VMDATASTORETHRESHOLD option.

System action:

The virtual machine is not backed up.

User response:

Reduce the data usage of the datastore or increase the threshold in the
VMDATASTORETHRESHOLD option. Then, back up the virtual machine again.

------------------------------------------------------------------------
ANS4202E

The Deployment Manager failed to install language pack: language pack
name. The Microsoft Installer error code was error code.



Explanation:

The previous language pack has been uninstalled, and the installation of
the new language pack failed.

System action:

Processing continues.

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.

------------------------------------------------------------------------
ANS4204E

The Operating System of the client computer: 'os name' is not supported
by the target version: 'target version'



Explanation:

The operating system level of the client computer is no longer supported
by the target level.

System action:

Processing stops.

User response:

Check the release documentation for information on supported operating
system levels.

------------------------------------------------------------------------
ANS4206E

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



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.

Make sure that all of the Windows self extracting client images on the
client computer are valid.

------------------------------------------------------------------------
ANS4207E

The Deployment Manager was unable to initiate the final connection
between the server and the updated backup-archive client.



Explanation:

After the automatic client deployment, the dsmc query session command
from the updated backup-archive client was not successful.

System action:

The Deployment Manager process ends.

User response:

Log on to the client computer and check the backup-archive client error
log.

------------------------------------------------------------------------
ANS4210E

The Deployment Manager failed to install package: 'client package name'.
The Microsoft Installer error code was 'system architecture'



Explanation:

The previous client package has been uninstalled, and the installation
of the new client package failed.

System action:

Processing stops.

User response:

Check the technote for Microsoft Installer error code description:
http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

------------------------------------------------------------------------
ANS4212E

The Deployment Manager failed to restart service: servicename



Explanation:

After the automatic client deployment, the IBM Spectrum Protect client
services failed to start.

System action:

Processing stops.

User response:

Log on to the client machine and check the backup-archive client error
log.

------------------------------------------------------------------------
ANS4213E

Automatic restart of the client computer was required because reason



Explanation:

The Deployment Manager determined that the deployment requires
restarting the client.

Automatic restart is not enabled. The Deployment Manager process cancels
the deployment.

The current client is not uninstalled or updated.

System action:

Deployment Manager cancels the client deployment and stops

User response:

Reschedule the client deployment.

------------------------------------------------------------------------
ANS4215E

The automatic deployment path from the current client code version
'source version' to the client package version 'target version' is not
supported.



Explanation:

None

System action:

Processing stops.

User response:

Refer to the Backup-Archive Client documentation in the information
center.

Reschedule the client deployment with an appropriate target level.

------------------------------------------------------------------------
ANS4217E

The Deployment Manager received an error while setting up the client
API. The standard API function being invoked is API setup function name.



Explanation:

The Deployment Manager process failed when setting up the client API.

System action:

Processing stops.

User response:

Check the error log on the client computer.

------------------------------------------------------------------------
ANS4218E

The Deployment Manager received an error while initializing the client
API. The standard API function being invoked was API setup function
name.



Explanation:

The Deployment Manager process failed when initializing the client API.

System action:

Processing stops.

User response:

Check the error log on the client computer.

------------------------------------------------------------------------
ANS4219E

The Deployment Manager received an error while creating a pipe for the
standard output of the child process.



Explanation:

The Deployment Manager failed to create a pipe for the standard output
of the child process.

System action:

Processing stops.

User response:

Check the error log on the client computer.

------------------------------------------------------------------------
ANS4220E

The Deployment Manager is unable to determine if IBM Spectrum Protect
processes are still running.



Explanation:

The Deployment Manager could not determine whether all IBM Spectrum
Protect processes were shut down successfully.

System action:

Reschedule with automatic restart (autoreboot) enabled.

User response:

None

------------------------------------------------------------------------
ANS4221E

The architecture of the package: 'package architecture' does not match
the current client: 'system architecture'



Explanation:

The setup script was unable to retrieve the matching package from the
server.

System action:

Processing stops.

User response:

Ensure that the client packages for all architectures are available on
the server.

------------------------------------------------------------------------
ANS4222E

The Deployment Manager is unable to read information in file: file name.



Explanation:

Deployment Manager failed to open a file containing required system
information.

System action:

Processing stops.

User response:

Check the error log on the client computer.

------------------------------------------------------------------------
ANS4227E

The Deployment Manager failed to install package: 'client package name'.
The client computer is out of disk space. The Microsoft Installer error
code was 'error code'



Explanation:

The previous client package has been uninstalled, and the installation
of the new client package failed because the client computer is out of
disk space.

System action:

Processing stops.

User response:

Check the technote for Microsoft Installer error code description:
http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

------------------------------------------------------------------------
ANS4228E

The Deployment Manager failed to install language pack: 'language pack
name'. The client computer is out of disk space. The Microsoft Installer
error code was 'error code'



Explanation:

The previous language pack has been uninstalled, and the installation of
the new language pack failed because the client computer is out of disk
space.

System action:

Processing continues.

User response:

Check the technote for Microsoft Installer error code description:
http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

------------------------------------------------------------------------
ANS4229I

The client computer is required to restart to complete the new
Backup-Archive client installation.



Explanation:

The deployment of the new backup-archive client will not be complete
until the client computer is restarted. The restart is scheduled to
happen immediately after all language packs are deployed.

System action:

The Deployment Manager process continues. The client computer will be
shut down and restarted after all language packs are deployed, or
immediately if there are no language pack to install.

User response:

None

------------------------------------------------------------------------
ANS4230I

The client computer will be shut down and restarted immediately.



Explanation:

The Deployment Manager needs to restart the client computer to complete
the client deployment. It is possible the other messages provide details
of the deployment.

System action:

The Deployment Manager process continues. The client computer will be
shut down and restarted immediately after all language packs are
deployed, or immediately if there are no language pack to install.

User response:

None

------------------------------------------------------------------------
ANS4232E

Self-extracting installation image: image name cannot be found.



Explanation:

The Deployment Manager could not find the required installation image.

System action:

Processing stops. Client deployment will be cancelled.

User response:

Check the server's activity log or the scheduler log on the client
computer. Reshcedule the client deployment.

------------------------------------------------------------------------
ANS4234E

The deployment for language packs failed.



Explanation:

The Deployment Manager failed to install one or more language packs. It
is possible the other messages provide details of the installation.

System action:

The Deployment Manager process continues.

User response:

Check the error log and installation on the client computer. Identify
the language packs that failed to install and manually deploy them.

------------------------------------------------------------------------
ANS4235I

The deployment manager cannot log events to the server.



Explanation:

The Deployment Manager is unable to log events to the server. It is
possible the other messages provide details of the communications.

System action:

The Deployment Manager process continues. Events will be logged locally
on the client machine only.

User response:

Check network connection and the error log on the client computer.

------------------------------------------------------------------------
ANS4242E

The setup script encountered a warning or error while retrieving the
client package for the architecture architecture. The error level is
error level error level.



Explanation:

It is possible that the client package is not available on the server.

System action:

Processing stops.

User response:

Ensure that client packages for all architectures are available on the
server. Check the backup-archive client error log for more detailed
error messages.

------------------------------------------------------------------------
ANS4248E

The client is already at the target level: target version.



Explanation:

Processing stopped because the automatic client deployment feature does
not support the installation of a client to a workstation that is
already at its target level.

System action:

Your current backup-archive client is not affected.

User response:

Refer to the Backup-Archive Client documentation in the information
center.

Reschedule the client deployment with an appropriate target level.

------------------------------------------------------------------------
ANS4251W

writername file 'filename': not found.



Explanation:

The indicated VSS writer file or directory was returned by VSS as part
of the backup file list of the writer. However, the object does not
exist on the disk..

System action:

Processing stops if SKIPMISSINGSYSWFILES option is set to NO. Processing
continues if SKIPMISSINGSYSWFILES option is set to YES.

User response:

Verify that this file can be skipped during system state backup.

------------------------------------------------------------------------
ANS4252W

architecture, schedule-name, domain-name : The client deployment was not
completed pending the restart of the client computer. The deployment
manager did not restart the client computer automatically because the
AUTODEPLOY option was set to NOREBOOT.



Explanation:

The previous client has been uninstalled, and the installation of the
new client was not completed pending the restart of the client computer.
The architecture of the client, schedule name, and domain name are
identified at the beginning of the message text.

System action:

The Deployment Manager process completes.

User response:

Manually restart the client computer as soon as possible.

------------------------------------------------------------------------
ANS4253E

There was not enough disk space on the client computer. Required space:
package space bytes; available space: system space bytes.



Explanation:

The deployment manager determined there was insufficient free disk space
for the client deployment.

System action:

Processing stops.

User response:

Free up required disk space and reschedule the client deployment.

------------------------------------------------------------------------
ANS4254E

The deployment manager detected an HSM client on the workstation that it
needs to deploy the Backup-Archive client to.



Explanation:

An attempt was made to deploy the Backup-Archive client to a workstation
that already has the HSM client installed. The Backup-Archive client
cannot be deployed to a workstation that has the HSM client.

System action:

Processing stops.

User response:

Uninstall the HSM client and reschedule the Backup-Archive client
deployment.

------------------------------------------------------------------------
ANS4255E

There is not enough memory for the deployment manager to create the
system information object



Explanation:

The system information object could not be created because there is not
enough available RAM to temporarily write the data into.

System action:

Processing stops.

User response:

Close all unneeded applications on the client workstation and reschedule
the deployment.

------------------------------------------------------------------------
ANS4256E

The DSMI_DIR environment variable is not defined.



Explanation:

The deployment manager cannot initiate a connection to the server
because the DSMI_DIR environment variable is not set. This error can
occur if the deployment manager is started without using the client
scheduler.

System action:

Processing stops.

User response:

Read the available documentation to determine how to use the client
scheduler to create a client deployment task.

------------------------------------------------------------------------
ANS4257E

The deployment manager cannot parse information in file: file name.



Explanation:

The deployment manager could not parse or extract the required
information from the specified file.

System action:

Processing stops.

User response:

Check the error log file on the client workstation.

------------------------------------------------------------------------
ANS4258E

The deployment manager received the Windows "OpenSCManager failed" error
message.



Explanation:

The deployment manager could not connect to the Windows service control
manager to start the client scheduler. In general, this error occurs
because the user who is initiating the task does not have sufficient
authority.

System action:

Processing stops.

User response:

Ensure that the user who starts the client scheduler has administrative
privileges.

------------------------------------------------------------------------
ANS4259E

The client scheduler is not started as a root user.



Explanation:

The client scheduler requires root user privileges to upgrade the client
code.

System action:

Processing stops.

User response:

Log in as root and start the client scheduler.

------------------------------------------------------------------------
ANS4260E

The installation file system is not writeable.



Explanation:

The deployment manager cannot write to the installation file system.

System action:

Processing stops.

User response:

Check the installation file system permissions. It is possible that the
current client node runs in a virtualized environment using the client
code installed in a shared storage of the physical environment.
Reschedule the client deployment with the client node in the physical
environment.

------------------------------------------------------------------------
ANS4261E

The deployment manager cannot upgrade the Backup-Archive Client.



Explanation:

The Backup-Archive Client cannot be upgraded because either the current
location is not the default installation location or the DSM_DIR,
DSMI_DIR, DSM_CONFIG and DSMI_CONFIG environment variables are defined
with a relative path and not an absolute path.

System action:

Processing stops.

User response:

Check the installation directory of the current Backup-Archive Client.
If the Backup-Archive Client is not installed in the default location,
manually upgrade the Backup-Archive Client. If the DSM_DIR, DSMI_DIR,
DSM_CONFIG and DSMI_CONFIG environment variables are defined with a
relative path, define them with an absolute path and try the client
deployment again.

------------------------------------------------------------------------
ANS4262E

The preview of the client installation failed.



Explanation:

The deployment manager did not uninstall the current client. The client
code is unchanged.

System action:

Processing stops.

User response:

Check the deployment manager log and trace files on the client
workstation for specific issues identified during the preview.
Reschedule a deployment after any issues are resolved.

------------------------------------------------------------------------
ANS4263E

The deployment manager failed to uninstall the backup-archive client.



Explanation:

The deployment manager received an error while uninstalling the current
client.

System action:

Processing stops.

User response:

Check the deployment manager log and trace files on the client
workstation for more details on the error. You might have to manually
uninstall the client.

------------------------------------------------------------------------
ANS4264E

The deployment manager failed to install the backup-archive client.



Explanation:

The current client was uninstalled and the deployment manager received
an error while installing the new client code.

System action:

Processing stops.

User response:

Check the deployment manager log and trace files on the client
workstation for more details on the error. Manully install the new
client after the issue is resolved.

------------------------------------------------------------------------
ANS4265I

Client deployment options are not specified in the scheduler command or
from client services.



Explanation:

The default client options file will be used. The deployment manager
might not report the correct server and node information when reporting
status.

System action:

Processing continues.

User response:

Avoid initiating the client deployment directly from the command-line,
instead, always start the client scheduler as a Windows service.

------------------------------------------------------------------------
ANS4266I

The deployment manager failed to install non-English language pack(s).



Explanation:

The previous packages were uninstalled, and the installation of one or
more new language packs were not successful.

System action:

Processing continues.

User response:

Check the deployment trace file on the client workstation for specific
language pack information.

------------------------------------------------------------------------
ANS4267I

The deployment manager failed to install the hardware plugin package.



Explanation:

The previous package was uninstalled. The installation of the new
hardware plugin package failed.

System action:

Processing stops.

User response:

Check the deployment trace file on the client workstation.

------------------------------------------------------------------------
ANS4268I

The deployment manager failed to install the journal-based backup
package.



Explanation:

The previous journal-based backup package was uninstalled. The new
journal based backup package installation failed.

System action:

Processing stops.

User response:

Check the deployment trace file on the client workstation.

------------------------------------------------------------------------
ANS4269W

The deployment manager is stopping the scheduler or the CAD processes.



Explanation:

Before deploying the new client, the deployment manager must stop the
scheduler and CAD processes. After the deployment, the processes must be
restarted.

System action:

Processing continues.

User response:

The client scheduler is interrupted during the deployment.

------------------------------------------------------------------------
ANS4270I

The deployment manager and the new client installation packages were
downloaded to directory: file name.



Explanation:

The download directory contains everything required to complete the new
client deployment. Deployment log and trace files can be found in the
log/ sub-directory.

System action:

Processing continues.

User response:

Obtain log and trace files from the download directory for problem
determination. The files are found within the log/ sub-directory.

------------------------------------------------------------------------
ANS4271E

The deployment package is missing one or more required installation
image files.



Explanation:

The client deployment package might not have been imported correctly to
the server. It is possible that the deployment package is not retrieved
completely to the client computer, due to a lack of disk space.

System action:

Processing stops.

User response:

Ensure that client packages are available on the server and there is
sufficient disk space on the client computer. Check the backup-archive
client error log file for more detailed error messages.

------------------------------------------------------------------------
ANS4272E

The processor type of the package: package processor type does not match
the current client: system processor type..



Explanation:

The processor type supported by the client package that you want to
deploy does not match the processor type of the workstation that you are
trying to deploy the client to. It is not always possible for the
deployment manager to connect to the server and report the error.

System action:

Processing stops.

User response:

Verify that you are using the correct client package for the processor
architecture of the computer that you want to upgrade. Then restart the
deployment.

------------------------------------------------------------------------
ANS4273E

The deployment manager detected a journal based backup (JBB) client on
the workstation where it needs to deploy the Backup-Archive Client.



Explanation:

An attempt was made to deploy the Backup-Archive Client to a workstation
that already has the JBB client installed. On some platforms, the
Backup-Archive Client cannot be deployed to a workstation that has the
JBB client installed.

System action:

Processing stops.

User response:

Uninstall the JBB client and reschedule the Backup-Archive Client
deployment.

------------------------------------------------------------------------
ANS4274E

The deployment manager cannot stop the scheduler or the CAD processes.



Explanation:

The deployment manager tried to shut down the Backup-Archive Client
scheduler or CAD processes but the Backup-Archive Client might be busy
with other tasks.

System action:

Processing stops.

User response:

Reschedule the Backup-Archive Client deployment.

------------------------------------------------------------------------
ANS4275E

The deployment manager cannot restart the scheduler or the CAD
processes.



Explanation:

Before exiting, the deployment manager could not restart the
Backup-Archive Client scheduler or CAD processes. The deployment manager
stopped the processes prior to the client upgrade.

System action:

Processing continues.

User response:

Log on to the Backup-Archive Client workstation and check the error log
file. If you have set environment variables make sure they are not
defined using relative path.

------------------------------------------------------------------------
ANS4276E

The deployment manager cannot obtain information about the scheduler or
the CAD processes.



Explanation:

The deployment manager needs process information in order to stop and
restart the Backup-Archive Client scheduler or CAD processes.

System action:

Processing stops.

User response:

Log on to the Backup-Archive Client workstation and check the error log
file and the deployment manager error log file.

------------------------------------------------------------------------
ANS4277E

The target operating system version target operating system does not
meet the minimum required version minimum required version



Explanation:

The operating system version is earlier than the version required by the
automatic deployment package.

System action:

The deployment is canceled.

User response:

Ensure that the version being deployed is supported by the target
operating system.

------------------------------------------------------------------------
ANS4278E

The deployment manager cannot obtain information about the Logical
Volume Snapshot Agent (LVSA).



Explanation:

The deployment manager needs to determine whether an LVSA is installed
on the client workstation.

System action:

Processing stops.

User response:

Log on to the Backup-Archive Client workstation and check the error log
file and the deployment manager error log file.

------------------------------------------------------------------------
ANS4280E

Automatic client deployment is not allowed on the client workstation.



Explanation:

One or more of the running client services include AUTODEPLOY = NO in
the option file.

System action:

Processing stops.

User response:

Change the AUTODEPLOY option on the client and reschedule the client
deployment.

------------------------------------------------------------------------
ANS4281E

The update manager cannot remove the TIVsmCapi package from non-global
zone(s): zone name.



Explanation:

APAR IC57433 prevents the removal of the TIVsmCapi package on Solaris on
a sparse-root, non-global zone if uninstalling is done from the global
zone.

System action:

Processing stops.

User response:

Manually uninstall the IBM Spectrum Protect client directly from the
non-global zones and reschedule the deployment.

------------------------------------------------------------------------
ANS4282E

Sparse-root non-global zone(s) were found with IBM Spectrum Protect
Backup-Archive Client that was installed from the non-global zone: zone
names.



Explanation:

One or more non-global zones are sharing the /usr file system with the
global zone. The IBM Spectrum Protect Backup-Archive Client is installed
in the global zone with the -G parameter and also installed manually in
the non-global zone(s). You cannot update the IBM Spectrum Protect
Backup-Archive Client in the global zone because it will update the
version of GSKit that is shared with the sparse-root non-global zones
that are not part of the automatic deployment.

System action:

Processing stops.

User response:

Manually upgrade the Backup-Archive Client or install it from the global
zone without using the -G parameter. This ensures that you have the same
version between the global zone and the sparse-root non-global zones,
and you can then deploy the client automatically on all such zones.

------------------------------------------------------------------------
ANS4283E

There is not enough disk space on path to uncompress GSKit packages.
Required space: req_space bytes; available space: avail_space bytes.



Explanation:

The deployment manager determined that there is not enough free disk
space to uncompress GSKit packages.

System action:

Processing stops.

User response:

Free up the required amount of disk space and reschedule the automatic
client deployment.

------------------------------------------------------------------------
ANS4284E

The deployment is cancelled because an automatic client deployment task
was scheduled for a sparse-root, non-global zone that shares the /usr
file system with the global zone.



Explanation:

The automatic client deployment task that was attempted is not supported
and will be cancelled.

System action:

Processing stops.

User response:

Install the Backup-Archive Client from the global zone or manually
upgrade the Backup-Archive Client.

------------------------------------------------------------------------
ANS4285E

The update restore operation to an existing virtual machine 'VmName'
failed. The virtual machine is not in power off state.



Explanation:

The update restore operation to an existing virtual machine is not
supported for a running machine and will be aborted.

System action:

Restore aborted.

User response:

Turn off the virtual machine and re-run the update restore command.

------------------------------------------------------------------------
ANS4290E

Only one virtual machine can be selected for restore.



Explanation:

Restoring multiple virtual machines is not allowed. Only one virtual
machine can be selected for restore.

System action:

No processing occurs.

User response:

Select only one virtual machine for restore.

------------------------------------------------------------------------
ANS4291E

Virtual Machine could not be found on VMware server.



Explanation:

The backup of virtual machine failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4292E

No virtual machine found.



Explanation:

No virtual machine found with name or specified in domain option.

System action:

Processing stopped.

User response:

Specify a correct VM name or domain option.

------------------------------------------------------------------------
ANS4293E

Backup of VMware vApp 'vApp name' in Organization VDC 'Org VDC name' of
organization 'Org name' failed.



Explanation:

The vApp backup operation failed. This error message is a summary
message and does not contain detailed information.

System action:

The configuration information and VMs for the specified vApps are not
backed up. Processing continues to the next vApp.

User response:

Check the previous messages in the dsmerror.log file for more details
about this vApp .

------------------------------------------------------------------------
ANS4295W

The virtual machine 'vmname' was backed up using the Windows VSS system
provider. You must manually revert or delete the shadow copy on the
restored volumes or you may experience degraded performance and an
out-of-space condition.



Explanation:

At backup time, application protection was not able to back up the VM
within the 10-second VSS limit. Therefore, the Windows VSS system
provider was used. If you are restoring the application, the volume will
be automatically reverted. However, if you are restoring the entire VM,
you must manually revert or delete the shadow copy.

System action:

The virtual machine is restored, including the system provider shadow
copy.

User response:

Verify that the restore was successful, and the data is not corrupt. If
the data is not corrupt, you can delete the shadow copy. However, if the
data is corrupt, revert the shadow copy to restore data integrity. You
can figure out which shadow copy to delete or revert by looking for the
dsmShadowCopyID.txt file in the root directory of each restored volume.
Then, use the diskshadow delete or revert command.

------------------------------------------------------------------------
ANS4296I

architecture, schedule-name, domain-name: The Deployment Manager process
was started successfully. Deployment Manager Version Information:
version



Explanation:

The Deployment Manager process was started as a post schedule command.
This is the first message from the Deployment Manager. The architecture
of the client, schedule name, and domain name are identified at the
beginning of the message text.

System action:

Deployment Manager continues to process.

User response:

None

------------------------------------------------------------------------
ANS4297W

architecture, schedule-name, domain-name: Client deployment was
completed with warnings:



Explanation:

This is a generic warning message. It is possible the other messages
provide details of the deployment. The architecture of the client,
schedule name, and domain name are identified at the beginning of the
message text.

System action:

The Deployment Manager process completes.

User response:

Check the warning messages from the server administration center, the
server activity log, or error log on the client computer for more
information.

------------------------------------------------------------------------
ANS4298E

architecture, schedule, new_device_type: The client deployment was
cancelled. The previous event causing the cancellation is:



Explanation:

This is a generic message that the client deployment was cancelled. The
Deployment Manager does not uninstall or update the current client. It
is possible the other messages provide details of the deployment. The
architecture of the client, schedule name, and domain name are
identified at the beginning of the message text.

System action:

Processing stops.

User response:

Check the warning messages from the server administration center, the
server activity log, or error log on the client computer for more
information.

------------------------------------------------------------------------
ANS4299E

architecture, schedule-name, domain-name: The client deployment failed.
The previous event causing the failure is: event



Explanation:

This is a generic message that the client deployment failed. It is
possible that other messages provide details of the failure. The
architecture of the client, schedule name, and domain name are
identified at the beginning of the message text.

System action:

Processing stops.

User response:

Check the warning messages from the server administration center, the
server activity log, or error log on the client computer for more
information.

------------------------------------------------------------------------
ANS4300I

architecture, schedule-name, domain-name: Client deployment was
completed successfully.



Explanation:

The Deployment Manager process completes.

System action:

Processing stops.

User response:

None

------------------------------------------------------------------------
ANS4301I

IBM Spectrum Protect detected Microsoft Active Directory Domain
Controller on virtual machine 'VM'.



Explanation:

The virtual machine contains Microsoft Active Directory Domain
Controller.

System action:

IBM Spectrum Protect saved additional information about this virtual
machine.

User response:

None

------------------------------------------------------------------------
ANS4302W

IBM Spectrum Protect failed to detect if Microsoft Active Directory
Domain Controller on virtual machine 'VM'.



Explanation:

There was an error while checking if the virtual machine contains
Microsoft Active Directory Domain Controller.

System action:

IBM Spectrum Protect continues backing up this virtual machine.

User response:

Check IBM Spectrum Protect error log for additional information.

------------------------------------------------------------------------
ANS4303E

The vCloud Director vApp 'vapp-name' has not been previously backed up.



Explanation:

The specified vCloud Director vApp has not been previously backed up, so
can not be specified for restore.

System action:

The specified vCloud Director vApp is skipped, and the next vApp in the
restore list is processed.

User response:

Verify the vCloud Director vApp name to be restored, and re-try the
operation.

------------------------------------------------------------------------
ANS4304I

IBM Spectrum Protect could not detect the IBM Spectrum Protect for
Virtual Environments license. Active Directory Domain Controller will
not be protected on VM 'VM'.



Explanation:

The virtual machine contains Microsoft Active Directory Domain
Controller, but a IBM Spectrum Protect for Virtual Environments license
is not detected. The Domain Controller will not be protected.

System action:

Install IBM Spectrum Protect for Virtual Environments 7.1 or later to
protect Active Directory.

User response:

None

------------------------------------------------------------------------
ANS4305W

Backup of VMware vApp 'vApp name' in Organization VDC 'Org VDC name' of
organization 'Org name' completed. Some VMs were not backed up. mode:
'Incremental Forever - full_or_incr' target node name:
'target_node_name' data mover node name: 'data_mover_node_name' VMs
backup status: number of VM backed up out of number of VMs in vApp VMs
backed up successfully.



Explanation:

The vApp backup operation completed successfully. However, one or more
VMs for the specified vApp were not backed up. These VMs will not be
created during the restore operation.

System action:

Processing continues to the next vApp.

User response:

Check the dsmerror.log file for this vApp for more information about
this message. Resolve the problem, then try the operation again.

------------------------------------------------------------------------
ANS4308E

Full VM backup of 'hypervisor' Virtual Machine 'vmname' failed with
RC=rc mode=full_or_incr, target node name='target_node_name', data mover
node name='data_mover_node_name'



Explanation:

The Full VM backup of virtual machine failed.

System action:

The full backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4311E

Full VM restore of 'hypervisor' Virtual Machine 'vmname' failed with
RC=rc target node name='target_node_name', data mover node
name='data_mover_node_name'



Explanation:

The Full VM restore of the virtual machine failed.

System action:

The full restore of the the virtual machine finished with failures. The
next virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4313I

Rebalance Schedule sched-name Type: balance-type



Explanation:

A rebalance operation was requested for the named schedule. A rebalance
can be complete or minimal. A Minimal rebalance is performed
automatically at the end of each schedule. You can configure a complete
rebalance by using the option settings, VMREBALANCESCHEDULEPERIOD and
VMREBALANCESCHEDULEONLY.

System action:

The rebalance operation begins.

User response:

No action is required.

------------------------------------------------------------------------
ANS4319E

Rebalance schedule error occurred while processing the timestamp file.



Explanation:

An error occurred while a tagged schedule was processing a local
timestamp file. The timestamp file will be recreated after the next
schedule is run.

System action:

The schedule completed.

User response:

The timestamp file name is based on the schedule name. It has the format
"rebalance_timestamp_schedulename.file" Deleting the file may help. The
timestamp file will be recreated after the next schedule is run.

------------------------------------------------------------------------
ANS4441E

'fs' is a 'fstype' file system, which is not a supported file system
type for file backup, image backup or archive.



Explanation:

The specified file system is not supported for any type of backup. IBM
Spectrum Protect does not support backup and archive or image backup for
this type of volume.

System action:

The file system is skipped. Processing continues with the next file
system.

User response:

Refer to the IBM Spectrum Protect client manual for a complete list of
supported file systems.

------------------------------------------------------------------------
ANS4442E

'VM-Name' a backup cannot be created because the virtual machine has
assigned disk with duplicate disk identifiers.



Explanation:

The client detected that the virtual machine has assigned disk with
duplicate disk identifiers. The disk may have been copied. A backup
cannot be created on a virtual machine that have duplicate disk
identifiers.

System action:

The virtual machine is not backuped. Processing continues with the next
virtual machine.

User response:

Check that the virtual disks has diffrent disk identifiers and update
the virtual machine configuration to match any changes to the file
system. If the problem persists, contact an administrator of the Hyper-V
server.

------------------------------------------------------------------------
ANS4443E

'fs' is a CSVFS file system, which is not a supported file system type
for file backup, image backup or archive.



Explanation:

Microsoft Cluster Shared Volumes File Systems (CSVFS) are NTFS or ReFS
volumes that are added to Cluster Shared Volumes. These volumes are
intended for Hyper-V and expanded support for SQL, not for regular file
data. IBM Spectrum Protect does not support file level backup and
archive or image backup for CSVFS volumes.

System action:

The file system is skipped. Processing continues with the next file
system.

User response:

Refer to the IBM Spectrum Protect client manual for a complete list of
supported file systems.

------------------------------------------------------------------------
ANS4446E

A file restore mount operation for hypervisor type Virtual Machine
'vmname' failed. The data center node name is 'data center node name',
the mount proxy node name is 'mount proxy node name'.



Explanation:

The file restore mount operation of the virtual machine failed.

System action:

The mount of the virtual machine finished with failures.

User response:

Review the local client error log for the reason for the failure.

------------------------------------------------------------------------
ANS4449E

A cleanup of the file restore mount of hypervisor type Virtual Machine
'vmname' failed. The data center node name is 'data center node name',
the mount proxy node name is 'mount proxy node name'.



Explanation:

The cleanup of file restore mount operation of the virtual machine
failed.

System action:

The cleanup of mount of the virtual machine finished with failures.

User response:

Review the local client error log for the reason for the failure.

------------------------------------------------------------------------
ANS4450E

The mount proxy platform is not supported for file restore mount
operations.



Explanation:

The file restore mount operation failed. The mount proxy platform is
unsupported or the IBM Spectrum Protect Recovery Agent is not correctly
installed and configured.

System action:

The file restore mount operation failed.

User response:

Ensure that the IBM Spectrum Protect Recovery Agent is installed and
configured correctly and run the file restore mount operation from a
supported mount proxy platform.

------------------------------------------------------------------------
ANS4451E

The Windows iSCSI service is not available.



Explanation:

The Windows iSCSI service is not available on the mount proxy machine.
It is either not started or is not installed or configured correctly.

System action:

Processing stops. The file restore mount operation fails.

User response:

Ensure that the iSCSI service is up and running on the mount proxy
machine.

------------------------------------------------------------------------
ANS4900W

Schedule 'schedule-name' has opened a new session with the server.



Explanation:

A scheduled event endsbecause of a connection failure. The scheduled
event had to be restarted outside its normal startup window to continue
the operation.

System action:

The scheduled event is completed using more than one session.

User response:

None required. If this is a recurrent condition, you may want to check
for network problems.

------------------------------------------------------------------------
ANS4901E

The following object contains one or more unmatched quotation marks and
cannot be processed: 'filespace path filename'.



Explanation:

The file name in the file list contains unmatched quotes. If a line in
the file list begins with a single or double quotation mark this
quotation mark is considered to be an opening quotation mark. The
corresponding closing quotation mark of the same type must be at the end
of the line. If there is no closing quotation mark or the closing
quotation mark has been encountered in the middle of the line, it is an
invalid input.

System action:

The object is skipped.

User response:

Correct the specification of the object.

------------------------------------------------------------------------
ANS4904E

The instant access operation for the 'vmname' virtual machine failed.
The target node is 'target_node_name and the data mover node is
'data_mover_node_name'.



Explanation:

The instant access operation for the virtual machine failed.

System action:

Errors occurred and the instant access operation did not complete.

User response:

See the client error log to determine the cause of the failure.

------------------------------------------------------------------------
ANS4907E

Instant restore of VMware Virtual Machine 'vmname' failed. target node
name='target_node_name', data mover node name='data_mover_node_name'



Explanation:

The instant restore of the virtual machine failed.

System action:

The instant restore of the the virtual machine finished with failures.
The reason for the failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS4910E

The cleanup operation for the 'vmname' virtual machine failed. The
target node is 'target_node_name' and the data mover node is
'data_mover_node_name'.



Explanation:

The cleanup operation for the virtual machine failed.

System action:

Errors occurred and the cleanup operation did not complete.

User response:

See the client error log to determine the cause of the failure.

------------------------------------------------------------------------
ANS4915I

Object increased in size during compression: filespace pathfilename



Explanation:

The file increased in size during compression.

System action:

Processing contiues.

User response:

None.

------------------------------------------------------------------------
ANS4917E

A failure occurred while accessing the VMware libraries. The required
files for the virtual machine backup were not found. The files are
installed only if the client is defined as a data mover in IBM Spectrum
Protect for Virtual Environments.



Explanation:

A failure occurred while accessing the VMware libraries for the virtual
machine environment.

System action:

The backup operation cannot continue.

User response:

Install the IBM Spectrum Protect for Virtual Environments package to use
the client to back up virtual machines.

------------------------------------------------------------------------
ANS4936E

The snapshot of virtual machine 'vmname' failed and a snapshot cannot be
attempted again.



Explanation:

The snapshot of the virtual machine failed with a permanent error. Such
as the Hyper-V writer is not responding. Another snapshot attempt will
not be made.

System action:

The snapshot of the virtual machine finished with an error. Processing
continues to the next virtual machine.

User response:

Check the Windows event log for the reason for the failure.

------------------------------------------------------------------------
ANS4937I

Resending file file in a new transaction session to recover from the
transmission error.



Explanation:

None.

System action:

The file is resent.

User response:

None.

------------------------------------------------------------------------
ANS4938I

Virtual machine: 'vm-name' disk: 'disk-name' is excluded by size.



Explanation:

The option file or command given excluded the disk from backup
processing.

System action:

The disk is not processed.

User response:

If the disk is intentionally excluded, then this message is expected
behavior. Otherwise modify the command or option file to include the
disk.

------------------------------------------------------------------------
ANS4942E

The file specification 'string' is invalid.



Explanation:

The operating system indicated that the file specification is invalid.
One possible reason is that the file specification contains unrecognized
characters. Another possible cause is incorrect use of quotation marks
in the file specification.

System action:

Processing stopped.

User response:

Enter a correct file specification as described in the Using the
Backup-Archive Client book for the particular operating system. Ensure
that the file specification contains valid characters. Verify correct
use of quotation marks for specifications that contain blanks spaces. If
multiple file specifications are used, make sure that any use of
quotation marks does not cause the file specifications to be treated as
a single file specification.

------------------------------------------------------------------------
ANS4944I

Virtual machine: 'vm-name' disk: 'disk-name' is excluded by user.



Explanation:

The option file or command given excluded the disk from backup
processing.

System action:

The disk is not processed.

User response:

If the disk is intentionally excluded, then this message is expected
behavior. Otherwise modify the command or option file to include the
disk.

------------------------------------------------------------------------
ANS4946W

Warning: virtual machine: 'vm-name' disk: 'disk-name' excluded by user,
was not found.



Explanation:

The specified virtual disk does not exist on the virtual machine.

System action:

Processing continues.

User response:

Use the "dsmc backup vm ..." command with the -preview option to display
a listing of the disk labels which exist on the virtual machine. Since
the disk was specified to be excluded from the backup, the backup will
continue. However it is possible that a disk will included in the backup
which was not desired, check the spelling of the disk label, and correct
the disk label if an undesired disk is now included in the backup
operation.

------------------------------------------------------------------------
ANS4947E

Error: virtual machine: 'vm-name' disk: 'disk-name' included by user,
was not found.



Explanation:

The specified virtual disk does not exist on the virtual machine.

System action:

Processing stops.

User response:

Use the "dsmc backup vm ..." command with the -preview option to display
a listing of the disk labels which exist on the virtual machine. Check
the spelling of the disk label and correct the disk label and then retry
the 'backup vm' operation.

------------------------------------------------------------------------
ANS4948E

A specified virtual disk was not found on the virtual machine.



Explanation:

You must specify a virtual disk label name which exists on the virtual
machine.

System action:

Processing stops.

User response:

For a backup operation, use the "dsmc backup vm ..." command with the
-preview option to display a listing of the disk labels which exist on
the virtual machine. For a restore operation, use the "dsmc query vm
..." command with the -detail option to display a listing of the disk
labels which exist on the virtual machine backup. Check the spelling of
the disk label and correct the disk label and then retry the operation.

------------------------------------------------------------------------
ANS4972W

File server file-server-name has been upgraded to Data ONTAP version
'version.modifcation.submodification'. This version does not support
unicode file names for snapshot difference incremental backup. Upgrade
to a version that supports unicode file names as soon as possible.



Explanation:

The file server has been upgraded from a version that supports unicode
file names for incremental backup using snapshot difference to a version
that does not. If you have upgraded from Data ONTAP version 7.3.3 (or
later) to 8.0, you lose the ability to back up files with unicode file
names when performing snapshot difference incremental backup.

System action:

Processing continues. However, files with unicode names are not backed
up.

User response:

Upgrade to a version that supports unicode file names as soon as
possible. If you have upgraded from Data ONTAP version 7.3.3 (or later)
to 8.0, upgrade to 8.1 (or later). If it is not possible to upgrade at
this time, you can suppress this warning message by renaming the file
space on the IBM Spectrum Protect server and performing a snapshot
difference incremental backup.

------------------------------------------------------------------------
ANS4973E

An error occurred accessing NTFS security information for file
'filespace namepath-namefile-name'



Explanation:

An access denied error occurred while attempting to access NTFS security
info rmation.

System action:

The object is skipped.

User response:

See your system administrator or bypass the failing check by using
SkipNTSecu rity option.

------------------------------------------------------------------------
ANS4974E

Error processing 'filespace namepath-namefile-name': a required NT
privilege is not held.



Explanation:

The user account running IBM Spectrum Protect does not possess a
required NT user right/pr ivilege for performing the current operation.

System action:

The object is skipped.

User response:

Your system administrator has the authority to grant the needed
privilege.

------------------------------------------------------------------------
ANS4987E

Error processing 'filespace namepath-namefile-name': the object is in
use by another process



Explanation:

The specified file is being used by another process. You tried to read
from or write to a file that is currently being used by another process.

System action:

File skipped.

User response:

Ensure that the file is not locked by another process. If the file is
not locked, retry the command.

------------------------------------------------------------------------
ANS4988W

File 'filespace namepath-namefile-name' is currently unavailable on
server and has been skipped.



Explanation:

You tried to restore or retrieve a file that is currently not available
from the IBM Spectrum Protect server. This is most likely a temporary
condition.

System action:

IBM Spectrum Protect cannot restore or retrieve the file.

User response:

Try to restore or retrieve the file again after the file becomes
available on the server. If the problem persists, see your IBM Spectrum
Protect administrator for assistance.

------------------------------------------------------------------------
ANS4989E

Error processing 'filespace namepath-namefile-name': the directory is in
use by another process. All objects in the directory and any of its
subdirectories are skipped.



Explanation:

The specified directory is being used by another process. You tried to
read from or write to a directory that is currently being used by
another process. The objects contained in the directory and its
subdirectories are not backed up.

System action:

Processing stopped for that directory. If other files and directories
were also specified in this backup, they are processed

User response:

Ensure that you specified the correct directory name, correct the
permissions, or specify a new location.If the directory name is correct,
retry the backup when no process has exclusive use of the directory.

------------------------------------------------------------------------
ANS4991I

Application Type Application Message Id Application Message



Explanation:

This is a message sent by the application you are currently running with
IBM Spectrum Protect.

System action:

IBM Spectrum Protect logs the application message.

User response:

Refer to the documentation for the application that you are using.

------------------------------------------------------------------------
ANS4992W

Application Type Application Message Id Application Message



Explanation:

This is a message sent by the application you are currently running with
IBM Spectrum Protect.

System action:

IBM Spectrum Protect logs the application message.

User response:

Refer to the documentation for the application that you are using.

------------------------------------------------------------------------
ANS4993E

Application Type Application Message Id Application Message



Explanation:

This is a message sent by the application you are currently running with
IBM Spectrum Protect.

System action:

IBM Spectrum Protect logs the application message.

User response:

Refer to the documentation for the application that you are using.

------------------------------------------------------------------------
ANS4994S

Application Type Application Message Id Application Message



Explanation:

This is a message sent by the application you are currently running with
IBM Spectrum Protect.

System action:

IBM Spectrum Protect logs the application message.

User response:

Refer to the documentation for the application that you are using.

------------------------------------------------------------------------
ANS4997E

Error processing 'filespace namepath-namefile-name': file system quota
reached condition - no space left.



Explanation:

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:

Select the appropriate action for this object. Create some free space or
increase the quota on the destination file system before you retry the
operation. Another option is to restore or retrieve the file to another
file system.

------------------------------------------------------------------------
ANS4998E

Link information for file 'filename' could not be obtained: access to
the object is denied.



Explanation:

Access to the specified file link is denied. You tried to read
information for file link and you do not have access permission for this
object.

System action:

Processing of System State stops.

User response:

Try the operation again. If the problem persists, contact IBM technical
support for additional assistance.

------------------------------------------------------------------------
ANS4999I

The following message was too long to log to the server: 'shortened
message with message number'



Explanation:

The message text and inserts are too large to send to the server in the
available internal buffer.

System action:

The message number message is written to the local client error log,
then shortened and sent to the server as a part of this message. The
message is reduced in length by substituting '...' in the middle of the
original message.

User response:

The message referred to has been shortened, but describes the error that
occurred. See the documentation for that message for more information.

------------------------------------------------------------------------
ANS5003S

The management class assigned to directories does not exist.



Explanation:

The management class named on the DIRMC option does not exist in your
assigned policy set on the server. The error log contains an entry
showing the invalid management class name.

System action:

processing stops.

User response:

Remove the current DIRMC option from the client options file, then run
DSMC QUERY MGMTCLASS -DETAIL to view information about available
management classes. Make sure the management class you select has a
backup copy group. If you have more than one IBM Spectrum Protect
server, make sure you are connecting to the correct server. If you are
unable to find a suitable management class, contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS5004S

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



Explanation:

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

System action:

processing stops.

User response:

Remove the current DIRMC option from the client options file, then run
DSMC QUERY MGMTCLASS -DETAIL to view information about available
management classes. Make sure the management class you select has a
backup copy group. If you have more than one IBM Spectrum Protect
server, make sure you are connecting to the correct server. If you are
unable to find a suitable management class, contact your IBM Spectrum
Protect administrator for further assistance.

------------------------------------------------------------------------
ANS5006W

The policy set does not contain any backup copy groups. The process is
unable to continue the backup.



Explanation:

You tried to back up the files using a policy set that contained no
backup management information.

System action:

The process did not back up the files.

User response:

See your IBM Spectrum Protect administrator for assistance in
associating your node with a policy set containing a management class
that has a backup copy group. Then try the operation again.

------------------------------------------------------------------------
ANS5007W

The policy set does not contain any archive copy groups. IBM Spectrum
Protect is unable to continue the archive.



Explanation:

You tried to archive the files using a policy set that contains no
archive management information.

System action:

IBM Spectrum Protect did not archive the files.

User response:

See your IBM Spectrum Protect administrator for assistance in
associating your node with a policy set containing a management class
that has an archive copy group. Then try the operation again.

------------------------------------------------------------------------
ANS5008W

Incorrect password entered



Explanation:

You entered a password that was incorrect.

System action:

IBM Spectrum Protect cannot connect to the server without the correct
password.

User response:

Reenter the password, or ask your system administrator for the current
password.

------------------------------------------------------------------------
ANS5009W

New password entries are not the same



Explanation:

During the change password, update password, or open registration
dialog, the two entries for the new password were not the same.

System action:

The password was not changed on the server.

User response:

Backspace over both of the new passwords and reenter them, ensuring that
they match.

------------------------------------------------------------------------
ANS5011I

Backup stopped by user



Explanation:

You requested to stop the backup operation.

System action:

Backup stopped.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5012E

Server out of backup data storage space



Explanation:

The server ran out of space in its backup data storage.

System action:

IBM Spectrum Protect cannot complete the requested backup operation. Any
files displayed on the lower half of the backup activity panel were
successfully backed up.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS5013E

Not enough memory for backup operation



Explanation:

IBM Spectrum Protect cannot allocate memory for the specified backup
operation.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

Close all unneeded applications and retry the operation. Reducing the
scope of queries and the amount of data returned might also help, or see
your system administrator.

------------------------------------------------------------------------
ANS5014I

Backup completed



Explanation:

The backup was completed.

System action:

IBM Spectrum Protect backed up the files.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5015I

Restore stopped by user



Explanation:

You requested to stop the restore operation.

Attention: If you were restoring files with "overwrite" option
specified, the file you restored last can be damaged (partially
overwritten).

System action:

Restore stopped.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5016E

Not enough memory for the requested restore operation.



Explanation:

Not enough memory is available for the requested restore operation.

System action:

Processing stops.

User response:

Close all unneeded applications and retry the operation. Reducing the
scope of queries and the amount of data returned can also help, or see
your system administrator.

------------------------------------------------------------------------
ANS5017I

Restore completed



Explanation:

A restore was completed.

System action:

IBM Spectrum Protect restored the files.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5018E

Not enough memory for archive operation



Explanation:

The client cannot allocate memory for the requested archive operation.

System action:

Processing stops.

User response:

Close all unneeded applications and retry the operation. Reducing the
scope of queries and the amount of data returned might also help, or see
your system administrator.

------------------------------------------------------------------------
ANS5019I

Archive stopped by user



Explanation:

You requested to stop the archive operation.

System action:

Archive stopped.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5020E

The IBM Spectrum Protect server is out of archive data storage space.



Explanation:

The server ran out of space in its archive data storage.

System action:

Client cannot complete the requested archive operation.

User response:

Report the problem to your IBM Spectrum Protect system administrator,
who can allocate more resources to archive storage.

------------------------------------------------------------------------
ANS5021I

Archive completed



Explanation:

An archive was completed.

System action:

IBM Spectrum Protect archived the files.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5022I

Retrieve stopped by user



Explanation:

You requested to stop the retrieve operation.

Attention: If you were retrieving files with "overwrite" option
specified, the file you retrieved last can be damaged (partially
overwritten).

System action:

Retrieve stopped.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5023E

Not enough memory for retrieve operation



Explanation:

The process in which the program runs has exceeded the maximum allocated
memory.

System action:

Processing ends.

User response:

Close all unneeded applications and retry the operation. Reducing the
scope of queries and the amount of data returned might also help, or see
your system administrator.

------------------------------------------------------------------------
ANS5024I

Retrieve completed



Explanation:

A retrieve was completed.

System action:

IBM Spectrum Protect retrieved the files.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5025E

The node name contains invalid characters.



Explanation:

The specified node name has invalid characters.

System action:

Current operation has been cancelled.

User response:

Retry with another node name that has valid characters.

------------------------------------------------------------------------
ANS5026W

MatchAllChar and MatchOneChar options MUST precede Include/Exclude
options



Explanation:

The MatchAllChar and MatchOneChar options must precede any
include-exclude options.

System action:

Current application ends

User response:

Move the MatchAllChar and MarchOneChar options before any
include-exclude options.

------------------------------------------------------------------------
ANS5027W

Objects of different types cannot be backed up at the same time.



Explanation:

Backing up objects of different types at the same time is not allowed in
certain scenarios. For example, backing up Hyper-V and VMware virtual
machines at the same time is not possible.

System action:

No processing takes place.

User response:

Select objects of the same type to perform backup operation.

------------------------------------------------------------------------
ANS5028I

Successful completion



Explanation:

The operation successfully completed.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS5029E

This operation cannot continue due to an error on the IBM Spectrum
Protect server. See your IBM Spectrum Protect server administrator for
assistance.



Explanation:

The IBM Spectrum Protect server encountered an error condition that
prevents the IBM Spectrum Protect client operation from continuing. Your
IBM Spectrum Protect server administrator can review the IBM Spectrum
Protect server activity log for more details about the error.

System action:

The processing stopped.

User response:

Contact your IBM Spectrum Protect server administrator for assistance.
The administrator can review the IBM Spectrum Protect server activity
log for further information about the conditions that lead to this
error.

------------------------------------------------------------------------
ANS5030E

No objects on server match query



Explanation:

No objects on the server match the query operation being performed.

System action:

The processing stopped.

User response:

Ensure the names are properly entered.

------------------------------------------------------------------------
ANS5031E

Client aborted transaction



Explanation:

The client system ended the operation with the server and ended the
current transaction.

System action:

The processing stopped.

User response:

Restart the session.

------------------------------------------------------------------------
ANS5032W

Active object not found



Explanation:

An attempt was made to expire an object, but the server was unable to
find an active backup version of the object. This message is preceded by
message ANS1228E which specifies the object name. For instance, this
message could be issued if two separate client processes are backing up
the same file system at the same time. If one of the processes expires a
file, then the server will make that file inactive. If the second
process subsequently attempts to expire that same file, the server will
not find an active version of the file, so the second process will issue
this message for that file.

System action:

The object is not expired. Processing continues with the next object..

User response:

Review the console output, schedule log, or error log and locate the
ANS1228E message that immediately precedes this message. ANS1228E will
identify the object that could not be expired. Examine the conditions
under which the problem occurred and assess whether those conditions
explain the occurrence of this message. For example, this message could
appear if multiple instances of the client were attempting to back up
the file system concurrently. If the reason this message occurred can
not be determined and the message occurs when the operation is tried
again, then contact support for further assistance. Also try searching
for this message number on http://www.ibm.com for possible solutions.

------------------------------------------------------------------------
ANS5033E

Server has no data for the object.



Explanation:

Server tried to do a restore or retrieve on an object that has no data
associated with it. If a corrective 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 that might help identify the problem.

------------------------------------------------------------------------
ANS5034E

You entered an incorrect password.



Explanation:

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

System action:

The processing stops.

User response:

Retry the session with the correct password. If this fails or you have
forgotten your password, ask the administrator to assign a new password.

------------------------------------------------------------------------
ANS5035E

Node is in use.



Explanation:

The node you are running on is in use by another operation on the
server. This might be from another client or from some activity on the
server.

System action:

The processing stopped.

User response:

Retry the operation, or see your system administrator to see what other
operations are running for your node.

------------------------------------------------------------------------
ANS5036E

Expiration date must be greater than today's date



Explanation:

Archive expiration date is too low, the date must be greater than
today's date.

System action:

The current operation is canceled.

User response:

Retry archiving the file with an expiration date that is higher than
today's date.

------------------------------------------------------------------------
ANS5037W

The requested data is offline



Explanation:

For the restore or retrieve operation, one or more of the requested
files must be recalled from offline storage media (generally tape). The
wait time depends on your site's offline storage management policies.

System action:

CLient waits for offline storage media to become available and then
continues.

User response:

None.

------------------------------------------------------------------------
ANS5038E

Object too large for server limits.



Explanation:

The object is too large. The configuration of the server does not have
any data storage space that accepts the object.

System action:

File skipped.

User response:

See your system administrator to determine the maximum file (object)
size for which your site's server is configured.

------------------------------------------------------------------------
ANS5039E

Server out of data storage space.



Explanation:

The server does not have any space available to store the object.

System action:

Ended the current operation.

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.

------------------------------------------------------------------------
ANS5040E

Server media mount not possible.



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.

------------------------------------------------------------------------
ANS5041E

Size estimate exceeded.



Explanation:

The total amount of data for a backup or archive operation exceeds the
estimated size originally sent to the server for allocating data storage
space. This happens when many files are growing by large amounts while
the backup or archive operation is in session.

System action:

Processing stopped.

User response:

Retry the operation. If the problem continues, check what other
processes are running on the client machine that are generating large
amounts of data. Disable those operations while the backup or archive
operation is taking place.

------------------------------------------------------------------------
ANS5042E

File data is currently unavailable on the IBM Spectrum Protect server



Explanation:

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

*  Data is corrupted at the IBM Spectrum Protect server

*  The IBM Spectrum Protect server encountered a read error

*  File is temporarily involved in a reclaim operation at the server

*  The IBM Spectrum 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.

System action:

Processing stopped.

User response:

Try the operation again at a later time. If the problem continues,
contact your IBM Spectrum Protect server administrator for further
assistance. The administrator can review the IBM Spectrum Protect server
activity log for messages related to the problem.

------------------------------------------------------------------------
ANS5043W

Unexpected retry request. The server found an error while writing the
data.



Explanation:

None.

System action:

The client retries the operation.

User response:

None.

------------------------------------------------------------------------
ANS5044E

Session rejected: All server sessions are currently in use.



Explanation:

Server has all available sessions in use and cannot accept a new one at
this time.

System action:

Server canceled the current operation.

User response:

Retry the operation.If the problem continues, see your system
administrator to increase the number of concurrently active sessions to
the server.

------------------------------------------------------------------------
ANS5045E

The session is rejected. Your password has expired.



Explanation:

Your password has expired.

System action:

Server canceled the current operation. You are not allowed to connect to
the server until the password is updated.

User response:

Update your password. You may use the SET PASSWORD command, or have the
administrator update your node.

------------------------------------------------------------------------
ANS5046E

Session rejected: Unknown or incorrect node ID entered



Explanation:

The node name you entered is not known by the server, or you are
attempting to access a file migrated to a different node.

System action:

The current operation is canceled. You are not allowed to connect to the
server until your node name is registered with the server. If attempting
to access a migrated file, your node name must be the same node which
migrated the file.

User response:

Ensure that you entered your node name correctly. If yes, see your
system administrator. Verify that the server is using closed
registration and that your node name is registered with the server.

------------------------------------------------------------------------
ANS5047E

Session rejected: Duplicate ID entered. Node already logged onto server



Explanation:

Another process using this node name is active with the server.

System action:

Cannot connect to the server. Canceled the current operation.

User response:

Ensure that your node name is unique to the server so that it cannot be
used by another person. See your system administrator to identify the
owner of that node name.

------------------------------------------------------------------------
ANS5048E

Please choose a filespace.The filespace to delete/set access cannot be
found.



Explanation:

The filespace to delete cannot be found.

System action:

The system returns to the calling procedure.

User response:

Verify the filespace name.

------------------------------------------------------------------------
ANS5049E

Session rejected: The server is disabled



Explanation:

The server is in a disabled state and cannot be accessed for normal
activity.

System action:

Canceled the current operation.

User response:

Retry the operation after the server returns to an enabled state. If the
problem continues, see your system administrator.

------------------------------------------------------------------------
ANS5050E

The server is not configured to allow open registration.



Explanation:

No authorization. Registration is required by your system administrator.
The server is not configured to allow open registration.

System action:

Session not started.

User response:

You must obtain a node and password from your system administrator.

------------------------------------------------------------------------
ANS5051S

Session rejected: the client code is down-level



Explanation:

The server version and your client version do not match. The client code
is downlevel.

System action:

The current operation is canceled.

User response:

See your system administrator to see what version to run for your
location.

------------------------------------------------------------------------
ANS5052E

Session rejected: Downlevel server code version.



Explanation:

The server version and your client version do not match. The server code
is downlevel.

System action:

The current operation is canceled.

User response:

See your system administrator to see what version to run for your
location.

------------------------------------------------------------------------
ANS5053W

The operation was stopped by the user.



Explanation:

The operation was stopped at the request of the user. This usually
occurs when the 'Q' key is pressed two times.

System action:

Processing stopped.

User response:

None.

------------------------------------------------------------------------
ANS5054E

The operating system refused a request for memory allocation.



Explanation:

The client 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.

System action:

Client cannot complete the requested operation.

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 task serially for each directory. If the task is an
incremental backup, use the option "-memoryefficientbackup=yes".

------------------------------------------------------------------------
ANS5055E

File not found during Backup, Archive or Migrate processing. No file
specification 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 be
backed up, archived or migrated.

System action:

File skipped.

User response:

None.

------------------------------------------------------------------------
ANS5056E

The specified directory path could not be found.



Explanation:

An invalid or unreachable directory path was specified.

System action:

Processing stopped.

User response:

Try the operation again using a valid directory path.

------------------------------------------------------------------------
ANS5057E

Access to the specified file or directory is denied.



Explanation:

Access to the specified file or directory is denied. You tried to read
from or write to a file and you do not have access permission for either
the file or the directory.

System action:

Processing stopped.

User response:

Ensure that you specified the correct file or directory name, correct
the permissions, or specify a new location.

------------------------------------------------------------------------
ANS5058E

No file handles available



Explanation:

All file handles for your system are currently in use. No more are
available.

System action:

Processing stopped.

User response:

Either free some file handles by ending other processes, or modify your
system setup to allow for more files to be open at the same time.

------------------------------------------------------------------------
ANS5059E

The file exists and cannot be overwritten.



Explanation:

The file being restored or retrieved exists and cannot be overwritten
due to lack of authority or access permissions.

System action:

The file is skipped.

User response:

Verify that you have sufficient access permissions to overwrite the
file, then try the operation again. If the problem persists, contact
your system administrator or administrator for further assistance.

------------------------------------------------------------------------
ANS5060E

Invalid parameter passed.



Explanation:

The system encountered an internal program error due to an invalid
parameter.

System action:

The system returns to the calling procedure.

User response:

Ask your service representative to check the error log.

------------------------------------------------------------------------
ANS5061E

An invalid file handle passed. Report how you got this system error.



Explanation:

An internal system error occurred. A file operation failed because of an
invalid file handle.

System action:

Processing stops.

User response:

Try the operation again. If the failure persists, obtain a service trace
that captures the problem and contact technical support for additional
assistance. Your administrator can help you configure the trace.

------------------------------------------------------------------------
ANS5062E

Disk full



Explanation:

Operation has stopped because the destination disk is full.

System action:

Processing stopped.

User response:

Free up disk space and retry the operation

------------------------------------------------------------------------
ANS5083E

Drive specification contains wildcard character.



Explanation:

Drive name shouldn't contain wildcard character.

System action:

Wildcarded objects skipped.

User response:

Use valid drive specification.

------------------------------------------------------------------------
ANS5091S

The IBM Spectrum Protect server does not currently have space in the
storage pool for this file. This might be a temporary condition.



Explanation:

This message is typically issued when the storage pool in which the data
is being placed does not have sufficient to store the data, but that the
space will be available soon. For example, a storage pool migration may
free up sufficient space to store the data.

System action:

Process ends.

User response:

This is possibly a temporary condition. Try the operation again at a
later time. If the error persists, contact your IBM Spectrum Protect
administrator, who can examine server console and error logs to locate
the cause of the problem.

------------------------------------------------------------------------
ANS5092S

Server out of data storage space.



Explanation:

The server does not have any more space available to store the object.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Report to your system administrator that a storage pool on the server is
full.

------------------------------------------------------------------------
ANS5093S

SLM_LICENSE_EXCEEDED: The client licenses for IBM Spectrum Protect are
exceeded. See your IBM Spectrum Protect administrator.



Explanation:

Adding a new enrollment will exceed the product license count for this
IBM Spectrum Protect server.

System action:

The client enrollment or connection request ends.

User response:

See your IBM Spectrum Protect administrator to delete unused enrollments
or negotiate an increase in the number of allowed licenses for your
server.

------------------------------------------------------------------------
ANS5094E

Session Rejected. Sufficient server memory is not available.



Explanation:

The server does not have enough memory to allow your client to establish
a connection with the server.

System action:

Session was not started.

User response:

Retry later or see your system administrator.

------------------------------------------------------------------------
ANS5122E

The specified filespace does not exist on the server. The filespace
might have been deleted by another client or an administrator.



Explanation:

The specified filespace does not exist on the server. Your administrator
might have already deleted the filespace or another client using your
client's node name might have deleted it.

System action:

IBM Spectrum Protect ends the current operation.

User response:

The filespace you selected does not exist any more. See your IBM
Spectrum Protect administrator for help in finding how the filespace was
deleted.

------------------------------------------------------------------------
ANS5123S

Open registration failed because the specified node name is already
defined in the server.



Explanation:

Open registration failed because a node is defined on the server with
the same name.

System action:

Current operation has been cancelled.

User response:

Retry with another node name.

------------------------------------------------------------------------
ANS5124S

Open registration failed because there is no default domain.



Explanation:

Open registration failed because a default policy domain does not exist
in which to place your node. A default policy domain is required to
fully support open node registration.

System action:

Current operation has been cancelled.

User response:

See your IBM Spectrum Protect administrator for assistance in
registering your node.

------------------------------------------------------------------------
ANS5125S

Open registration failed because an invalid node name was specified.



Explanation:

Open registration failed because the specified node name has invalid
characters.

System action:

Current operation has been cancelled.

User response:

Retry with another node name that does not have any invalid characters.

------------------------------------------------------------------------
ANS5126S

Filespaces with duplicate names are not supported. Unmount the duplicate
file space.



Explanation:

The selected file space has a duplicate volume label. Because IBM
Spectrum Protect uses the volume label to keep track of backup/archive
information, it cannot back up or archive files from a file space with a
duplicate volume label.

System action:

IBM Spectrum Protect cannot select the volume.

User response:

If the file space needs to be available to the system, exit IBM Spectrum
Protect, and assign a volume label to the file space. Restart the
process and retry the operation. Otherwise, unmount the duplicate file
space.

------------------------------------------------------------------------
ANS5127I

IBM Spectrum Protect has detected an incomplete setup! The system
options file 'dsm.sys' was not found, while the client options file
'file-path' exists! The wizard will guide you through the configuration
process of the initial basic IBM Spectrum Protect client options files
replacing your current option file. Would you like to continue?



Explanation:

IBM Spectrum Protect has detected an incomplete setup. The system
options file, dsm.sys, was not found. Additionally, a user options file,
dsm.opt, was found. To complete the configuration the configuration
wizard will create dsm.sys and replace dsm.opt with minimal settings.

System action:

IBM Spectrum Protect may stop

User response:

If the current version of dsm.opt is needed, rename the file and restart
IBM Spectrum Protect. If the current version is not needed, select yes
and allow IBM Spectrum Protect to replace the file.

------------------------------------------------------------------------
ANS5128E

The management class for this file did not have a backup copy group.



Explanation:

For backup operations, a file may only be bound to a management class
that has a backup copy group.

System action:

IBM Spectrum Protect did not back up the file.

User response:

See your IBM Spectrum Protect system administrator for assistance in
finding a management class with the required copy group. The
administrator may also define such a management class for you.

------------------------------------------------------------------------
ANS5129E

The management class for this file did not have an archive copy group
specified.



Explanation:

For archive operations, a file may only be bound to a management class
that has an archive copy group.

System action:

The file was not archived.

User response:

See your IBM Spectrum Protect system administrator for assistance in
finding a management class with the required copy group. The
administrator may also define such a management class for you.

------------------------------------------------------------------------
ANS5130W

No filespaces selected for deletion



Explanation:

You requested a deletion operation without selecting a client domain.

System action:

IBM Spectrum Protect cannot perform a deletion without a domain
selected.

User response:

Select the volumes you want to delete and retry the operation.

------------------------------------------------------------------------
ANS5132I

Filespace deletion canceled by user



Explanation:

You requested to cancel the filespace deletion operation.

System action:

The filespace deletion operation stopped.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5133I

Filespace 'filespace' was deleted



Explanation:

The specified filespace was successfully deleted.

System action:

IBM Spectrum Protect deleted the filespace.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5134E

Unable to delete the filespace because this node does not have
permission to delete archived or backed up data.



Explanation:

You tried to delete a filespace that you do not have permission to
access.

System action:

Processing stopped.

User response:

Ensure that you specify the correct filespace, or specify a filespace
you have access to.

------------------------------------------------------------------------
ANS5135I

Archive delete stopped by user



Explanation:

You requested to stop the archive delete operation.

System action:

Archive delete stopped.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5138I

Archive delete completed



Explanation:

An archive delete was completed.

System action:

IBM Spectrum Protect deleted the archived files.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5139E

Your node does not have permission to delete archived files.



Explanation:

Your node is registered at the server with the ARCHDELETE option set to
'NO'. Therefore your node is not allowed by the server to delete
archived files.

System action:

Archived files were not deleted.

User response:

See your IBM Spectrum Protect system administrator. The administrator
has authority to delete archived files, and can also grant that
authority to your node.

------------------------------------------------------------------------
ANS5145W

Server cannot restart the last restore request. Do you want to restore
without restart?



Explanation:

The restart restore token has expired. The server cannot restart the
restore from where it last ended.

System action:

Processing stopped; waiting for user intervention.

User response:

Retry the request without restart or abort the request.

------------------------------------------------------------------------
ANS5146W

You cannot perform this operation while accessing data for another node.
Do you wish to switch back to accessing your own node?



Explanation:

The user cannot perform the selected operation while accessing another
users data.

System action:

Processing stopped; waiting for user intervention.

User response:

Answer "Yes" to switch back to accessing the server as the original
node.

------------------------------------------------------------------------
ANS5148W

The server needs to do a one-time conversion of your archive data before
you can continue. This operation may take a long time, and cannot be
canceled once it has started. Are you willing to wait for the conversion
to complete?



Explanation:

The server must do a conversion of the archive data before continuing.
The conversion could take a long time, and cannot be canceled once it is
started.

System action:

Processing stopped; waiting for user intervention.

User response:

Answer "Yes" to start the archive data conversion. If you answer "No",
the current operation will be canceled.

------------------------------------------------------------------------
ANS5150E

An active restore for the same source file specification exists. Unable
to continue with this request.



Explanation:

Currently, there is an active restore for the same source file
specification. Another restore of the same source file specification
cannot be started.

System action:

The requested restore fails.

User response:

Start another restore with a different source file specification.

------------------------------------------------------------------------
ANS5151S

This node currently has a pending restartable restore session. The
requested operation cannot complete until this session either completes
or is canceled.



Explanation:

This operation can not be completed because a restartable restore
session is pending. The operation is not allowed because the restartable
session and the current operation affect the same file space.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Issue the Query Restore command to view a list of your restartable
restore sessions in the server database. Issue the Cancel Restore
command to cancel any unneeded restartable restore sessions.

------------------------------------------------------------------------
ANS5152S

Session Rejected: The server is not licensed for this platform type. See
your IBM Spectrum Protect administrator.



Explanation:

The server license governs the types of client that can connect to it.
The license for this server does not include the requesting client type.

System action:

The client enrollment or connection request ends.

User response:

See your IBM Spectrum Protect administrator who must upgrade the server
license to accept your client type.

------------------------------------------------------------------------
ANS5153E

Session Rejected: The server does not allow a signon as a Unicode
enabled client.



Explanation:

The client cannot establish a connection to the server because of a
unicode enabling mismatch between server and client.

System action:

Session was not started.

User response:

See your system administrator immediately.

------------------------------------------------------------------------
ANS5154I

File is implicitly excluded



Explanation:

You tried to back up or migrate a file that is implicitly excluded.

System action:

IBM Spectrum Protect will not back up or migrate an implicitly excluded
file.

User response:

None.

------------------------------------------------------------------------
ANS5155E

The valid password is not available. The IBM Spectrum Protect
administrator for your system must run IBM Spectrum Protect and enter
the password to store it locally.



Explanation:

The file containing the stored password for the specified server is
unavailable.

System action:

Process ends.

User response:

The system administrator for your system must set and store a new
password.

------------------------------------------------------------------------
ANS5158S

Filespace deletion is in progress. Try again later.



Explanation:

The filespace is in the process of being deleted.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

Try the operation again later. If the filespace was being deleted, it
could take awhile for it to complete. If the problem continues, report
the problem to your system administrator.

------------------------------------------------------------------------
ANS5164E

Backup or archive of drives with duplicate volume labels is not allowed.



Explanation:

You tried to back up or archive a drive that has a duplicate volume
label. Because IBM Spectrum Protect uses the volume label to keep track
of backup or archive information, it cannot back up or archive files
from a drive with a duplicate volume label.

System action:

IBM Spectrum Protect cannot select the drive for backup or archive
operations.

User response:

If the volume needs to be available to the system, exit IBM Spectrum
Protect and assign a unique volume label to the drive. Restart IBM
Spectrum Protect and try the operation again.

------------------------------------------------------------------------
ANS5165E

Drive has no volume label. Backup/Archive not allowed.



Explanation:

You tried to backup or archive a drive that has no volume label.

System action:

IBM Spectrum Protect rejected the selected drive.

User response:

If the drive is a floppy drive, place a disk with a volume label in it
and retry the operation. If the disk is a hard drive, ensure the drive
has a volume label, and retry the operation.

------------------------------------------------------------------------
ANS5176W

The requested virtual machine operation cannot be performed because a
virtual machine backup or restore operation is already in progress.
Please retry the operation after the first operation completes.



Explanation:

A virtual machine operation is already in progress, so the requested
virtual machine operation cannot be performed until the first operation
complets.

System action:

Processing stops

User response:

Wait for the first virtual machine operation to complete, and then
restart the current request.

------------------------------------------------------------------------
ANS5177E

Client-side deduplication and server-initiated sessions are mutually
exclusive.



Explanation:

Conflicting options SESSIONINIT=serveronly and DEDUPLICATION=yes were
specified. This combination is not allowed.

System action:

Processing stops.

User response:

Use client-initiated sessions or disable client-side deduplication

------------------------------------------------------------------------
ANS5178E

Restart of the RSM service failed. Restart the RSM service manually.



Explanation:

RSM database files have been restored from the IBM Spectrum Protect
server and imported. The client has tried to restart the RSM service on
the user's behalf but has run into a problem.

System action:

Processing stopped.

User response:

Restart the RSM service manually.

------------------------------------------------------------------------
ANS5179E

Client is unable to continue. Exiting program.



Explanation:

Client ran into a problem and is unable to continue. This error message
is usually preceded by other error messages. Resolve those errors and
try again.

System action:

Program terminates.

User response:

Fix the problem(s) that preceded this message and then restart the
client.

------------------------------------------------------------------------
ANS5181E

Invalid selection; A specific backup set must be selected.



Explanation:

A selection was made that might result in multiple backup sets being
restored at the same time, but restoring multiple backup sets at the
same time is not supported.

System action:

The backup set restore was not performed.

User response:

Select a specific backup set to be restored.

------------------------------------------------------------------------
ANS5182E

Multiple backup sets can not be restored at the same time.



Explanation:

Multiple backup sets were selected to be restored, but restoring
multiple backup sets at the same time is not supported.

System action:

The backup set restore was not performed.

User response:

Select a specific backup set to be restored.

------------------------------------------------------------------------
ANS5183W

Objects of different types cannot be restored at the same time.



Explanation:

Restoring objects of different types is not allowed. For example,
restoring Backup Sets and regular file objects at the same time is not
possible.

System action:

No processing takes place.

User response:

Select objects of the same type to perform restore operation.

------------------------------------------------------------------------
ANS5184E

Illegal Operation On Following Object: object



Explanation:

Requested operation cannot be performed on this object.

System action:

This object will be skipped.

User response:

Try another operation on this object, or try the same operation on
another object.

------------------------------------------------------------------------
ANS5186E

Server is downlevel, System Services and System State backup disabled
for this session.



Explanation:

The operation cannot be performed because server version is downlevel.

System action:

System Service and System State backup is disabled for this session.

User response:

Must use level 5.2.0 or higher server.

------------------------------------------------------------------------
ANS5187E

Unable to set SHAREAS extended attribute for file: 'pathname' Return
code: 'returncode' 'strerror' Reason code: 'reasoncode'



Explanation:

You must be the file owner or have superuser authority.

System action:

File processed without setting attribute.

User response:

The attribute must be set manually.

------------------------------------------------------------------------
ANS5188E

Periodic Full plus Incremental VM backups have been deprecated. Please
use Incremental Forever Full or Incremental Forever Incremental to
perform virtual machine backups.



Explanation:

Periodic Full plus Incremental virtual machine backups have been
deprecated.

System action:

Processing stops

User response:

Restart the virtual machine backup and use Incremental Forever Full or
Incremental Forever Incremental instead for the backup mode.

------------------------------------------------------------------------
ANS5189E

Online SystemState restore has been deprecated. Please use offline WinPE
method for performing system state restore.



Explanation:

Online SystemState restore has been deprecated.

System action:

Processing stops

User response:

Perform the system state restore using offline WinPE method.

------------------------------------------------------------------------
ANS5191E

NT Active Directory is not online. Offline backup is not supported.



Explanation:

NT Active Directory is not online when performing a backup operation.
Offline backup is not supported.

System action:

Processing stopped.

User response:

Reboot computer and turn on Active Directory, and try the operation
again.

------------------------------------------------------------------------
ANS5192E

NT Active Directory is online. Online restore is not supported.



Explanation:

NT Active Directory is online when performing a restore operation.
Online restore is not supported.

System action:

Processing stopped.

User response:

Reboot computer and enter Active Directory repair mode, then try the
operation again.

------------------------------------------------------------------------
ANS5193E

Certificate Services is not online. Offline backup is not supported.



Explanation:

Certificate Services is not online when performing a backup operation.
Offline backup is not supported.

System action:

Processing stopped.

User response:

Start Certificate Services and try the operation again.

------------------------------------------------------------------------
ANS5194E

Certificate Services is online. Online restore is not supported.



Explanation:

Certificate Services is online when performing a restore operation.
Online restore is not supported.

System action:

Processing stopped.

User response:

Stop Certificate Services and try the operation again.

------------------------------------------------------------------------
ANS5196W

Invalid encryption key password entered.



Explanation:

The encryption key password supplied does not meet the IBM Spectrum
Protect requirements. This key can be up to 63 bytes in length and
include the 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:

IBM Spectrum Protect allows you to try again.

User response:

Enter the correct encryption key password.

------------------------------------------------------------------------
ANS5201E

The specified function is not implemented



Explanation:

The specified function is not implemented.

System action:

Processing stopped.

User response:

Correct the command and retry the operation.

------------------------------------------------------------------------
ANS5202I

One or more system objects were excluded from processing by entries in
the include-exclude list.



Explanation:

One or more system objects were excluded from processing by entries in
the include-exclude list and the client did not process them.

System action:

Excluded objects skipped.

User response:

None.

------------------------------------------------------------------------
ANS5204W

Only one backup set may be selected for restore.



Explanation:

Restoring multiple backup sets is not allowed. Only one backup set may
be selected and restored.

System action:

No processing takes place.

User response:

Only one backup set may be selected for restore.

------------------------------------------------------------------------
ANS5208E

An invalid date or time was entered.



Explanation:

An invalid date or time value was entered. Either the syntax of the
value was not correct, or an actual value (for example, "45" for month)
was invalid.

System action:

Processing stops.

User response:

Identify and correct the invalid date or time value. Refer to the user's
guide of the corresponding platform for the correct date syntax.

------------------------------------------------------------------------
ANS5209E

System Volume backup failed.



Explanation:

IBM Spectrum Protect encountered an error while backing up files of the
Windows 2000 System Volume

System action:

Processing stopped.

User response:

Examine the Windows 2000 File Replication Service Event log to insure
the system volume was successfully initialized. Restart the service and
retry the backup operation

------------------------------------------------------------------------
ANS5210E

System Volume restore failed.



Explanation:

IBM Spectrum Protect encountered an error while restoring files of the
Windows 2000 System Volume

System action:

Processing stopped.

User response:

Examine the Windows 2000 File Replication Service Event log to insure
the system volume was successfully initialized. Restart the service and
retry the restore operation.

------------------------------------------------------------------------
ANS5211E

The cluster service is offline. The cluster service must be online to
perform an authoritative cluster database restore operation.



Explanation:

The cluster service must be online to restore the cluster database. IBM
Spectrum Protect tried to start the service and failed. It is possible
that an authoritative restore cannot be done.

System action:

Processing stops.

User response:

Start the cluster service and retry the operation.

------------------------------------------------------------------------
ANS5212E

An error occurred while trying to rename file space.



Explanation:

This operation can not be completed because the file space could not be
renamed.

System action:

IBM Spectrum Protect ended the current operation.

User response:

Contact system administrator for more information.

------------------------------------------------------------------------
ANS5215E

function-type is not allowed on object 'object'. Object is not sent to
the server.



Explanation:

The operation could not be performed on this object. For example, if
this is an image operation, the selected path is a file or a directory
and therefore is not a valid object for image operations.

System action:

This object is skipped.

User response:

Verify that the object named is of a type supported by the command. For
example, if a filespace name is required but a directory name was given,
change the name so it includes only the filespace name.

------------------------------------------------------------------------
ANS5216E

Could not establish a TCP/IP connection with address
'tcp-addr:tcp-port'. The TCP/IP error is 'tcp-err-string' (errno =
errno).



Explanation:

A TCP/IP connection was attempted with a server or agent program and
failed.

System action:

Processing stops.

User response:

Ensure that the target TCP/IP address and port number is correct. Check
to ensure that a IBM Spectrum Protect server or agent has been started
at the target TCP/IP address and is configured to listen at the port
listed in the message.

------------------------------------------------------------------------
ANS5217E

Your node does not have permission to delete backed up files.



Explanation:

You cannot delete backed up files unless your IBM Spectrum Protect
administrator has authorized your node to do so.

System action:

IBM Spectrum Protect does not delete the backed up files.

User response:

Use the DSMC QUERY SESSION command to verify your authorization. Ask
your IBM Spectrum Protect administrator to provide the necessary
authorization.

------------------------------------------------------------------------
ANS5219W

Objects of different groups cannot be restored at the same time.



Explanation:

Restoring objects of different groups is not allowed.

System action:

No processing takes place.

User response:

Select objects of the same group to perform restore operation.

------------------------------------------------------------------------
ANS5222E

The archive description exceeds 254 characters.



Explanation:

IBM Spectrum Protect places a maximum length of 254 characters on the
archive description.

System action:

processing stops.

User response:

Issue the command again and specify a shorter valid archive description.

------------------------------------------------------------------------
ANS5224W

Error error code encountered while reverting to the restored snapshot.



Explanation:

After the virtual machine disks are restored, the virtual machine is
reverted to the restored state. The specified error was encountered
while performing this revert operation.

System action:

Processing continues

User response:

Try powering on the restored virtual machine. If it fails to start,
re-try the restore process.

------------------------------------------------------------------------
ANS5225W

Error error code encountered while removing the restored snapshot.



Explanation:

After the virtual machine disks are restored, the virtual machine is
reverted to the restored state, and the snapshot is removed. The
specified error was encountered while removing the snapshot.

System action:

Processing continues

User response:

Try powering on the restored virtual machine. If it fails to start,
re-try the restore process.

------------------------------------------------------------------------
ANS5226E

The virtual machine backup operation failed.



Explanation:

The virtual machine backup operation failed. Check the error log for
details on why the operation failed.

System action:

Processing stops

User response:

Review the console output and error logs for the details on the problem.
Fix any issues and restart the operation.

------------------------------------------------------------------------
ANS5227E

IBM Spectrum Protect detected an error where both a snapshot name was
specified, and a request to create a snapshot were specified.



Explanation:

Either a snapshot name should be specified, or a request for IBM
Spectrum Protect to create the snapshot should be specified, but not
both.

System action:

Processing stops.

User response:

This is an internal error and should be reported to your service
representative.

------------------------------------------------------------------------
ANS5228E

A backup VM operation failed because VMMAXPARALLEL was reduced to 1 and
the client still cannot obtain a server mount point.



Explanation:

During a parallel backup operation, concurrent backup sessions required
additional server mount points to perform the backups in parallel. The
client attempted to obtain the additional mount points, but the client
requests exceeded the number of mount points (MAXNUMMP) defined for the
node. In an effort to make the backup occur, the client reduced the
VMMAXPARALLEL option to 1, but was still unable to obtain a mount point.
The backup operation was stopped.

System action:

The backup operation was stopped

User response:

Check the console or schedule log for additional information. Retry the
operation at a later time. Ensure VMMAXPARALLEL is set to a value less
than or equal to MAXNUMMP.

------------------------------------------------------------------------
ANS5229E

The Snapshot is already mounted for backup 'backup-name'.



Explanation:

The Snapshot is currently mounted on the local machine or a remote
machine. No mount operation on the snapshot will be allowed until it has
been unmounted.

System action:

Processing stops

User response:

See the dsmerror.log file for further details.

------------------------------------------------------------------------
ANS5230E

The Snapshot is already imported to the local system for backup
'backup-name'.



Explanation:

The Snapshot is currently imported on the local machine. This maybe
becasue the Snapshot is in use or it was not created with the Import VSS
snapshots only when needed feature enabled.

System action:

Processing stops

User response:

Remote Mount operation not allowed on snapshots that are currenlty
imported.

------------------------------------------------------------------------
ANS5231E

VMDK size reported by VMware vSphere API is different than actual size
of vmdk file. Reissue the restore command with the testflag
-VMRESTORE_INCVMDKSIZE.



Explanation:

VMDK size reported by VMware vSphere API for virtual machine
configuration is different than actual size of vmdk file. This can be
the result of running a storage alignment tool on vmdk files before
backup.

System action:

Restore processing stops.

User response:

Reissue the restore command with the testflag -VMRESTORE_INCVMDKSIZE.

------------------------------------------------------------------------
ANS5232I

The virtual machine backup operation was skipped.



Explanation:

The virtual machine backup operation was skipped. Check the error log
for details on why the operation was skipped.

System action:

Processing of the virtual machine is skipped

User response:

Review the console output and error logs for the details.

------------------------------------------------------------------------
ANS5233E

The directory cannot be found in the specified backup. The top-level
directory is displayed.



Explanation:

An invalid or unreachable directory path was specified.

System action:

The top-level directory is displayed instead.

User response:

Select a valid directory and change the backup again.

------------------------------------------------------------------------
ANS5234E

The system cannot connect to the virtual machine or the machine is
powered off. If the problem persists, contact your administrator.



Explanation:

The virtual machine is powered off or the Windows domain administrator
credentials is not correct.

System action:

Processing stops.

User response:

Ensure that the virtual machine is powered on. Use dsmc SET PASSWORD
-type=DOMAIN 'domain\userid' 'password' to update the Windows domain
credentials. Then, try the operation again.

------------------------------------------------------------------------
ANS5235E

The virtual machine cannot be reached or a firewall is blocking the
connection to the machine.



Explanation:

The file restore interface cannot reach the virtual machine or a
firewall is blocking the connection.

System action:

Processing stops.

User response:

Ensure that the virtual machine is powered on. If the virtual machine is
powered on, review the firewall rules to ensure that the correct ports
are opened. Also ensure that the virtual machine host name and TCP/IP
address are resolving in the DNS server and there are no network issues.

------------------------------------------------------------------------
ANS5236E

You do not have permission to restore the file to the destination
folder.



Explanation:

The user does not have permission to restore files to the selected
destination.

System action:

Processing stops.

User response:

Ensure that the user has proper permissions to restore files to selected
location.

------------------------------------------------------------------------
ANS5237E

File Restore is not set up correctly or the virtual machine cannot be
reached. Contact your administrator for assistance.



Explanation:

The user is unable to log in to the file restore interface due to one of
the following reasons:

*  The configuration of File Restore is incorrect because the Windows
   domain credentials do not have the correct permissions.

*  The virtual machine is powered off or a firewall is blocking the
   connection.

*  A network issue.



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.



------------------------------------------------------------------------
ANS5238E

Cannot get list of Linux block devices on the Linux mount proxy machine.



Explanation:

The Linux command blkid to get the list of block devices fails.

System action:

The operation stops.

User response:

Check that the blkid Linux command is working correctly on the Linux
mount proxy machine.

------------------------------------------------------------------------
ANS5239E

Cannot add the disk flat file 'flat file because no free loop devices
are available on the Linux mount proxy machine.



Explanation:

Some Linux machines have a limited number of loop devices. For file
restore operations of a local snapshot, it is required that each Linux
proxy machine have a free loop device for each volume to mount.

System action:

The file restore operation stops.

User response:

Increase the number of loop devices on the Linux mount proxy machine or
install the Linux mount proxy on a Linux distribution where the number
of loop devices is not limited.

------------------------------------------------------------------------
ANS5240E

Setting up device mappings for the disk flat file 'flat file' by using
the kpartx command on the Linux mount proxy machine failed with rc 'rc'.



Explanation:

A failure occurred trying to create devices with the Linux utility
command kpartx.

System action:

The file restore operation stops.

User response:

Check that the kpartx Linux command is working correctly on the Linux
mount proxy machine.

------------------------------------------------------------------------
ANS5241E

Mounting block device 'device_name' to 'mount-point' failed with rc
'rc'.



Explanation:

A file restore operation was unable to mount the original block device
on the Linux mount proxy. The mount command on the Linux mount proxy
produced an unexpected error and the related block device was not
mounted. The specified volume was skipped.

System action:

File restore operations continue with the next device.

User response:

Update the Linux mount proxy OS. This behavior has been observed with
LVM on a guest machine with Redhat 7.3 and Redhat 6.5 on the mount
proxy.

------------------------------------------------------------------------
ANS5242E

Assembling the RAID device 'device' failed with rc 'rc'.



Explanation:

A failure occurred trying to assemble a RAID device on the Linux mount
proxy.

System action:

Marking device as 'mount_failed' and continuing the file restore
operation.

User response:

Check the consistency of the RAID device.

------------------------------------------------------------------------
ANS5243E

Activating LVM device number 'device-number' failed with rc 'rc'.



Explanation:

A failure occurred trying to activate LVM device on the Linux mount
proxy.

System action:

Marking device as 'mount_failed' and continuing the file restore
operation.

User response:

Check the consistency of the LVM device.

------------------------------------------------------------------------
ANS5244E

It is not possible to detect the original mount points because the etc
path cannot be found in any mounted volumes.



Explanation:

To detect the original mount points, it is required to read the fstab
and mtab files that are present in the etc path.

System action:

The file restore operation continues.

User response:

Check that the original virtual machine guest has a valid etc path.

------------------------------------------------------------------------
ANS5245W

TCPWINDOWSIZE optionCur is specified, but exceeds the maximum value
allowed by IBM Spectrum Protect. TCPWINDOWSIZE optionNew will be used
instead.



Explanation:

Refer to product manual for more information about the TCPWINDOWSIZE
option.

System action:

The operation continues with the maximum value allowed by IBM Spectrum
Protect.

User response:

Set TCP window size to a value in the allowable range.

------------------------------------------------------------------------
ANS5246W

TCPWINDOWSIZE optionCur is specified, but exceeds the maximum value
allowed by the operating system. TCPWINDOWSIZE optionNew will be used
instead.



Explanation:

The specified value is within the range allowed by IBM Spectrum Protect,
but the operating system restricts the value to something less.

System action:

The operation continues with the maximum value allowed by the operating
system.

User response:

Set TCP window size to a value allowed by the operating system.

------------------------------------------------------------------------
ANS5247E

The configuration for File Restore is not complete. Contact your
administrator for assistance.



Explanation:

The user is unable to log in to the file restore interface because the
Windows domain credentials are missing.

System action:

Processing stops.

User response:

The administrator must provide the Windows domain administrator
credentials in the File Restore page of the configuration notebook in
the Data Protection for VMware vSphere GUI.

------------------------------------------------------------------------
ANS5248E

It is not possible to detect the original mount points because the
original virtual machine guest file system information cannot be read.
rc='rc'.



Explanation:

To detect the original mount points, it is required to read the fstab
file that is present in the etc path.

System action:

The file restore operation continues.

User response:

Check that the original virtual machine guest has a valid fstab file.

------------------------------------------------------------------------
ANS5249E

The virtual machine restore operation failed.



Explanation:

The virtual machine restore operation failed. Check the error log for
details on why the operation failed.

System action:

Processing stops

User response:

Review the console output and error logs for the details on the problem.
Fix any issues and restart the operation.

------------------------------------------------------------------------
ANS5250E

An unexpected error was encountered. IBM Spectrum Protect function name
: function-name IBM Spectrum Protect function : function-desc IBM
Spectrum Protect return code : TSM-rc IBM Spectrum Protect file :
file-name (line-number)



Explanation:

None.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS5251E

The snapshot provider is not available for this operation.



Explanation:

IBM Spectrum Protect was not able to take a snapshot because the
snapshot provider is not available.

System action:

Processing stopped.

User response:

If you are attempting an operation using the Microsoft Volume Shadow
Copy service make sure that Volume Shadow Copy service is installed on
the system and also ensure that the IBM Spectrum Protect snapshot plugin
"pivss.dll" is present.

------------------------------------------------------------------------
ANS5252E

IBM Spectrum Protect attempted to execute a system command which failed.
command : command rc : rc



Explanation:

IBM Spectrum Protect needed to execute a system command in conjunction
with a snapshot operation.

System action:

Processing stops.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS5253W

The system could not create Volume Shadow Copy Services staging
directory 'dir'.



Explanation:

The system was unable to create a user-specified location for the Volume
Shadow Copy Services staging area. The default staging area on the
system drive will be used instead.

System action:

Processing continues.

User response:

Check the option to specify the staging area for Volume Shadow Copy
Services operations and specify a valid location.

------------------------------------------------------------------------
ANS5254E

The Volume Shadow Copy Services snapshot plugin 'pivss.dll' was not
found.



Explanation:

The system cannot find the VSS snapshot plugin 'pivss.dll' in any of the
plugin locations.

System action:

Processing stops.

User response:

Check the IBM Spectrum Protect installation to ensure the plugin was
installed correctly.

------------------------------------------------------------------------
ANS5255E

Unable to copy local file 'local-file' to remote location 'remote-file'.



Explanation:

An attempt to transfer a file to a remote system failed..

System action:

Processing stops.

User response:

Ensure that the directory path on the remote system exists and that the
IBM Spectrum Protect application has the proper authority to write to
that location.

------------------------------------------------------------------------
ANS5256W

Cannot find the original mtab file.



Explanation:

To detect the original mount points, it is required to read the original
mtab information. In some Linux distributions, the mtab file could be a
symbolic link to /proc/self/mounts that could interfere with the Linux
mount proxy.

System action:

The file restore operation continues.

User response:

Check that the original virtual machine guest has a valid mtab file.

------------------------------------------------------------------------
ANS5257E

The volume 'volume' does not support the requested VSS operation.



Explanation:

The volume does not support the requested VSS operation. Some reasons
for this error include the following conditions:

*  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:

Try the backup again, and use a supported backup destination. If you are
backing up Hyper-V VMs and the VSSUSESYSTEMPROVIDER option is set to
YES, try the operation again, with the VSSUSESYSTEMPROVIDER option set
to NO.

------------------------------------------------------------------------
ANS5258E

Microsoft volume shadow copy snapshot initialization failed.



Explanation:

IBM Spectrum Protect encountered an error while initializing the
Microsoft Volume Shadow Copy Service for backup or restore. The IBM
Spectrum Protect error log and Windows event log can contain additional
information about this error.

System action:

IBM Spectrum Protect stops the operation.

User response:

Try the operation again. If the error persists, review the IBM Spectrum
Protect error log and Windows event log for information related to this
error. Use the Windows command VSSADMIN LIST WRITERS to determine the
status of the Volume Shadow Copy service. Reboot the machine to clear
the volume shadow copy error state. If the system is a Domain Controller
and the Active Directory service is stopped, restart the Active
Directory service.

------------------------------------------------------------------------
ANS5259W

Failed to update volume 'volume' for read-write access used for
'volume'.



Explanation:

Changing the volume to read-write access requires exclusive access to
the volume. If the volume is opened by any application, this operation
will fail.

System action:

Processing continues.

User response:

Close all the applications using the volumes and use operating system's
interface to mount failed volume for read-write access.

------------------------------------------------------------------------
ANS5260W

Restore object 'volume' has volume either source 'volume' or target
'volume' volume that has already been selected for restore from a
different snapshot volumes. It will be restore using file-level copy.



Explanation:

This error can occur when multiple objects are selected for snapshot
restore and have data overlapping on the volumes and were selected for
restore from different backup versions. Snapshot restore can only be
performed from one local backup.

System action:

The restore object identified in the message will be restored using the
file-level copy after snapshot restore is completed.

User response:

Retry the restore of identified object separately for faster restore
using snapshot.

------------------------------------------------------------------------
ANS5261W

An attempt to create a snapshot has failed. Another attempt will be made
to create the snapshot in number seconds.



Explanation:

An attempt to create a snapshot has failed with a retryable error. The
program will wait for a short time and retry the operation.

System action:

None.

User response:

Check the IBM Spectrum Protect error logs for additional information.

------------------------------------------------------------------------
ANS5262I

Snapshot restore will failover to file-level copy from snapshot volume.



Explanation:

Snapshot restore is not possible due to an error at this time. IBM
Spectrum Protect will automatically fail over to other restore method to
complete the restore operation.

System action:

Processing continues.

User response:

Check the error log for more information from messages preceding this
one to identify the error condition.

------------------------------------------------------------------------
ANS5263E

Snapshot module for 'snapshot provider' failed with error 'error msg'.



Explanation:

The snapshot module for identified snapshot provider failed to perform
the operation and returned with the identified error.

System action:

Restore may automatically failover to alternate restore method
'file-level copy from snapshot volume' if possible. Otherwise,
processing stops.

User response:

Check the error log for more information from messages preceding this
one. Use snapshot provider interface to identify and correct the
problem.

------------------------------------------------------------------------
ANS5264W

No snapshot plugin found for 'snapshot provider' snapshot provider.



Explanation:

The snapshot restore requires a plugin for the specified snapshot
provider type. The plugin must be installed under IBM Spectrum Protect
directory.

System action:

Restore will failover to alternate restore method of 'file-level copy
from snapshot volume'.

User response:

Contact your IBM Spectrum Protect administrator to obtain and install
the required plugin module.

------------------------------------------------------------------------
ANS5265W

Snapshot restore has already been initialized using 'snapshot provider'
provider module. Another module for 'snapshot provider' provider can not
be loaded at the same time for restore of 'object name'.



Explanation:

This error occurs when restoring multiple LOCAL backup objects that were
created using different snapshot providers. Snapshot restore can only be
done using one snapshot interface.

System action:

Restore will failover to file-level copy restore from snapshot volume.

User response:

If snapshot restore is desired for the object identified in the message,
restore it using a separate command.

------------------------------------------------------------------------
ANS5266E

File-level copy restore of 'object name' failed.



Explanation:

Data files could not be copied from the local 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 the error log for more information from messages preceding this
one.

------------------------------------------------------------------------
ANS5267E

Disk Mapper module failed for the operation.



Explanation:

An underlying IBM Spectrum Protect operation has failed to perform the
operation due to a system error.

System action:

Processing stops.

User response:

Check the error log for more information from messages preceding this
one to identify cause of the failure. Contact IBM Spectrum Protect
administrator for more information.

------------------------------------------------------------------------
ANS5268W

The Microsoft Volume Shadow Copy Services writer 'name' current state
(state) is not valid for the current operation.



Explanation:

None.

System action:

The system will retry the operation automatically after thirty seconds
up to three times to allow the writer to return to the proper state. If
after three attempts the writer is still in the incorrect state, the
operation will fail.

User response:

Determine if there are other Volume Shadow Copy Services operations that
are occurring concurrently with the current operation.

------------------------------------------------------------------------
ANS5269E

The Microsoft Volume Shadow Copy Services writer 'name' current state
(state) is not valid for the current operation or cannot be determined.
The last error reported is 'error'.



Explanation:

None.

System action:

Processing stops.

User response:

Check the Microsoft event log to determine if there are any problems
with the writer.

------------------------------------------------------------------------
ANS5270E

A VSS restore request with timestamp 'time1' conflicts with a restore
request with timestamp 'time2'



Explanation:

A VSS restore request was issued which requires restoring multiple
components which reside in VSS backup documents with different backup
timestamps. For example, a user backs up Exchange storage group STG1 on
Monday and Exchange storage group STG2 on Tuesday. On Wednesday, the
user tries to restore STG1 and STG2.

System action:

Processing stops.

User response:

Resubmit the restore request as separate requests for each component.
For example, if you receive this error trying to restore Exchange
storage groups STG1 and STG2, resubmit a restore request for storage
group STG1 and a separate restore request for storage group STG2.

------------------------------------------------------------------------
ANS5271E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
before snapshot initialization.



Explanation:

None.

System action:

Processing stops.

User response:

See the IBM Spectrum Protect error logs for additional information.

One of the VSS writers is in an invalid or unexpected state. Try the
command "vssadmin list writers" and check the state of VSS writers.
Writers must be in STABLE state before IBM Spectrum Protect can continue
with VSS operations. Some of the writers can recover automatically from
minor errors. In most cases, restarting a writer solves the problem. The
easiest way to restart writers is to restart the operating system. It is
possible to restart the specific service that implements a VSS writer,
but it is difficult to determine which service to restart.

------------------------------------------------------------------------
ANS5272E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
after snapshot initialization.



Explanation:

None.

System action:

Processing stops.

User response:

See the error log for additional information.

------------------------------------------------------------------------
ANS5273E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
after taking a snapshot.



Explanation:

None.

System action:

Processing stops.

User response:

See the error log for additional information.

------------------------------------------------------------------------
ANS5274E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
after backup completion.



Explanation:

None.

System action:

Processing stops.

User response:

See the error log for additional information.

------------------------------------------------------------------------
ANS5275E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
before restore initialization.



Explanation:

None.

System action:

Processing stops.

User response:

See the error log for additional information.

------------------------------------------------------------------------
ANS5276E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
after preparing for a restore operation.



Explanation:

None.

System action:

Processing stops.

User response:

See the error log for additional information.

------------------------------------------------------------------------
ANS5277E

A Microsoft Volume Shadow Copy Services writer is in an invalid state
after restore termination.



Explanation:

None.

System action:

Processing stops.

User response:

See the error log for additional information.

------------------------------------------------------------------------
ANS5278W

Cannot detect all the original mount points because the number of
standard devices mounted 'device-number' is different than the number of
standard devices found in fstab and mtab files 'device-number'.



Explanation:

This is a requisite for the recognition of the standard devices.

System action:

The file restore operation continues.

User response:

Check that the devices are correct in the fstab and mtab of the virtual
machine guest.

------------------------------------------------------------------------
ANS5279E

Error processing 'filename': file not found.



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 Spectrum Protect.

System action:

Processing stops.

User response:

None.

------------------------------------------------------------------------
ANS5280E

Object enumeration from a file set or file list failed.



Explanation:

For more information, see the IBM Spectrum Protect client error log.
This message is always accompanied by error log message ANS5279E if the
object was not found or by ANS5250E for other causes, for example,
access was denied. These messages identify the object in question.

System action:

Processing stopped.

User response:

See the user response based on other messages in the client error log.

------------------------------------------------------------------------
ANS5281E

A remote backup failure has occurred. remote node name : node remote
address : address multi-node name : multi-node error message : msg
return code : rc



Explanation:

For more information, see the IBM Spectrum Protect client error log on
the remote system.

System action:

Processing stopped.

User response:

See the user response based on other messages in the client error log.

------------------------------------------------------------------------
ANS5282E

A remote backup failure has occurred.



Explanation:

For more information, see the IBM Spectrum Protect client error log.

System action:

Processing stopped.

User response:

See the user response based on other messages in the client error log.

------------------------------------------------------------------------
ANS5283E

The operation was unsuccessful.



Explanation:

None.

System action:

Processing stopped.

User response:

See the user response based on other messages in the client error log.

------------------------------------------------------------------------
ANS5284I

IBM Spectrum Protect has detected an incomplete setup! The client
options file 'dsm.opt' was not found, while the system options file
'file-path' exists! The wizard will guide you through the configuration
process of the initial basic IBM Spectrum Protect client options files
replacing your current option file. Would you like to continue?



Explanation:

IBM Spectrum Protect has detected an incomplete setup. The user options
file, dsm.opt, was not found. Additionally, a system options file,
dsm.sys, was found. To complete the configuration the configuration
wizard will create dsm.opt and replace dsm.sys with minimal settings.

System action:

IBM Spectrum Protect may stop

User response:

If the current version of dsm.sys is needed, rename the file and restart
IBM Spectrum Protect. If the current version is not needed, select yes
and allow IBM Spectrum Protect to replace the file.

------------------------------------------------------------------------
ANS5285E

The Microsoft Volume Shadow Copy Services (VSS) backup XML document is
not valid for restore. For more information, see the client error log.



Explanation:

Microsoft has released a Volume Shadow Copy Services (VSS) update in the
following operating system versions:

*  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.

------------------------------------------------------------------------
ANS5286I

The VSS Instant Restore operation was successful but some existing VSS
snapshots have been deleted by the VSS provider.



Explanation:

A successful VSS Instant Restore operation was performed for snapshot
volumes that were in a dependent relationship. In order for the restore
process to succeed, it was necessary to remove the snapshot volumes
causing the dependency. Those snapshot volumes typically represent newer
snapshot backups. This forced IBM Spectrum Protect to remove the backups
that included the deleted snapshots. This situation is typical when
using SAN Volume Controller (SVC) space-efficient volumes that have
multiple snapshots.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS5287W

VSS restore operation will be performed using VSS Fast Restore because
the XIV VSS Hardware Provider is at level 2.2.2.



Explanation:

XIV VSS Hardware Provider 2.2.2 has issues with VSS Instant Restore.
Please update the XIV VSS Hardware Provider to version 2.2.3, or later.

System action:

Processing continues.

User response:

Update XIV VSS Hardware Provider to version 2.2.3, or later.

------------------------------------------------------------------------
ANS5288W

Test flag DISCARDZEROFILEDATA enabled. Discarding data for zero length
object file-name



Explanation:

During the restore of a zero length file or directory, data was
decompressed. This data could be Extended Attributes, Alternate Streams,
or ACL data. By default this data is restored. Because the
DISCARDZEROFILEDATA test flag is set the data is discarded.

System action:

The data is discarded and processing continues

User response:

Note the file or directory name in this message and determine if the
discarded data needs to be reset through some other means.

------------------------------------------------------------------------
ANS5289W

The sequence of the devices is not correct and it is not possible to
identify all the original mount points. The volume 'volume' is not
consistent. The detection of the original mount points is stopped.



Explanation:

The correct order of the devices is required for the recognition of the
standard devices.

System action:

The detection of the original mount points is stopped. The file restore
operation continues.

User response:

Check that the devices are correct in the fstab and mtab files of the
virtual machine guest.

------------------------------------------------------------------------
ANS5290W

Devices of type 'device_type' are not supported. Skipping device
'device_name'.



Explanation:

The device detected is not supported.

System action:

The device for the target virtual machine is not mounted. The operation
continues.

User response:

Use a different type of device on the guest machine. Only
ext2,ext3,ext4,xfs, btrfs and reiserfs are supported devices.

------------------------------------------------------------------------
ANS5291E

An error occurred while attempting to delete the temporary linked clone
virtual machine 'linked clone name' (rc=return code). Check if this
virtual machine still exists and delete it manually.



Explanation:

It was not possible to delete the linked clone virtual machine. This
temporary virtual machine was created for file restore purposes to mount
a local snapshot. This virtual machine may have been manually renamed,
or accidentally modified or deleted.

System action:

The file restore cleanup operation continues.

User response:

Check if this virtual machine still exists and delete it manually.

------------------------------------------------------------------------
ANS5292E

A valid password file was not found for server 'server-name'. The
administrator for your system must run the backup-archive client and
enter the password to store it locally. Additionally, the administrator
needs to give the non-administrative user read access to the password
file.



Explanation:

The file containing the stored password for the specified server
server-name is unavailable.

System action:

Processing ends.

User response:

The administrator for your system must set and store a new password and
make the password file readable by the non-administrative user.

------------------------------------------------------------------------
ANS5293E

A valid password file was found for server 'server-name', but it does
not have read access granted to non-administrative users. The
administrator for your system needs to change the password files to
allow non-administrative users to read the files or the user needs to
become an authorized user.



Explanation:

The file containing the stored password for the specified server
server-name is not readable by non-administrative users.

System action:

Processing ends.

User response:

The administrator for your system must set the password files to be
readable by the non-administrative user.

------------------------------------------------------------------------
ANS5294E

The current user is not an IBM Spectrum Protect Authorized user. You
must be an IBM Spectrum Protect Authorized user to perform the current
operation.



Explanation:

In order to perform normal IBM Spectrum Protect operations you must be
an Authorized user. Please refer to the 'IBM Spectrum Protect UNIX and
Linux Backup-Archive Clients Installation and User's Guide' for details
configuring your environment to allow the system user to become an IBM
Spectrum Protect Authorized user.

System action:

Processing ends.

User response:

The administrator must update the dsm.sys options file to set the
PASSWORDDIR option to a location readable by the current user or to give
the current user read/write permissions to the password file.

------------------------------------------------------------------------
ANS5296I

The virtual machine 'vm-name' contains one or more virtual disks that
are of type Thick Eager Zero. Creating disks of this type can take a
long time. This restore operation might time out before the disks are
ready.



Explanation:

Restoring a VM that has Thick Eager Zero virtual disks can take a long
time to complete because the disks are zero-filled to obscure any
previous content. The time that is required to provision a Thick Eager
Zero disk depends on processing loads on the VMware resources (vCenter
and datastores).

System action:

None

User response:

Reattempt the restore operation at a time when the processing load is
light on the datacenter and vCenter resources

------------------------------------------------------------------------
ANS5298E

A Flashcopy background copy is in progress between source volume: and
target volume: .



Explanation:

A Flashcopy background copy from a previous operation is not complete
for the given source and target volumes.

System action:

Command will fail.

User response:

Please wait until the background copy is complete and retry the command.

------------------------------------------------------------------------
ANS5300E

Error detected in specified file list 'file list name' during processing
of line line number: found an invalid external object ID / inode number
/ inode generation number / restore order number / alias entry: 'invalid
entry'. Invalid line: 'invalid entry'



Explanation:

File list parsing failed because of an invalid entry.

System action:

The operation aborted because of an file list error.

User response:

Correct the invalid file list entry and restart the operation.

------------------------------------------------------------------------
ANS5301E

Error detected in specified file list 'file list name' during processing
of line line number: found an invalid ordering of external object IDs.
ext. object ID of previous file: previous external object ID ext. object
ID of current file: current external object ID



Explanation:

File list parsing failed because of an invalid ordering of the external
object IDs.

System action:

The operation aborted because of an file list error.

User response:

Correct the invalid file list ordering and restart the operation.

------------------------------------------------------------------------
ANS5302E

File list stream error to file 'file list name' detected during
processing of line line number.



Explanation:

File list processing failed because of an stream error.

System action:

The operation aborted because of an file list stream error.

User response:

Check the specified file list and restart the operation.

------------------------------------------------------------------------
ANS5303I

***** date Processed count IBM Spectrum Protect server and count file
list objects *****



Explanation:

IBM Spectrum Protect has processed the specified number of IBM Spectrum
Protect server and file list objects.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS5304E

program-name: synchronous file deletion failed for external object ID:
external object ID.



Explanation:

The HSM client could not delete an object on the IBM Spectrum Protect
Server.

System action:

The current file is skipped for synchronous file deletion and the
process will continue.

User response:

Check the IBM Spectrum Protect server log file.

------------------------------------------------------------------------
ANS5307E

The session is rejected. The server does not allow a signon of a client
that is not enabled for space-management retention-protection.



Explanation:

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

System action:

The session is not started.

User response:

See your system administrator.

------------------------------------------------------------------------
ANS5308W

No matching NAS nodes were found on the server.



Explanation:

You tried to start a backup or restore of a NAS system but the IBM
Spectrum Protect client was not able to find a corresponding node on the
server that is configured to access the NAS system.

System action:

The NAS backup or restore window will be closed.

User response:

See your IBM Spectrum Protect administrator for assistance in
associating your node with a NAS node that has the authority to access
the NAS system on the server. Then try the operation again.

------------------------------------------------------------------------
ANS5821E

Cannot connect to Active Directory.



Explanation:

IBM Spectrum Protect could not connect to Active Directory. The Active
Directory is either not running or you don't have enough permissions to
use it.

System action:

Processing stops.

User response:

Make sure your system is set up as Active Directory controller and the
the service is active. Make sure you are logged in as a user with
sufficient rights to administer the Active Directory.

------------------------------------------------------------------------
ANS5822E

No Active Directory objects match query.



Explanation:

A search has been performed in Active Directory; however, no objects
matching the query were found.

System action:

Processing stops.

User response:

Make sure you specify a valid distinguished name of Active Directory
object or a container, or a valid wildcarded name, and that you have
sufficient rights to administer the Active Directory.

------------------------------------------------------------------------
ANS5823W

Object exists, skipping



Explanation:

The client tried to restore the specified object, but the object already
existed in the target restore location and the user chose not to replace
the existing object.

System action:

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

User response:

The object was skipped because either REPLACE NO was in effect, causing
all existing objects to 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 skip the object was deliberate.
Otherwise the operation can be retried using either REPLACE ALL
(automatically replace existing object) or REPLACE PROMPT (prompt the
user whether to replace the object).

------------------------------------------------------------------------
ANS5824E

Invalid Active Directory search specification.



Explanation:

The search specification for Active Directory objects is not valid.

System action:

Processing stops.

User response:

Refer to the documentation for supported Active Directory syntax.

------------------------------------------------------------------------
ANS5825E

Reanimate 'tombstone-name' to 'distinguished-name' failed. See the error
log for more details.



Explanation:

An attempt to reanimate Active Directory tombstone object has been
performed, but an error occurred.

System action:

Processing continues to process all other tombstone objects per user's
request.

User response:

None.

------------------------------------------------------------------------
ANS5826E

Restoring to a read-only domain controller is not allowed.



Explanation:

An attempt to restore to a read-only domain controller.

System action:

Processing stops.

User response:

None.

------------------------------------------------------------------------
ANS5827E

A backup copy of the Active Directory database was not found.



Explanation:

An attempt to restore Active Directory objects from a database that was
not backed up.

System action:

Processing stops.

User response:

Verify the Active Directory was backed up with system state.

------------------------------------------------------------------------
ANS5828E

A system state file space was not found on the server. Active Directory
functions can not be executed.



Explanation:

An attempt to restore the Active Directory database from a system state
backup that does not exist.

System action:

Processing stops.

User response:

Verify that system state was backed up or back up the system state then
retry the command.

------------------------------------------------------------------------
ANS5829E

A system state backup on the specified date was not found. Active
Directory functions can not be executed.



Explanation:

An attempt to restore the Active Directory database from a system state
backup that does not exist.

System action:

Processing stops.

User response:

Verify that system state was backed up on the specified date or specify
a new date.

------------------------------------------------------------------------
ANS5830E

Restore of object 'tombstone-name' is not allowed by Active Directory.



Explanation:

Object of certain types cannot be restored. This is a system limitation.

System action:

Processing continues to process all other objects per user's request.

User response:

None.

------------------------------------------------------------------------
ANS5831E

Restore for this object is not allowed by Active Directory.



Explanation:

Object of certain types cannot be restord. This is a system limitation.

System action:

Processing continues to process all other objects per user's request.

User response:

None.

------------------------------------------------------------------------
ANS5832E

Reanimate tombstone object failed. See the error log for more details.



Explanation:

An attempt to reanimate Active Directory tombstone object has been
performed, but an error occurred.

System action:

Processing continues to process all other tombstone objects per user's
request.

User response:

None.

------------------------------------------------------------------------
ANS5833E

This system is a Domain Controller but the Active Directory service is
stopped. You can not perform the operation unless the Active Directory
service is running.



Explanation:

The Active Directory service must be running when you back up or restore
the system state or operate on Active Directory objects. When the Active
Directory service is running, it can be in online state or in offline
state. When you query or restore Active Directory objects, or back up
the system state, the Active Directory service must be online. When you
restore the system state, the Active Directory service must be offline
(but not stopped).

System action:

Processing stopped.

User response:

If you are querying or a restoring the Active Directory objects or
backing up the system state, put the Active Directory service in online
state by starting the Active Directory service. If you are restoring the
system state, put the Active Directory service in offline state by
rebooting to the Active Directory Restore Mode. When the Active
Directory service is in the appropriate state, retry the operation.

------------------------------------------------------------------------
ANS5834E

Unexpected LDAP error occurred. See the error log for more details.



Explanation:

An unexpected error occurred during Active Directory tombstone
reanimation.

System action:

Processing continues to process all other tombstone objects per user's
request.

User response:

Check the error log for detailed information on the LDAP error.

------------------------------------------------------------------------
ANS5835E

An LDAP operation returned return code: 'error string'



Explanation:

An unexpected error occurred during Active Directory tombstone
reanimation.

System action:

Processing continues to process all other tombstone objects per user's
request.

User response:

None.

------------------------------------------------------------------------
ANS5836W

One or more attributes were not restored. See the error log.



Explanation:

During processing of an Active Directory object, one or more object
attributes could not be restored.

System action:

Processing continues to process all other Active Directory objects per
user's request.

User response:

Check the error log for detailed information on which attribute(s) could
not be restored.

------------------------------------------------------------------------
ANS5837W

'object name': attribute 'attribute name' could not be restored.



Explanation:

The listed attribute could not be restored during processing on the
Active Directory object.

System action:

Processing continues to process all other Active Directory objects per
user's request.

User response:

None.

------------------------------------------------------------------------
ANS5838E

The utility dsamain.exe does not exist on the system. You cannot perform
the operation unless IBM Spectrum Protect can launch this utility.



Explanation:

You attempted to launch dsamain.exe, but the utility does not exist.

System action:

Processing stopped.

User response:

Verify that the dsamain.exe utility exists in the Windows system32
directory. When you can run the utility independently of IBM Spectrum
Protect, retry the operation.

------------------------------------------------------------------------
ANS5839E

The Active Directory object specification is not allowed.



Explanation:

You attempted to restore the domain object (starting with "DC="), or you
attempted to restore all objects ("name=*"), or you did not specify
anything.

System action:

Processing stops.

User response:

Modify the specification then retry the operation.

------------------------------------------------------------------------
ANS5840E

The current user is not a member of the Administrators group, and cannot
perform this function.



Explanation:

You must be a member of the Administrators group to perform the Active
Directory objects function.

System action:

Processing stops.

User response:

Log on with a user who is a member of the Administrators group or add
this user to the Administrators group then retry the operation.

------------------------------------------------------------------------
ANS5841E

Active Directory database could not be opened.



Explanation:

An error occurred while opening the restored Active Directory database.

System action:

Processing stopped.

User response:

Make sure ntdsutil.exe utility is located in the same directory with IBM
Spectrum Protect client executables. If it doesn't exist, reinstall the
client. Verify that the dsamain.exe utility exists in the Windows
system32 directory. When you can run the utility independently of IBM
Spectrum Protect, retry the operation. If the problem persists, contact
the support.

------------------------------------------------------------------------
ANS5842E

'tombstone-name': object class violation.



Explanation:

Object class error violation occurred during tombstone reanimation. This
can happen if the Active Directory schema was modified and is no longer
compatible with the tombstone.

System action:

Processing continues to process all other objects per user's request.

User response:

Recreate the failing object manually or restore it from a backup.

------------------------------------------------------------------------
ANS5843E

Object class violation.



Explanation:

Object class error violation occurred during tombstone reanimation. This
can happen if the Active Directory schema was modified and is no longer
compatible with the tombstone.

System action:

Processing continues to process all other objects per user's request.

User response:

Recreate the failing object manually or restore it from a backup.

------------------------------------------------------------------------
ANS5844E

Unable to update password.



Explanation:

An error occurred during the password update attempt.

System action:

The password is not updated on the server.

User response:

Try to update the password again.

------------------------------------------------------------------------
ANS5845E

Unable to update password because the maximum number of update attempts
has been exceeded.



Explanation:

This message is issued after making 3 unsuccessful attempts to update
the password. The original password for the node was entered
incorrectly; the new password does not meet the length or valid
character requirements for our passwords; or there was a mismatch
between the first and second times the new password was entered.

System action:

The password is not updated.

User response:

*  Make sure the original password is entered correctly. Contact your
   IBM Spectrum Protect administrator for further assistance if you do
   not know the original password.

*  Make sure the new password meets the password length and character
   requirements.

*  You will be prompted to enter the new password two times, so make
   sure it is entered correctly both times.

------------------------------------------------------------------------
ANS5876I

SET EVENT Activate Retention completed



Explanation:

The Data Retention ACTIVATE transaction has completed.

System action:

IBM Spectrum Protect activated the objects that were selected.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5877I

SET EVENT Hold completed



Explanation:

The Data Retention HOLD transaction has completed.

System action:

IBM Spectrum Protect held the objects that were selected.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS5878I

SET EVENT Release completed



Explanation:

The Data Retention RELEASE transaction has completed.

System action:

IBM Spectrum Protect released the objects that were selected.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS6586E

Recovery Agent operation failed.



Explanation:

The Recovery Agent operation on a VMVSS snapshot failed.

System action:

Processing stops.

User response:

Check the Recovery Agent logs and error messages, resolve the problem,
and try the operation again.

------------------------------------------------------------------------
ANS6587W

VMVSS backup failed to back up Exchange mailbox history from virtual
machine 'VM-Name'.



Explanation:

An error occurred when a data mover tried to back up the Exchange
mailbox history from a virtual machine. The current version of Data
Protection for Exchange might not support uploading mailbox history at
the same time as a virtual machine backup. The error code indicates the
reason for the failure.

System action:

Processing continues without backing up the mailbox history information.

User response:

Try to back up mailbox history on guest vm by using Data Protection for
Exchange command 'tdpexcc.exe backup * full /UpdateMailboxInfoOnly'.
Upgrade Data Protection for Exchange if the current product level does
not support mailbox history backup command. Use traceflags VMTSMVSS in
data mover dsm.opt file to further diagnose the problem.

------------------------------------------------------------------------
ANS6718E

The path contains too many nested subdirectories. The maximum number of
nested directories is 1400.



Explanation:

To avoid exhausting system resources, the client stops processing
directory structures that exceed the maximum nesting depth. Directories
that exceed the maximum nesting depth are not typical.

System action:

Processing of the current operation is stopped.

User response:

Determine whether the directory is valid. Directory structures of this
depth are not typical, and could indicate a problem with the file system
structure. An example of such a directory is if the directory is
cyclical. If the directory is not valid, remove or repair the directory,
then try the operation again. If the directory is valid, reduce the
depth of the directory structure. Then try the operation again.
Alternatively you can use an EXCLUDE.DIR statement to exclude the
directory from backup or archive processing. Then try the operation
again.

------------------------------------------------------------------------
ANS7421W

The archive attribute for file filename cannot be reset. The return code
from Windows API function SetFileAttributes() is rc.



Explanation:

The client was unable to reset the archive attribute for the file
indicated in the message. This error is due to an error received from
the Windows API function SetFileAttributes().

System action:

processing stops.

User response:

Try the operation again. If the problem persists, it may be indicative
of a problem with the file. Contact your system administrator or IBM
Spectrum Protect administrator for further assistance.

------------------------------------------------------------------------
ANS7422E

Unsupported action 'action' in schedule 'schedule name'.



Explanation:

The scheduled action is unknown to the current version of the IBM
Spectrum Protect client and cannot be performed by means of a schedule.
The most likely cause is that the scheduled action requires a later
version of the backup-archive client. The unsupported action is
displayed as a number because the text description is not available.
Scheduled actions and their corresponding action number can be found by
searching for this message on the IBM Spectrum Protect support site.

System action:

The scheduled action is not performed or queried.

User response:

Search the IBM Spectrum Protect support site for this message to find
information about scheduled actions, their corresponding action numbers
and the client version at which the action is supported. Then upgrade
your IBM Spectrum Protect client to a version that supports running this
action as a scheduled event. Until the client is upgraded, you can run
the action manually if your version of the client supports it.

------------------------------------------------------------------------
ANS7423E

Use Set Access backup <vmname> -TYPE=VM for VMware backup file spaces.
Use of the long form fs-name is not allowed.



Explanation:

You have chosen to set access using the long-form VM file space name.
This name format is not platform independent and requires special
processing. Use the -TYPE=VM option and supply only the VM name.

System action:

The set access command is not processed.

User response:

Enter the set access command using the -TYPE=VM option and the short
form of the VM file space name which is simply the VM name.

------------------------------------------------------------------------
ANS7500W

Object 'object-name' could not be bound to management class
'mgmt-specified' specified in an 'option' statement.



Explanation:

The management class specified in an include statement was not valid. If
the include statement is an "INCLUDE.SIZE" statement the warning message
will be issued if an appropriate copygroup is defined for the management
class. For example, this warning will be issued on a backup operation if
no backup copygroup is defined for the management class or this message
will be issued on an archive operation if no archive copygroup is
defined for the management class.

System action:

The management class on the include statement is ignored and processing
continues.

User response:

Contact the IBM Spectrum Protect administrator to correct the
appropriate copygroup definition on the IBM Spectrum Protect Server.

------------------------------------------------------------------------
ANS7501E

An invalid host address was received. Host address is too long.



Explanation:

An invalid host parameter was found in the HTTP Request. The parameter
is too long. The maximum length for a host address is 64 characters.

System action:

IBM Spectrum Protect returns HTTP error code 400 Bad Request.

User response:

Use a host machine with a valid/shorter host address.

------------------------------------------------------------------------
ANS7502E

An invalid filename was received. Filename is too long.



Explanation:

A filename passed to the dsmcad service is too long and thus invalid.

System action:

IBM Spectrum Protect returns HTTP error code 400 Bad Request.

User response:

Retry connecting to dsmcad but use a valid/shorter filename.

------------------------------------------------------------------------
ANS7507W

The node name entry is invalid. Please try again.



Explanation:

An invalid entry is entered on the Node Name field.

System action:

IBM Spectrum Protect prompts you to enter a valid node name.

User response:

Enter a valid node name or see your system administrator for the correct
syntax.

------------------------------------------------------------------------
ANS7510E

A NAS node cannot be used for this operation.



Explanation:

NAS nodes cannot be used for operations like Access Another Node.

System action:

IBM Spectrum Protect prompts you to enter a valid node name.

User response:

Enter a valid, non-NAS, IBM Spectrum Protect node name.

------------------------------------------------------------------------
ANS7524E

SSL is required.



Explanation:

SSL is required to protect the client password during authentication.

System action:

Processing terminates.

User response:

Enable SSL communication or set SSLREQUIRED to NO.

------------------------------------------------------------------------
ANS7525E

SSL is required by server.



Explanation:

SSL is required to protect the client password during authentication.

System action:

Processing terminates.

User response:

Enable SSL communication or contact your IBM Spectrum Protect server
administrator.

------------------------------------------------------------------------
ANS7526E

The SNAPSHOTROOT option is not valid with either of the following
options: -GROUPNAME and -VIRTUALFSNAME.



Explanation:

The SNAPSHOTROOT option is incompatible with the -GROUPNAME and
-VIRTUALFSNAME options and cannot be used with either one of those
options.

System action:

Processing stops.

User response:

For information about backup-archive client processing options, see IBM
Spectrum Protect Backup-archive Clients Installation and User's Guide.

------------------------------------------------------------------------
ANS7527E

The (-SNAPSHOTROOT) option is not valid in conjunction with num-specs
file specifications.



Explanation:

The (-SNAPSHOTROOT) option must be used in conjunction with only one
file specification. It cannot be used with zero file specification
(e.g., an INCREMENTAL command with no file specifications) or with more
than one file specification.

System action:

Processing stopped.

User response:

See the appropriate Using the Backup-Archive Client book for your
operating system for correct use of the named option.

------------------------------------------------------------------------
ANS7528E

The (-SNAPSHOTROOT) option for GPFS fileset is not valid without
filelist



Explanation:

The (-SNAPSHOTROOT) option for GPFS fileset is only supported using a
filelist.

System action:

Processing stopped.

User response:

See the appropriate Using the Backup-Archive Client book for your
operating system for correct use of the named option.

------------------------------------------------------------------------
ANS7529E

The specified SNAPSHOTROOT 'obj-name' is not valid for the BACKUP IMAGE
command.



Explanation:

When you use the (-SNAPSHOTROOT) option with the BACKUP IMAGE command,
SNAPSHOTROOT must specify the device name of the logical 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 be used unless
SNAPSHOTPROVIDERIMAGE has one of the following values in effect:

*  VSS

*  JFS2



System action:

Processing is stopped.

User response:

For the correct use of the (-SNAPSHOTROOT) option, see the appropriate
Backup-Archive Client Installation and User's Guide book for your
operating system.

------------------------------------------------------------------------
ANS7531E

The (-SNAPSHOTROOT) option is invalid when processing the NetWare NDS or
Server Specific Information.



Explanation:

The (-SNAPSHOTROOT) option is only intended with NetWare file server
volumes and is not compatible with processing the NDS or Server Specific
Information on NetWare.

System action:

Processing stopped.

User response:

See the appropriate Using the Backup-Archive Client book for your
operating system for correct use of the named option.

------------------------------------------------------------------------
ANS7533E

The specified file system 'obj-name' does not 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 Windows drive, or an
NFS mount. The (-SNAPSHOTROOT) option is valid for local operations
only.

System action:

Processing is stopped.

User response:

For the correct use of the (-SNAPSHOTROOT) option, see the appropriate
Backup-Archive Client Installation and User's Guide book for your
operating system.

------------------------------------------------------------------------
ANS7534W

Initialization functions cannot open /dev/tty special file. errno =
errno-value, error message



Explanation:

Special file /dev/tty, required by command line internal editor could
not be opened during initialization. The system set the error code
errno-value.

System action:

Processing continues as if EDITOR option was set to NO.

User response:

Check your terminal settings.

------------------------------------------------------------------------
ANS7535W

Command line internal editor can not be initialized.



Explanation:

EDITOR option is set to YES in the options file, but command line
internal editor can not be started.

System action:

Processing continues as if EDITOR option was set to NO

User response:

Check previous messages to determine the reason why the internal editor
could not be started.

------------------------------------------------------------------------
ANS7543E

Error: Scout is not available for object query. Either scout is not
running or the initial file system scan has not finished.



Explanation:

The scout daemon must be running for the reconcile process to do a query
for all migrated files. If the scout daemon is not running or the
initial file system scan has not finished you cannot run the reconcile
tool in orphan check mode.

System action:

Processing stops.

User response:

Ensure that the scout daemon is running. If the scout daemon is not
running, restart it and retry the command. If the scout daemon is
running, wait until it finishes the initial file system scan. You can
check the current status of the scout daemon by using the dsmscoutd
scanplan command.

------------------------------------------------------------------------
ANS7544E

ICC routine icc-routine failed with the following error: "error-string".



Explanation:

There was an error within ICC cryptography library while processing the
data. For example, this problem can occur when encrypted client data is
corrupted, so the restore operation cannot correctly decrypt it. This
message reports an error code and problem description which can be used
by IBM Spectrum Protect technical support personnel to determine the
cause of the failure.

System action:

The processing stops.

User response:

Ensure IBM Spectrum Protect software is installed correctly. If needed,
reinstall the software. Make sure you use the correct encryption key
password for the data. Make sure there are no IBM Spectrum Protect
server or network problems that may affect the transfer of data. If the
problem still exists, contact IBM Spectrum Protect technical support.

------------------------------------------------------------------------
ANS7545E

Unexpected error while encrypting the data.



Explanation:

There was an error while encrypting the data. See the error log for more
information.

System action:

The object is not backed up.

User response:

Ensure IBM Spectrum Protect software is installed correctly. If needed,
reinstall the software. Retry the operation. If the problem still
exists, contact IBM Spectrum Protect technical support.

------------------------------------------------------------------------
ANS7546E

Unexpected error while decrypting the data.



Explanation:

There was an error while decrypting the data. See the error log for more
information. This can happen if the encrypted data has been corrupted
while in storage, during the network transfer, or both.

System action:

The object is not restored.

User response:

Ensure IBM Spectrum Protect software is installed correctly. If needed,
reinstall the software. Make sure there are no IBM Spectrum Protect
server or network problems that may affect the transfer of data. Retry
the operation. If the problem still exists, contact IBM Spectrum Protect
technical support.

------------------------------------------------------------------------
ANS7547E

Unexpected error while digesting the data.



Explanation:

There was an error while digesting the data. See the error log for more
information.

System action:

The object is not backed up.

User response:

Ensure IBM Spectrum Protect software is installed correctly. If needed,
reinstall the software. Retry the operation. If the problem still
exists, contact IBM Spectrum Protect technical support.

------------------------------------------------------------------------
ANS7550E

The absolute option requires using the CreateNewBase=yes option when
performing a snapshot differential backup.



Explanation:

The absolute option specified does not have any effect when performing a
snapshot differential backup.

System action:

Processing stopped.

User response:

Try to use the CreateNewBase=yes option when performing a snapshot
differential backup.

------------------------------------------------------------------------
ANS7552I

timestamp ***** Processed count files *****



Explanation:

IBM Spectrum Protect has processed the specified number of files.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS7553W

Disabled demand migration (ENOSPC) on file system file-system-name
because of high threshold, low threshold, and pmpercentage settings.



Explanation:

The settings of high threshold = 100, low threshold = 100, and
pmpercentage = 0 are reserved to disable demand migration and
automigration. Used for GPFS driven migration.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS7554E

provider option is required if HSMBACKENDMODE is set to TSMFREE.



Explanation:

You need to specify provider option for every operation with dsmmigrate.

System action:

The operation stopped.

User response:

Specify the provider option value for the operation.

------------------------------------------------------------------------
ANS7557E

invalid provider.



Explanation:

You need to specify a valid provider for every operation with
dsmmigrate.

System action:

The operation stopped.

User response:

Specify a valid provider option value for the operation.

------------------------------------------------------------------------
ANS7558E

target option is required if HSMBACKENDMODE is set to TSMFREE.



Explanation:

You need to specify target option for every operation with dsmmigrate.

System action:

The operation stopped.

User response:

Specify the target option value for the operation.

------------------------------------------------------------------------
ANS7559E

The absolute option requires specifying the NoJournal option when
performing a Journal Based Backup for backing up fs .



Explanation:

The absolute option specified does not have any effect when performing
journal based backups.

System action:

Incremental backup is performed.

User response:

Verify that the file spaces specified are not associated with journal
based backup. If the -nojournal option is also specified, then this
message will not appear.

------------------------------------------------------------------------
ANS7566E

Unable to load external library: reason



Explanation:

There is no valid library in hsm/bin directory.

System action:

The operation stopped.

User response:

Copy a valid external library to hsm/bin directory.

------------------------------------------------------------------------
ANS7567E

program-name:External recall failed! Reason:



Explanation:

There is no valid library in hsm/bin directory.

System action:

The operation stopped.

User response:

Copy a valid external library to hsm/bin directory.

------------------------------------------------------------------------
ANS7641I

The user does not have administrative credentials to perform a full
system state backup.



Explanation:

The user account used to perform system state backup including ASR
Writer data must be a member of the Administrators group.

System action:

System state backup skips ASR Writer data.

User response:

Log on with a user who is a member of the Administrators group or add
this user to the Administrators group. Then try the system state backup
again.

------------------------------------------------------------------------
ANS7642E

An error occurred creating the registry directory structure.



Explanation:

An error occurred while creating the directory structure to save or
replace a registry key.

System action:

Registry function fails.

User response:

Ensure that the user account that is running the backup of the registry
has the proper authority. If the user account has the proper authority,
you might need to restart the machine. There might be operations that
are pending which have a file or files in the registry directory
structure locked.

------------------------------------------------------------------------
ANS7650E

The user does not have sufficient privileges to execute IBM Spectrum
Protect.



Explanation:

The user account used to execute IBM Spectrum Protect must have the
"Back up files and directories" and the "Restore files and directories"
security settings assigned.

System action:

Processing stops.

User response:

Assign the "Back up files and directories" and the "Restore files and
directories" security settings to the account using the Windows Local
Security Settings tool or use a different user-id to execute IBM
Spectrum Protect.

------------------------------------------------------------------------
ANS7660E

An error occurred replacing one or more registry keys.



Explanation:

The registry key or keys being replaced are exclusively held by another
process. The registry keys were previously restored but the system was
not restarted.

System action:

processing stops.

User response:

Restart the system and try the restore operation again.

------------------------------------------------------------------------
ANS7709E

Restore operation failed. Not all files were restored.



Explanation:

Restore operation failed due to an error.

System action:

Operation completed.

User response:

Check the error log for more details.

------------------------------------------------------------------------
ANS7899E

The client referenced a deduplicated extent that does not exist on the
IBM Spectrum Protect server



Explanation:

The deduplicated extent has been deleted from the server during the
backup or archive operation. If you are using deduplication cache, it
might be out of synch with the IBM Spectrum Protect server.

System action:

The processing stops.

User response:

Retry the operation. If the problem persists, turn off deduplication and
retry the operation.

------------------------------------------------------------------------
ANS7900I

Deduplication cache has been reset because it is not synchronized with
the IBM Spectrum Protect server



Explanation:

The deduplication cache contains deduplicated extent entries that do not
exist on the IBM Spectrum Protect server. This occurs when the extents
are deleted from the IBM Spectrum Protect server after they were
recorded in the deduplication cache.

System action:

The deduplication cache is reset, and all cache entries are removed. The
processing continues.

User response:

None

------------------------------------------------------------------------
ANS7901W

Client deduplication and option-name are mutually exclusive.



Explanation:

The following features cannot be used with deduplication: lan-free,
subfile, NAS, useTsmBuffers.

System action:

Client deduplication is disabled.

User response:

Review the configuration. Do not configure deduplication with the
lan-free, subfile, NAS, or useTsmBuffers features.

------------------------------------------------------------------------
ANS7902I

Client deduplication cache is full. Cache is reset.



Explanation:

The number of entries cached in the client deduplication cache has
exceeded the configured size for the cache.

System action:

The deduplication feature is designed so that this happens periodically.
The cache is reset to no entries.

User response:

You can reconfigure the client deduplication cache size to a larger
value to reduce the frequency of resets.

------------------------------------------------------------------------
ANS7903W

Client deduplication cache is locked by another process.



Explanation:

Another process is using the client deduplication cache. Only one
process may use it at a time.

System action:

This process does not use the client deduplication cache. The server
deduplication is not changed.

User response:

You can serialize processes using the client deduplication cache. Or you
can reconfigure the current process to use a different cache path to
avoid contention.

------------------------------------------------------------------------
ANS7904E

Client deduplication and lan-free or subfile backup are mutually
exclusive.



Explanation:

Client deduplication and lan-free or subfile are mutually exclusive.

System action:

Client deduplication is disabled.

User response:

Review the configuration. Do not configure deduplication with the
lan-free or subfile feature.

------------------------------------------------------------------------
ANS7906W

The current storage pool either ran out of space or the current object
exceeded the maxsize configuration parameter for the storage pool, data
will be stored into the next pool - deduplication is disabled.



Explanation:

The current storage pool on the IBM Spectrum Protect server is either
out of space or the current object exceeded the maxsize configuration
parameter for the storage pool . Data will be stored in the next storage
pool. Deduplication is disabled and the transaction is being resent.

System action:

Deduplication is disabled to allow the backup to complete.

User response:

Contact your system administrator to add volumes to the current storage
pool.

------------------------------------------------------------------------
ANS7907W

Connection to repository repos-name failed. Retrying with repos2-name.



Explanation:

Unable to connect to the FastBack DR Hub repository. Retry using
FastBack server repository.

System action:

Retry operation.

User response:

Specify a vaild repository.

------------------------------------------------------------------------
ANS7908E

Unable to mount FastBack snapshot policy 'Policy' client 'Client' volume
'Volume'. Reason: reason



Explanation:

IBM Spectrum Protect Mount failed.

System action:

IBM Spectrum Protect cannot continue processing.

User response:

Check the Recovery Agent logs for information about why the mount
operation failed to complete.

------------------------------------------------------------------------
ANS7912E

FastBackMount or FastBackShell is not installed.



Explanation:

Failure initializing FastBack environment. FastBackShell or
FastBackMount are not installed or are not located in the FastBack
install directory.

System action:

The FastBack operation cannot continue.

User response:

Reinstall the software. The FastBackShell and FastBackMount must be
installed on the dedicated proxy computer.

------------------------------------------------------------------------
ANS7913E

The given branch was not found in the DR Hub repository.



Explanation:

The parameter to the required fbbranch option is incorrect.

System action:

The operation cannot continue.

User response:

Correct the parameter given for the fbbranch option.

------------------------------------------------------------------------
ANS7914E

Incremental backup of FastBack client 'vmname' failed with RC rc



Explanation:

The archive or incremental backup of FastBack client volumes failed.

System action:

The archive or backup of FastBack client finished with failures. The
next FastBack client will be processed. The reason for the failure is
written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS7915E

Failure mounting FastBack client 'vmname' with FastBack command. RC=rc



Explanation:

The FastBackMount command failed to mount a FastBack volume.

System action:

The archive or backup of the FastBack volume can not continue. The next
Volume in in line will be processed. The output of the FastBackMount
command will show the reason for the failure.

User response:

Check the local client error log for the reason for the failure. Issue a
FastBack command for the FastBack volume to determine the reason for the
failure. Refer to the documentation for that message for more
information.

------------------------------------------------------------------------
ANS7916E

Failure initializing FastBack environment.RC=rc



Explanation:

Failure initializing FastBack environment. Can not find
FastBackShell.exe command. The FastBackShell or FastBackMount is not
installed or FastBackShell.exe command is not located in the FastBack
install directory.

System action:

The backup can not continue. The output of the FastBack command will
show the reason for the failure.

User response:

Issue a FastBack command to determine the reason for the failure. Refer
to the documentation for that message for more information. The
FastBackShell and FastBackMount must be installed on the backup proxy
computer.

------------------------------------------------------------------------
ANS7917E

No FastBack snapshots found for input policy, client and volume
combination.



Explanation:

Failure processing fbClientName option.

System action:

The backup cannot continue.

User response:

Check for errors in the FBClientName option value. Refer to the
documentation for the FBClientName option for more information.

------------------------------------------------------------------------
ANS7918E

Failure locating mounted volumes for FastBack client 'vmname' volumes.
Failed with RC=rc



Explanation:

FastBack client volumes can not be found. Volume mount points are not
available on the backup proxy computer.

System action:

The backup of the FastBack client can not continue. The next FastBack
client in the list will be processed. The output of the FastBackMount
command will show the reason for the failure.

User response:

Issue a fastbackshell mount add command for the FastBack client volume
to determine the reason for the failure. Refer to the documentation for
that message for more information.

------------------------------------------------------------------------
ANS7919E

Password for Host host could not be read 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

------------------------------------------------------------------------
ANS7936E

objType objName not found in dump.



Explanation:

IBM Spectrum Protect server could not find the object that is specified
in the FastBack Dump command..

System action:

IBM Spectrum Protect skips the current object.

User response:

Ensure that there is at least one snapshot for this FastBack volume,
client, and policy. Ensure that a correct object is specified as input.

------------------------------------------------------------------------
ANS7937E

No objType found in dump for input objType1 objType2.



Explanation:

IBM Spectrum Protect server found no clients for the specified policy.
IBM Spectrum Protect server found no volumes for the specified FastBack
client.

System action:

IBM Spectrum Protect skips the current object.

User response:

Ensure that there is at least one snapshot for this FastBack volume,
client, and policy. Ensure that a correct object is specified as input.

------------------------------------------------------------------------
ANS7938E

Unable to dismount FastBack volume 'volName'. RC = rc



Explanation:

IBM Spectrum Protect Dismount failed.

System action:



User response:



------------------------------------------------------------------------
ANS7939E

Invalid FastBack volume specification.



Explanation:

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

System action:



User response:

When entering a FastBack volume name, enter at least one FastBack client
name using the "-fbclientname=" option.

------------------------------------------------------------------------
ANS7940W

SUBDIR NO is not valid in this context. SUBDIR will be forced to YES for
FastBack commands.



Explanation:

When using FastBack, SUBDIR is forced to YES to ensure that the whole
volume is processed.

System action:

SUBDIR is forced to YES.

User response:

To avoid this message, do not use SUBDIR NO with the command.

------------------------------------------------------------------------
ANS7941E

FastBack invalid repository name or domain not set in password file
entry for hostname.



Explanation:

IBM Spectrum Protect The FastBack repository name is invalid or the
domain has not been set in the password file when specifying the REP
form of the repository.

System action:

IBM Spectrum Protect

User response:

Issue the command dsmc set password server userid:domain password
-type=fastback.

------------------------------------------------------------------------
ANS7942E

Maximum number of FastBack objName objects exceeded.



Explanation:

IBM Spectrum Protect The maximum number of FastBack objects shown in the
message has been exceeded.

System action:

IBM Spectrum Protect

User response:

Re-run the command with no more than the maximum number of objects
specified.

------------------------------------------------------------------------
ANS7943E

The combination of objName and objName is invalid.



Explanation:

IBM Spectrum Protect The combination of options specified is invalid.

System action:

IBM Spectrum Protect

User response:

Re-run the command with a compatible set of options.

------------------------------------------------------------------------
ANS7944W

The number of FastBack clients specified client is greater than the
number of FastBack clients found client.



Explanation:

IBM Spectrum Protect One or more of the FastBack clients specified was
not found. Look for message ANS7936E specifying the client name.

System action:

IBM Spectrum Protect

User response:

Correct the names of the clients specified.

------------------------------------------------------------------------
ANS7945W

The number of FastBack policies specified policy is greater than the
number of FastBack policies found policy.



Explanation:

IBM Spectrum Protect One or more of the FastBack policies specified was
not found. Look for message ANS7936E specifying the policy name.

System action:

IBM Spectrum Protect

User response:

Correct the names of the policies specified.

------------------------------------------------------------------------
ANS7946E

FastBack shell command timeout.SSH Keys may not be configured for no
password.



Explanation:

IBM Spectrum Protect The FastBack shell command timeout. SSH may not be
configured properly.

System action:

IBM Spectrum Protect

User response:

Correct SSH configuration.

------------------------------------------------------------------------
ANS7947E

The root user .ssh directory was not found. SSH is not configured
properly.



Explanation:

IBM Spectrum Protect SSH is not configured properly for the root user.

System action:

IBM Spectrum Protect

User response:

Correct SSH configuration.

------------------------------------------------------------------------
ANS7948E

The public key for the FastBack server was not found. SSH public keys
are configured properly.



Explanation:

IBM Spectrum Protect The SSH public keys are not configured properly for
the root user.

System action:

IBM Spectrum Protect

User response:

Correct SSH configuration.

------------------------------------------------------------------------
ANS7949E

The connection to FastBack server failed.



Explanation:

IBM Spectrum Protect The connection to FastBack server failed.

System action:

IBM Spectrum Protect

User response:

Insure that the FastBack server on the target machine is runing
properly.

------------------------------------------------------------------------
ANS7950E

The FastBack server is not installed on the target machine.



Explanation:

IBM Spectrum Protect The FastBack server is not installed on the target
machine.

System action:

IBM Spectrum Protect

User response:

Install the FastBack server on the target machine or specify a different
target machiner.

------------------------------------------------------------------------
ANS7951E

The FastBackShell on the target machine returned with the message
errormsg .



Explanation:

IBM Spectrum Protect An error occurred with the command issued to the
FastBackShell on the target machine.

System action:

IBM Spectrum Protect

User response:

Correct the options specified on the commandr.

------------------------------------------------------------------------
ANS7952E

The package package required for FastBack support is not installed.



Explanation:

IBM Spectrum Protect The required package is not installed.

System action:

IBM Spectrum Protect

User response:

Install and configure the required package.

------------------------------------------------------------------------
ANS7953E

The FastBack shell scripts returned an unexpected error error.



Explanation:

IBM Spectrum Protect The FastBack shell scripts returned an unexpected
error.

System action:

IBM Spectrum Protect

User response:

Correct the error.

------------------------------------------------------------------------
ANS7954E

The SSH connection failed. The SSH daemon may not be started or
configured on the target machine



Explanation:

IBM Spectrum Protect Ensure that the SSH daemon is configured correctly.

System action:

IBM Spectrum Protect

User response:

Correct the error.

------------------------------------------------------------------------
ANS7955E

The cygdrive-prefix is set incorrectly.



Explanation:

IBM Spectrum Protect Ensure that cygdrive-prefix is set to / in the ssh
cygwin environment. The command mount -s --change-cygdrive-prefix / can
be use to set the drive prefix correctly.

System action:

IBM Spectrum Protect

User response:

Correct the error.

------------------------------------------------------------------------
ANS7956E

Unable to execute cygwin shell commands. The cygwin environment may be
incorrectly



Explanation:

IBM Spectrum Protect Use ssh to connect to the cygwin shell and ensure
that the cygwin environment and cygdrive are configured correctly.

System action:

IBM Spectrum Protect

User response:

Correct the error.

------------------------------------------------------------------------
ANS7957E

Unable discover the FastBackShell location in the registry



Explanation:

IBM Spectrum Protect Check that the FastBackShell was installed on the
Windows FastBack server machine.

System action:

IBM Spectrum Protect

User response:

Correct the error.

------------------------------------------------------------------------
ANS8000I

Server command: 'command'.



Explanation:

The specified command is being sent to the server. This message is
displayed when the command is generated from a macro or when the client
is running in batch mode.

System action:

The command is sent to the server for processing.

User response:

None.

------------------------------------------------------------------------
ANS8001I

Return code return code value.



Explanation:

The error code shown has been returned from the preceding server
command. This message is preceded by a server message explaining the
reason for the error code.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS8002I

Highest return code was return code value.



Explanation:

At exit from the client, the highest return code encountered during the
session is displayed.

System action:

This value is used as the program exit code.

User response:

None.

------------------------------------------------------------------------
ANS8003I

Process number process ID started.



Explanation:

As a result of the preceding server command, the process whose ID is
shown starts to execute the command. The process can be monitored using
the QUERY PROCESS command.

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS8004W

Your password will expire within daysRemaining day(s).



Explanation:

The password for this id is about to expire.

System action:

Logging on to the IBM Spectrum Protect Server will not be prevented,
however, the id will be locked out once it expires.

User response:

Change the password or contact your IBM Spectrum Protect administrator
to get the password updated.

------------------------------------------------------------------------
ANS8005E

Java Applet failed to load. Please ensure that the Java Java version
Plugin has been installed 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 message displayed.

User response:

Install appropriate plugin for browser in order to use web client.

------------------------------------------------------------------------
ANS8006E

Unable to generate an acceptable password.



Explanation:

An error occurred during a password update attempt using a generated
password.

System action:

The password is not updated on the server.

User response:

Contact your IBM Spectrum Protect administrator.

------------------------------------------------------------------------
ANS8007E

The user is not authorized to perform LDAP authentication.



Explanation:

Your node uses LDAP authentication. Your PASSWORDACCESS option is set to
GENERATE but the current user cannot access the stored password to
perform authentication.

System action:

The operation is stopped.

User response:

Run IBM Spectrum Protect client as root user or set PASSWORDACCESS to
PROMPT.

------------------------------------------------------------------------
ANS8008W

Redirection inside macro whose output is redirected is ignored.



Explanation:

An output redirection symbol has been encountered inside a macro.
However, the output of the macro itself (or a higher level macro) is
already being redirected.

System action:

The redirection request is ignored.

User response:

None.

------------------------------------------------------------------------
ANS8010E

An attempt to backup or archive a file has exceed the maximum number of
retries.



Explanation:

After five unsuccessful attempts to backup or archive a file, the client
will no longer attempt to send the file to the server.

System action:

File skipped.

User response:

Check the console or schedule log for additional information. Retry the
operation at a later time.

------------------------------------------------------------------------
ANS8011W

Rejected server-initiated session with LDAP authentication from peer
name.



Explanation:

For security, the client will not accept server-initiated sessions from
servers that use LDAP authentication.

System action:

The client-server session is not opened, and the schedule is not
executed. The scheduler continues to wait for contact by a server that
uses LOCAL authentication.

User response:

If the client system is supposed to accept scheduled events from the
prompting IBM Spectrum Protect server, either ask the IBM Spectrum
Protect server administrator to configure your node to use LOCAL
authentication, or do not use server-initiated sessions. If the client
system is not supposed to accept scheduled events from the prompting
server, ask the IBM Spectrum Protect server administrator to remove the
client node name from the schedule on the prompting server.

------------------------------------------------------------------------
ANS8012E

Option processing storage exhausted.



Explanation:

During processing of the client options file, the client runs out of
memory.

System action:

The client session is ended.

User response:

Make more memory available and restart the administrative client.

------------------------------------------------------------------------
ANS8013I

Invalid encryption key password



Explanation:

The key you entered does not match the key that was used to encrypt the
file during backup. The file can not be restored unless the matching key
is entered.

System action:

User is prompted for encryption key password.

User response:

Enter the correct encryption key password.

------------------------------------------------------------------------
ANS8014E

Insufficient information to connect to host.



Explanation:

The client options file or command line, or both, do not contain enough
communications information to successfully connect to the server system.
For example, with TCP/IP both the TCPPort number and TCPServer address
are required to make a connection.

System action:

The administrative client session is ended.

User response:

Determine what information is needed to establish a connection for your
communications method and then specify all that information in your
client options file or on the administrative client command line.

------------------------------------------------------------------------
ANS8015E

File 'file spec', error code error code from options processing.



Explanation:

An unknown error code is returned from the routine that processes the
client options file.

System action:

The administrative client session is ended.

User response:

Attempt to determine the error and correct it. If the problem persists,
contact your service representative.

------------------------------------------------------------------------
ANS8016E

Command line parameter parameter number: 'parameter' is too long.



Explanation:

The specified command line parameter exceeds the maximum length for a
command line parameter.

System action:

The administrative client session is ended.

User response:

Reissue the command with a shorter parameter.

------------------------------------------------------------------------
ANS8017E

Command line parameter parameter number: 'parameter' is not valid.



Explanation:

The command line parameter shown is not a valid administrative client
parameter.

System action:

The administrative client session is ended.

User response:

Reissue the command with valid parameters.

------------------------------------------------------------------------
ANS8018E

Administrative command not valid in Console mode.



Explanation:

The Console Mode option has been specified but the client encounters
what appears to be a server command on the command line.

System action:

The administrative client session is ended.

User response:

Reissue the command with no server command.

------------------------------------------------------------------------
ANS8019E

Id and password must be supplied in Batch mode.



Explanation:

A server command has been encountered on the command line, but no
administrator ID or password, or both, are specified.

System action:

The administrative client session is ended.

User response:

Reissue the command and include the -ID and -PASSWORD parameters on the
command line.

------------------------------------------------------------------------
ANS8020E

Unable to open file 'file spec' for output.



Explanation:

The file name specified in the -OUTFILE option 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.

------------------------------------------------------------------------
ANS8021E

Exiting Batch mode session due to output file error.



Explanation:

The file specified in the -OUTFILE parameter cannot be opened for a
session running in Batch mode.

System action:

The administrative client session is ended.

User response:

Reissue the command with a valid output file name or make space
available for the output file.

------------------------------------------------------------------------
ANS8022E

Output will be written only to stdout.



Explanation:

The file specified in the -OUTFILE parameter cannot be opened, so output
is written only to the standard output stream.

System action:

Output that would have been written to the output file is written to the
standard output stream.

User response:

Allow processing to continue or exit the session and correct the file
name.

------------------------------------------------------------------------
ANS8023E

Unable to establish session with server.



Explanation:

The administrative client cannot start a session with the requested
server. This message is preceded by another message that explains the
reason for the error.

System action:

The administrative client session is ended.

User response:

Attempt to correct the error. If the problem persists, contact your
service representative.

------------------------------------------------------------------------
ANS8024E

End of macro after continued command line.



Explanation:

A macro containing a continuation line has been executed, but no more
lines are found in the macro 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.

------------------------------------------------------------------------
ANS8025E

I/O Error reading command input.



Explanation:

The client is unable to read an input command from the terminal.

System action:

The administrative client session is ended.

User response:

Correct the problem on the terminal and retry the administrative
session.

------------------------------------------------------------------------
ANS8026E

Input line longer than maximum of max length characters. Use
continuation.



Explanation:

An input command line is longer than the maximum input line length
allowed.

System action:

The input command is ignored.

User response:

Reissue the command with several lines using continuation characters.

------------------------------------------------------------------------
ANS8027E

Unterminated comment in command.



Explanation:

An input command contains an opening comment mark but no closing comment
mark.

System action:

The input command is ignored.

User response:

Reissue the command with matching comment marks.

------------------------------------------------------------------------
ANS8028E

Command longer than maximum of max length characters.



Explanation:

An input command longer than the maximum command length allowed has been
entered.

System action:

The input command is ignored.

User response:

Reissue the command with fewer characters. This could mean replacing
series of repeating blanks with a single blank.

------------------------------------------------------------------------
ANS8029E

Macro processing terminated.



Explanation:

An error occurs during processing of a macro because the -ITEMCOMMIT
option is not specified on the command line. Processing of this macro
and any higher level macro is terminated.

System action:

All current macro processing ends.

User response:

Specify the -ITEMCOMMIT option on the command line to ensure that the
server commits each command in the macro individually.

------------------------------------------------------------------------
ANS8030E

Substituted command longer than maximum of max length characters.



Explanation:

After variable substitution, an input command is longer than the maximum
command length allowed.

System action:

The input command is ignored.

User response:

Reissue the command with fewer characters. This may require replacing a
series of repeating blanks with a single blank.

------------------------------------------------------------------------
ANS8031E

Missing name of macro to execute.



Explanation:

A macro command is encountered that does not contain a macro name.

System action:

The command is ignored.

User response:

Reissue the macro command with a macro file name.

------------------------------------------------------------------------
ANS8032E

Could not allocate storage to process macro 'file spec'.



Explanation:

The client cannot allocate enough memory to process the macro shown.

System action:

The macro is ignored and an error is returned.

User response:

Make more memory available to the client and retry the macro command.

------------------------------------------------------------------------
ANS8033E

LDAP authentication is not supported by Web client.



Explanation:

The id you entered uses LDAP authentication. LDAP authentication is not
supported by Web client.

System action:

Login is unsuccessful.

User response:

Use an id with LOCAL authentication.

------------------------------------------------------------------------
ANS8034E

Your administrator ID is not recognized by this server.



Explanation:

The administrator ID entered is not known to the requested server.

System action:

The administrative session terminates.

User response:

Ensure that you are using a registered administrative ID for the server
to which you are connecting.

------------------------------------------------------------------------
ANS8036E

Administrative command not valid in Mount mode.



Explanation:

The Mount Mode option has been specified but the client encounters what
appears to be a server command on the command line.

System action:

The administrative client session is ended.

User response:

Reissue the command with no server command.

------------------------------------------------------------------------
ANS8037E

Missing name for redirection file.



Explanation:

A command is entered that contains an output redirection symbol but no
output file name.

System action:

The command is ignored and an error is returned.

User response:

Reissue the command with an output file name.

------------------------------------------------------------------------
ANS8038E

Unable to open file 'file spec' for redirection.



Explanation:

A command has been entered that specifies an output redirection file,
but the file cannot be opened.

System action:

The command is ignored and an error is returned.

User response:

Reissue the command with a valid output file name or make space
available for the output file.

------------------------------------------------------------------------
ANS8041E

The server connection has been lost and cannot be re-established.



Explanation:

During an administrative session, the client discovers that the
connection with the server has been severed; an attempt to reestablish
the connection fails.

System action:

The client session is ended.

User response:

Determine the cause of the failure; then try to restart the session at a
later time. If the problem persists, contact your service
representative.

------------------------------------------------------------------------
ANS8045E

Communications error.



Explanation:

An unexpected communications error occurs during an administrative
session.

System action:

The client session is ended.

User response:

Verify that communications are active between the client and server
machines. Server outages, processor outages, and communication
controller outages can cause this error.

------------------------------------------------------------------------
ANS8046E

The client connection with the server has ended due to an unexpected
error.



Explanation:

The error log might contain other messages related to this error.

System action:

The client session ends.

User response:

Check the communication link between the client and server to ensure
that it is operational. Examine the client error log for additional
messages related to this error.

------------------------------------------------------------------------
ANS8047E

The client connection with the server has ended due to a communications
buffer overflow.



Explanation:

The error log might contain other messages related to this error.

System action:

The client session ends.

User response:

Try the operation again. Check the communication link between the client
and server to ensure that it is operational. Examine the client error
log for additional messages related to this error.

------------------------------------------------------------------------
ANS8048W

Warning! Performing image restore of the Linux file system 'src' to an
alternate destination 'dest' is not recommended as this may result in
duplicate UUIDs leading to failed mounts after a successful restore.



Explanation:

Performing an image restore of a Linux file system to an alternate
destination may result in duplicate UUID leading to failed mounts after
a successful restore. On Linux, some file systems use UUID to identify
themselves. If you took an image backup of such volume and restored it
to a different location, you will have two volumes with the same UUID.
If you use UUID to define your file systems in /etc/fstab, be aware that
IBM Spectrum Protect may be unable to mount the restored file system
correctly. To avoid such situation, restore the image to its original
location.

System action:

Processing continues.

User response:

If it is not possible or not desirable to avoid performing an image
restore to an alternate destination, change the UUID of either the
original or restored volume. Refer to your Linux documentation for
instructions on how to do this. You may also need to edit your
/etc/fstab manually to allow the original, the restored or both volumes
to mount.

------------------------------------------------------------------------
ANS8049E

A connection with the server cannot be established due to a
communications time-out.



Explanation:

The error log might contain other messages related to this error.

System action:

The client session ends.

User response:

Check the communication link between the client and server to ensure
that it is operational. Examine the client error log for additional
messages related to this error.

------------------------------------------------------------------------
ANS8050E

The IBM Spectrum Protect server is not accepting administrative sessions
on the client port. You must use the port number designated for
administrative sessions.



Explanation:

The IBM Spectrum Protect server is configured to not allow
administrative sessions on the client TCP/IP port. A different port
number has been designated for use by administrative sessions.

System action:

The administrative session is not established.

User response:

Use the TCPADMINPORT client option to specify the TCP/IP port number
that the IBM Spectrum Protect server uses for administrative sessions.
See your IBM Spectrum Protect server administrator if you do not know
the correct port number.

------------------------------------------------------------------------
ANS8052E

Unable to decrypt file 'filespace namepath-namefile-name'....Please try
to restore this file individually



Explanation:

File could not be decrypted and restored.

System action:

File is not restored.

User response:

Restore the file separately.

------------------------------------------------------------------------
ANS8053E

The network cannot be accessed.



Explanation:

The error log might contain other messages related to this error.

System action:

The client session ends.

User response:

Check the communication link between the client and server to ensure it
is operational. Examine the client error log for additional messages
related to this error. Try the operation again.

------------------------------------------------------------------------
ANS8054E

No memory available to service request.



Explanation:

Sufficient server memory is not available.

System action:

The client session is ended.

User response:

Retry the administrative session. If the problem persists, contact your
service representative.

------------------------------------------------------------------------
ANS8055E

The server has insufficient resources to perform the operation.



Explanation:

The server ran out of resources. A lack of storage or other problem
condition does not allow any new activity. The server activity log might
contain additional information about this problem.

System action:

The client session ends.

User response:

The IBM Spectrum Protect administrator should examine the IBM Spectrum
Protect server activity log to determine the source of the resource
constraints. Try the operation again when the server is under less load.

------------------------------------------------------------------------
ANS8056E

Your administrator ID is locked.



Explanation:

The administrative ID entered has been locked by a system administrator
and cannot be used.

System action:

The client session is ended.

User response:

Contact your system administrator to unlock your ID.

------------------------------------------------------------------------
ANS8057E

The requested language files are not available.



Explanation:

The NLS repository for the language specified is not available.

System action:

The client session is ended.

User response:

Use a different language or obtain a copy of the NLS repository for the
language desired.

------------------------------------------------------------------------
ANS8058E

The specified path is a Linux Btrfs subvolume and is not valid for image
backup.



Explanation:

Linux Btrfs subvolumes are not supported for image backup.

System action:

The image backup operation is not performed.

User response:

Try the operation again using a valid Linux Btrfs file system.

------------------------------------------------------------------------
ANS8060E

Error validating file 'VHDX file name'



Explanation:

IBM Spectrum Protect cannot locate the file or the file format is not
valid.

System action:

The backup operation does not start.

User response:

Try the operation again. If the problem continues, check the error log
file for information about how to resolve this issue.

------------------------------------------------------------------------
ANS8061E

Session Rejected: The server does not allow a signon as a Unicode
enabled administrative client



Explanation:

The administrative client is unable to establish a connection to the
server because of a unicode enabling mismatch between server and client.

System action:

The client session is ended.

User response:

Register a new administrator from a different administrative client or
the server console, and signon with the new administrator ID.

------------------------------------------------------------------------
ANS8062E

Client-to-Client communication is not allowed to take place when IBM
Spectrum Protect Server authentication is turned off.



Explanation:

Client-to-Client communication requires IBM Spectrum Protect
Authentication to be enabled.

System action:

Processing stops.

User response:

Turn IBM Spectrum Protect Server authentication on using the Set
AUthentication ON command.

------------------------------------------------------------------------
ANS8063E

The remote IBM Spectrum Protect Client Acceptor associated with Node
'name' could not authenticate with the IBM Spectrum Protect Server.



Explanation:

Some IBM Spectrum Protect Client operations require the Backup/Archive
Client to contact Clients on remote machines. The remote machine in
question cannot authenticate with the IBM Spectrum Protect Server.

System action:

Processing stops.

User response:

On the remote machine, create a new IBM Spectrum Protect password for
the Client Acceptor or verify that the current password is still valid
before retrying the operation.

------------------------------------------------------------------------
ANS8064E

Communication timeout. Reissue the command.



Explanation:

The connection to the server is ended because of a communication timeout
from the server.

System action:

The server does not process the command.

User response:

Reissue the command. If necessary, increase the values of IDLETIMEOUT
and COMMTIMEOUT options in the server options file.

------------------------------------------------------------------------
ANS8103W

A command was not successful. command : command IBM Spectrum Protect
function name : function-name error output : error-output return code :
return code IBM Spectrum Protect file : file-name (line-number)



Explanation:

IBM Spectrum Protect client called an external program that failed.

System action:

Depending on the circumstances, the failure may or may not prevent
further processing.

User response:

See addition information in the error log. Use the information provided
in this message for troubleshooting or when talking with IBM Spectrum
Protect support.

------------------------------------------------------------------------
ANS8104W

Cannot determine EFS status of the file system 'file-system name',
errno='errnor number', processing data normally.



Explanation:

IBM Spectrum Protect cannot determine EFS status on the specified
filesystem. No EFS specific processing will take place for files on this
filesystem. If EFS is indeed enabled on the filesystem, all accessaible
files will be backedup in cleartext.

System action:

The filesystem will be processed as a regular filesystem.

User response:

Contact your system administrator to determine the cause of the error
reported in the message.

------------------------------------------------------------------------
ANS8105W

Unable to remove snapshot for volume 'filespace-name'.



Explanation:

IBM Spectrum Protect client was unable to remove the snapshot used for
image backup.

System action:

Processing continues.

User response:

See additional information in the error log. Use lvdisplay command to
view the active snapshots and lvremove command to remove the snapshot
manually.

------------------------------------------------------------------------
ANS8106E

Support for multiple IBM Spectrum Protect servers is enabled on this
node. The server name must be specified for this command.



Explanation:

When a node is enabled to support multiple IBM Spectrum Protect servers,
the command must specify a valid IBM Spectrum Protect server name.

System action:

Processing stopped.

User response:

Specify a valid server name for this command.

------------------------------------------------------------------------
ANS8107I

The -server='option-value' option value is ignored. The reconciliation
will proceed with the default server default-server.



Explanation:

The -server option is valid only in a multiple-server environment, and
must be used only with the two-way, orphan-check reconciliation mode.

System action:

Processing continues.

User response:

Use the -server option only with the two-way, orphan-check
reconciliation mode.

------------------------------------------------------------------------
ANS8201E

Windows Hyper-V incremental backups require Windows 2012 or later. On
Windows Server 2016 or later, the virtual machine version must be
greater than 5.



Explanation:

IBM Spectrum Protect can only perform incremental backups of Windows
Hyper-V on Windows operating systems of Windows Server 2012 and later.
If running on Windows Server 2016 or later than the virtual machine
version must be greater than 5.

System action:

The incremental backup operation was stopped.

User response:

To access incremental backups for Windows Hyper-V, upgrade the operating
system to Windows Server 2012 or later. On Windows Server 2016 and
later, the virtual machine version must be greater than 5 to support
Microsoft Hyper-V Resilient Change Tracking (RCT).

------------------------------------------------------------------------
ANS8503I

No matching option found for pattern: 'pattern'.



Explanation:

You specified a pattern which does not match the name of any supported
option.

System action:

This message is the only response to your query.

User response:

Specify a different pattern or omit the pattern to display all options.

------------------------------------------------------------------------
ANS8563E

Recall mode has an invalid value: invalidValue.



Explanation:

The recall mode you try to enable on the system is not existing.

System action:

None.

User response:

Check the value of the recall option.

------------------------------------------------------------------------
ANS8565W

ProgramName: list of recall IDs not found in queue. These recalls are
already finished:



Explanation:

The program is not able to find the recall IDs and is not able to delete
these processes.

System action:

None.

User response:

Check that recall IDs exist and are correct.

------------------------------------------------------------------------
ANS8778E

A browser program cannot be found or cannot be started. An error
occurred executing the command.command Verify that a browser is
installed and works correctly on your local machine.



Explanation:

A browser program cannot be found, so it is not possible to access the
IBM Spectrum Protect Web site and online documentation.

System action:

IBM Spectrum Protect continues to process user requests.

User response:

For the Windows platform, the default system browser is used. Verify
that a browser is installed on your machine.

------------------------------------------------------------------------
ANS8779E

A browser program cannot be found or cannot be started. One of the
following browsers is required: browser-list Verify that one of these
browsers is installed and works correctly on your local machine.



Explanation:

A browser program cannot be found, so it is not possible to access the
IBM Spectrum Protect Web site and online documentation.

System action:

IBM Spectrum Protect continues to process user requests.

User response:

For UNIX platforms, a list of supported browsers is provided in the
README. Install the required browser to access the IBM Spectrum Protect
Web sites and online documentation.

------------------------------------------------------------------------
ANS8780E

A browser program cannot be found or cannot be started. Check the
'file-name' file on your local machine for more information.



Explanation:

A browser program cannot be found, so it is not possible to access the
Web site or online documentation.

System action:

IBM Spectrum Protect continues to process user requests.

User response:

Install a browser to access the Web site or online documentation.

------------------------------------------------------------------------
ANS8809E

The LD_LIBRARY_PATH is either not set or is set incorrectly. Ensure that
the LD_LIBRARY_PATH environment variable contains the installation
directory path name.



Explanation:

The LD_LIBRARY_PATH must be set and it must contain the installation
directory path.

System action:

The VMware backup or restore operation fails.

User response:

Set the LD_LIBRARY_PATH and ensure that it contains the Backup/Archive
client installation directory.

------------------------------------------------------------------------
ANS8810E

The LD_LIBRARY_PATH is either not set or is set incorrectly. Ensure that
the LD_LIBRARY_PATH environment variable contains the installation
directory.



Explanation:

The LD_LIBRARY_PATH must be set and it must contain the installation
directory path.

System action:

The VMware backup or restore operation fails.

User response:

Set the LD_LIBRARY_PATH and ensure that it contains the Backup/Archive
client installation directory.

------------------------------------------------------------------------
ANS8811E

VMware operations can not be run when the hardware plugin product
TIVsm-BAhdw is installed and loaded. Please either uninstall the
hardware product TIVsm-BAhdw, or set the option DONTLOAD PIHDW in the
options file to prevent the hardware plugin from being loaded.



Explanation:

VMware operations are incompatible with the hardware plugin product
libraries.

System action:

The VMware backup or restore operation fails.

User response:

Uninstall the hardware product product TIVsm-BAhdw, or set the option
DONTLOAD PIHDW to prevent the hardware plugin from being loaded.

------------------------------------------------------------------------
ANS8818E

An error occurred trying to apply your changes. Your changes have not
been applied to the system. Contact your system administrator.



Explanation:

An error occurred trying to apply your changes.

System action:

User changes are not applied.

User response:

Contact your system administrator.

------------------------------------------------------------------------
ANS8819E

The following trace flag(s) are not valid: trace-flag-list. Correct them
before continuing.



Explanation:

One or more of the trace flags are not valid.

System action:

Prompts the user to correct the trace flags.

User response:

Correct the wrong trace flags.

------------------------------------------------------------------------
ANS8830W

Different server name stanzas (HSM-stanza and BA-stanza) for
file-system-name file system for space management and backup-archive.



Explanation:

The server name stanzas you specified for the space management (HSM)
client and the backup-archive (BA) client are different. The inline
backup and stub restore features will be unavailable for the file
system.

System action:

Processing continues.

User response:

If you want to allow inline backup and stub restore for the file system,
the MIGRATESERVER and DEFAULTSERVER options must specify the same
SERVERNAME stanza in dsm.sys. You may also choose to supply a server
stanza name using the SERVERNAME option in dsm.opt or on the command
line. In either case the stanza name must match the stanza specified in
the MIGRATESERVER option.

------------------------------------------------------------------------
ANS8939E

An unexpected error occurred trying to filter the directory tree.
rc=return-code



Explanation:

The filter was not applied to the directory tree.

System action:

The directory tree is not filtered.

User response:

Contact your system administrator for further assistance.

------------------------------------------------------------------------
ANS8946E

RPC call failed.



Explanation:

Unable to connect receiver recall daemon.

System action:

Processing stopped.

User response:

System is not operating correctly or recall daemons are not started.

------------------------------------------------------------------------
ANS8956E

Port port which is specified by the HSMRPCPORT option is already in use



Explanation:

The port specified by the HSMRPCPORT option is in use by a different
process.

System action:

Processing stopped.

User response:

Update the HSMRPCPORT with new available port number and restart HSM
daemons

------------------------------------------------------------------------
ANS8957E

Start of RPC Server process failed



Explanation:

dsmrecalld can not start RPC server.

System action:

Processing stopped.

User response:

Error detail can be found in system log.

------------------------------------------------------------------------
ANS9005W

program name: invalid 'parameter name' value: value (must be in [minimum
value..maximum value]).



Explanation:

The program found an invalid parameter in the space management
configuration of a filesystem.

System action:

The paramter value was rejected.

User response:

In case you tried to set the specified value manually, choose a value
from the specified range instead. If the value is read from a file
system's space management configuration file (located at
[fs]/.SpaceMan/hsmfsconfig.xml), edit the file accordingly. The name of
the filesystem can be determined from a subsequent error message.

------------------------------------------------------------------------
ANS9007W

program name: invalid 'parameter name' value: value (must be in [minimum
value..maximum value]).



Explanation:

The program found an invalid parameter in the space management
configuration of a filesystem.

System action:

The paramter value was rejected.

User response:

In case you tried to set the specified value manually, choose a value
from the specified range instead. If the value is read from a file
system's space management configuration file (located at
[fs]/.SpaceMan/hsmfsconfig.xml), edit the file accordingly. The name of
the filesystem can be determined from a subsequent error message.

------------------------------------------------------------------------
ANS9008W

Compression is enabled. Recall mode for file file-name cannot be set to
partial.



Explanation:

IBM Spectrum Protect can only set file attributes to a uncompressed
migrated file. This file has been migrated with compression enabled.

System action:

IBM Spectrum Protect does not set the file attributes.

User response:

Recall the file to state resident disable compression and migrate the
file again. Retry the operation.

------------------------------------------------------------------------
ANS9009E

program name: found invalid space management configuration for
'filesystem'.



Explanation:

The program found an invalid space management configuration for the
given filesystem.

System action:

The space management configuration was rejected for the given filesystem
. When updating an existing configuration, invalid configurations to set
are ignored. When a persistent configuration file is invalid, the
filesystem will appear to not have space management enabled.

User response:

In case you tried to update space management for this filesystem
manually, enter a valid configuration instead. In case the persistent
configuration file is invalid, edit the file accordingly; alternatively,
you can add space management explicitly (which will remove / overwrite
the existing configuration). The reason for the configuration can be
determined from a preceding error message. The filesystem's space
management configuration file is located at
'filesystem'/.SpaceMan/hsmfsconfig.xml.

------------------------------------------------------------------------
ANS9010E

program name: could not parse space management configuration file
'configuration file' for filesystem.



Explanation:

The space management configuration file for the given filesystem is
present but its content appears to have invalid format.

System action:

The configuration was rejected. The filesystem will appear to not have
space management enabled.

User response:

Check the given space management configuration file; it is supposed to
contain a well-formed XML document with a root element named
'HsmFsConfig'. To create a new configuration file, you can simply add
space management to this filesystem.

------------------------------------------------------------------------
ANS9011E

program name: could not write space management configuration file
'configuration file' for filesystem.



Explanation:

IBM Spectrum Protect could not write and save the space management
configuration file for the given filesystem.

System action:

IBM Spectrum Protect did not save the space management configuration
information. If you tried to add space management for this filesystem,
it was not added. If you tried to update the space managment
configuration, it was probably not updated. If an existing configuration
file in old format was read successfully, but could not be converted to
XML format, space management will be active for this filesystem with the
configuration from the old file.

User response:

Determine if there is any reason why the given file cannot be written.

------------------------------------------------------------------------
ANS9012E

error-program: Command must be run by root user.



Explanation:

IBM Spectrum Protect requires that a root user perform this operation.

System action:

IBM Spectrum Protect terminates the operation.

User response:

Change to root user, and then retry the operation.

------------------------------------------------------------------------
ANS9016E

Cannot get space management migration status for path.



Explanation:

An error occurred while trying to get the space management migration
status. Either the permissions for the status file are not set
correctly, or the status file is damaged.

System action:

IBM Spectrum Protect terminates the operation.

User response:

The root user should check the permissions of the status file, or
contact the service representative.

------------------------------------------------------------------------
ANS9017W

error-program: Minimum number of recall daemons min-dsmrecalld cannot be
greater than maximum number of recall daemons max-dsmrecalld; defaulting
to minimum min-dsmrecalld and maximum max-dsmrecalld.



Explanation:

A minimum number of recall daemons has been entered that is greater than
the maximum number of recall daemons.

System action:

IBM Spectrum Protect uses defaults instead of the values specified in
the client system options file (dsm.sys).

User response:

Correct the MINRECALLDAEMONS and MAXRECALLDAEMONS options in the client
system options file and retry the operation.

------------------------------------------------------------------------
ANS9020E

A session could not be established with a IBM Spectrum Protect server or
client agent. The return code is tsm-error;.



Explanation:

An issue prevented the client from making a connection with the IBM
Spectrum Protect server. Additional detail is not available to include
with this message. However, additional messages are likely to be
reported in the IBM Spectrum Protect error log.

System action:

Processing stops.

User response:

Check the error log for additional messages. Refer to those messages to
determine how to resolve any reported issues. If the IBM Spectrum
Protect-error is -50, there is a communication failure. Typical causes
of this error include misconfiguration of the server TCP/IP address or
port. Verify the configuration and that the client system network is
connected. Verify that a firewall does not prevent access to the IBM
Spectrum Protect server. Finally, verify that the IBM Spectrum Protect
server is running and accepting connections on the expected port.

------------------------------------------------------------------------
ANS9021E

error-program Unknown recall daemon (pid process-ID) terminated
abnormally, status: status.



Explanation:

A recall daemon stops abnormally.

System action:

IBM Spectrum Protect terminates the operation.

User response:

Try the operation again. If the problem persists, send the core file to
IBM technical support for analysis.

------------------------------------------------------------------------
ANS9022E

error-program Recall daemon (pid process-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 problem persists, send the core file to
IBM technical support for analysis.

------------------------------------------------------------------------
ANS9024E

Starting with this release all candidate processing is done internally
by the IBM Spectrum Protect monitor daemon. Thus -c is no longer a valid
option for dsmreconcile.



Explanation:

The command line options -c and -Candidates are no longer valid for
dsmreconcile as all candidates processing is now performed by
dsmmonitord.

System action:

IBM Spectrum Protect detected an invalid option. dsmreconcile is
exiting.

User response:

Don't use options -c and -Candidates with dsmreconcile anymore.

------------------------------------------------------------------------
ANS9025E

The Data Protection for WebSphere plug-in version and the backup-archive
client version do not match. Please upgrade your Data Protection for
WebSphere plug-in.



Explanation:

The release and version of the Data Protection for WebSphere plug-in is
downlevel from the release and version of the Backup-Archive Client.

System action:

None

User response:

Upgrade Data Protection for WebSphere to the proper release and version.

------------------------------------------------------------------------
ANS9028E

program name: could not acquire lock for filesystem.



Explanation:

Prior to modifying a space management configuration file, it is required
to lock the file in order to 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 determine the process holding the lock.

------------------------------------------------------------------------
ANS9029E

The WebSphere server is running, but the server must be shut down for a
restore operation. Shut down the WebSphere server and try the restore
operation again.



Explanation:

The WebSphere server must be brought down to perform a restore.

System action:

The restore operation fails.

User response:

Shut down the WebSphere server and try the restore operation again.

------------------------------------------------------------------------
ANS9030W

Cannot set conflicting attributes to file file-name.



Explanation:

IBM Spectrum Protect cannot set the file attributes because the
requested attributes are in conflict with one another.

System action:

IBM Spectrum Protect does not set the file attributes.

User response:

Retry this operation with attributes that do not conflict with each
other. This error also appears if you try to set partial recall mode for
an executable file.

------------------------------------------------------------------------
ANS9031W

File file-name is not a migrated file.



Explanation:

IBM Spectrum Protect can only set file attributes to a migrated file.
This file has not been migrated.

System action:

IBM Spectrum Protect does not set the file attributes.

User response:

Migrate this file, and then retry the operation.

------------------------------------------------------------------------
ANS9032W

File file-name is not in an HSM managed file system.



Explanation:

IBM Spectrum Protect detects that the file is not in an HSM managed file
system, and therefore, it cannot perform the operation requested.

System action:

IBM Spectrum Protect does not set the file attributes.

User response:

Add space management to the file system, migrate the file, and then
retry the operation.

------------------------------------------------------------------------
ANS9034E

The restore operation did not complete, due to a change in the original
WebSphere environment.



Explanation:

The data must be restored to the same environment that it was backed up
from. This includes items such as cell name, node name, and the location
where WebSphere is installed.

System action:

The restore operation does not complete.

User response:

Perform the restore procedure in the DP for WebSphere book.

------------------------------------------------------------------------
ANS9036W

program-name: migrated file(s) are missing on server for number stub
file(s). Look in 'file-spec' for file names.



Explanation:

IBM Spectrum Protect cannot find the migrated file(s) on the server.

System action:

Processing continues.

User response:

Look in the path mentioned in the message for the file name. Also ensure
that you are working with the correct server for this file.

------------------------------------------------------------------------
ANS9050I

program-name: One or more specified options are not valid.



Explanation:

IBM Spectrum Protect The specified options are not valid. No option was
changed.

System action:

Processing continues without changed options.

User response:

Verify the specified options and correct the command line options for
the command.

------------------------------------------------------------------------
ANS9051I

program-name: The options were successfully changed.



Explanation:

IBM Spectrum Protect Update of options was successful.

System action:

Processing continues with changed options.

User response:

Continue normal processing.

------------------------------------------------------------------------
ANS9054E

The plug-in was not found.



Explanation:

None.

System action:

None

User response:

Run "dsmc show plugins" at the command prompt to see the available
plug-ins on the system.

------------------------------------------------------------------------
ANS9057W

error-program: cannot get space information for file-system: error.



Explanation:

IBM Spectrum Protect cannot get the space information for the file
system.

System action:

Processing continues.

User response:

Verify that space management has been added to the file system.

------------------------------------------------------------------------
ANS9059E

error-program: process cannot detach to become a daemon.



Explanation:

IBM Spectrum Protect process cannot detach itself to become a daemon.

System action:

IBM Spectrum Protect cannot start the daemon as requested. IBM Spectrum
Protect stops.

User response:

Retry the operation.

------------------------------------------------------------------------
ANS9060W

error-program: cannot get and increase limit of open files.



Explanation:

IBM Spectrum Protect either cannot get the limit of the number of open
files, or cannot increase the limit of the number of open files.

System action:

IBM Spectrum Protect cannot increase the number of open files, and was
not able to complete the operation.

User response:

Free some file space by ending some processes or removing some files,
and retry the operation.

------------------------------------------------------------------------
ANS9062E

File 'filename' has changed during the backup.



Explanation:

A file changed during the backup. Check the dsmerror.log file for a list
of files that have changed.

System action:

The backup fails.

User response:

Try the backup again.

------------------------------------------------------------------------
ANS9063E

error-program: file system file-system is out of inodes.



Explanation:

IBM Spectrum Protect cannot get space for the file system because the
file system is out of inodes.

System action:

IBM Spectrum Protect cannot get space via migration.

User response:

Remove some files to make more inodes available and retry.

------------------------------------------------------------------------
ANS9064E

error-program: Cannot fork a new process: error.



Explanation:

IBM Spectrum Protect cannot fork a new process that is needed. If the
operating system errno is EAGAIN, then the limit on the total number of
processes running on the system or by a single user has been exceeded,
or the system does not have the resources necessary to create another
process. If the errno is ENOMEM, then there is not enough memory to
create the process.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

Depending on the error code (errno), either allocate additional virtual
memory (swap space) or increase the operating system process limit. Then
restart the HSM daemons or reboot the system.

------------------------------------------------------------------------
ANS9065E

File 'filename' or file 'filename2' has been added or removed during the
backup.



Explanation:

A file was added or removed during the backup.

System action:

The backup fails.

User response:

Try the backup again.

------------------------------------------------------------------------
ANS9067W

error-program: error updating dsmmigfstab file for file-system.



Explanation:

IBM Spectrum Protect found an error in updating the dsmmigfstab file for
this file system.

System action:

IBM Spectrum Protect does not update the dsmmigfstab file.

User response:

See the preceding error message and correct the error if possible. Then,
retry the operation. If problem persists, contact your system
administrator.

------------------------------------------------------------------------
ANS9068I

program-name: dsmmigfstab file updated for file system file-system.



Explanation:

IBM Spectrum Protect successfully updated the dsmmigfstab file for the
file system.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9069I

program-name: all file systems are reactivated to previous states.



Explanation:

IBM Spectrum Protect has reactivated all file systems managed by HSM to
their previous states before the global deactivation.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9070I

program-name: space management is now deactivated for all HSM file
systems.



Explanation:

IBM Spectrum Protect has deactivated space management for all file
systems listed in the dsmmigfstab file.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9071W

program-name: error reactivating space management for all HSM file
systems.



Explanation:

IBM Spectrum Protect found an error in trying to reactivate space
management.

System action:

IBM Spectrum Protect does not reactivate space management for HSM file
systems.

User response:

Make sure space management is installed correctly and retry the
operation.

------------------------------------------------------------------------
ANS9072W

error-program: error deactivating space management for all FSM file
systems.



Explanation:

IBM Spectrum Protect found an error in trying to deactivate space
management.

System action:

IBM Spectrum Protect does not deactivate space management for FSM file
systems.

User response:

Make sure space management is installed correctly and retry the
operation.

------------------------------------------------------------------------
ANS9073W

program-name: error deactivating space management for file system
file-system.



Explanation:

IBM Spectrum Protect found an error in trying to deactivate the file
system.

System action:

IBM Spectrum Protect does not deactivate space management for the file
system.

User response:

Make sure space management is installed correctly and retry the
operation.

------------------------------------------------------------------------
ANS9074I

program-name: space management functions have been locally deactivated
for file system file-system.



Explanation:

IBM Spectrum Protect has locally deactivated space management functions
like migration, recall and reconciliation for the file system.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9075W

program-name: error reactivating space management for file system
file-system.



Explanation:

IBM Spectrum Protect found an error in trying to reactivate space
management for the file system.

System action:

IBM Spectrum Protect does not reactivate space management for the file
system.

User response:

Verify that the specified file system is mounted and that HSM is enabled
for this file system. Then try the operation again. If the problem
persists, contact IBM technical support for additional assistance.
Provide the /etc/filesystems (or equivalent file) and the output from
the mount and dsmdf commands.

------------------------------------------------------------------------
ANS9076I

program-name: space management functions have been locally reactivated
for file system file-system.



Explanation:

IBM Spectrum Protect has locally reactivated space management functions
like migration, recall and reconciliation for the file system. Please,
note however that the space management might still be globally
deactivated.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9077I

program-name: removed space management from file system file-system.



Explanation:

IBM Spectrum Protect removed space management. The file system is now a
native file system.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9078W

Space management is not removed from file system file-system.



Explanation:

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

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

System action:

IBM Spectrum Protect is unable to complete the requested operation.

User response:

Refer to the immediately preceding error message and retry the
operation.

------------------------------------------------------------------------
ANS9079W

program-name: no migrated files matching search criteria found.



Explanation:

IBM Spectrum Protect did not find any migrated files matching the search
criteria.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

Retry the operation with a different search criteria.

------------------------------------------------------------------------
ANS9080E

program-name: not enough space in file system or storage pool to recall
all migrated files.



Explanation:

IBM Spectrum Protect detects there is not enough space in the file
system to hold all the migrated files if all are recalled. If you are
using GPFS storage pools, each pool needs to have enough space to recall
it's files.

System action:

IBM Spectrum Protect does not attempt to recall all the migrated files.

User response:

Make room in the file system by increasing the file system size or
removing some files. Retry the operation.

------------------------------------------------------------------------
ANS9081W

program-name: orphaned stub file(s) detected in file system file-system.



Explanation:

IBM Spectrum Protect detected one or more orphaned stub files. Either
the migration server was changed in the client system options file after
the file was migrated, or the migration server database is damaged.

System action:

IBM Spectrum Protect does not attempt to remove space management from
the file system.

User response:

Determine the cause of orphaned stub files. Switch to the correct
migration server and recall the migrated files. Retry the operation.

------------------------------------------------------------------------
ANS9082W

program-name: error encountered while reconciling file system
file-system.



Explanation:

IBM Spectrum Protect encountered an error performing reconciliation on
the file system.

System action:

Processing continues.

User response:

Refer to other messages displayed or messages in the log to correct the
problem. Then retry the operation.

------------------------------------------------------------------------
ANS9083W

program-name: cannot deactivate space management on file system
file-system.



Explanation:

IBM Spectrum Protect cannot deactivate space management on the file
system.

System action:

Processing continues.

User response:

Correct the error if possible and retry the operation.

------------------------------------------------------------------------
ANS9084E

program-name: file-system is not managed or not locally managed by space
management.



Explanation:

There is no entry for the file system in the dsmmigfstab file or the
file system is managed by another node.

System action:

IBM Spectrum Protect will not perform space management functions on this
file system.

User response:

Add space management to the file system, if appropriate, and then retry
the operation. If the file system is not locally managed, retry the
operation on the node managing the file system.

------------------------------------------------------------------------
ANS9085E

program-name: file system file-system is not managed by space
management.



Explanation:

There is no entry for the file system in the dsmmigfstab file.

System action:

IBM Spectrum Protect will not perform space management functions on this
file system.

User response:

Add space management to the file system, if appropriate, and then retry
the operation.

------------------------------------------------------------------------
ANS9086E

program-name: A DMAPI error occured adding space management to file
system file-system, it is possible DMAPI is disabled on this file
system. The system set the error code: errno = errno-value



Explanation:

IBM Spectrum Protect encountered an error and cannot add space
management to the file system.

System action:

The Space management cannot be added to file system.

User response:

Verify that DMAPI is enabled for this file system and retry the
operation.

------------------------------------------------------------------------
ANS9087I

Space management is successfully added to file system file-system.



Explanation:

IBM Spectrum Protect has added space management to the file system, and
will now monitor its space usage. You can also perform other space
management operations on this file system.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9088W

program-name: space management is already active for file system
filesystem.



Explanation:

This message is issued when trying to add space management to a
filesystem with space management already activated. It is not possible
to add space management for a filesystem that already has space
management activated.

System action:

The action was cancelled.

User response:

In case you wanted to update the filesystem's space management
configuration instead, use the appropriate update command.

------------------------------------------------------------------------
ANS9089E

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 was queried to the time that all the data was sent to the IBM
Spectrum Protect server. Check the dsmerror.log file for a list of files
that were added, removed, or changed.

System action:

The backup fails.

User response:

Try the backup again.

------------------------------------------------------------------------
ANS9090E

program-name: file-system is not a valid file system name.



Explanation:

IBM Spectrum Protect received an invalid file system name. The file
system is not mounted, or is not mounted correctly.

System action:

Processing continues.

User response:

Correct the file system name, and retry the operation.

------------------------------------------------------------------------
ANS9091E

The WebSphere 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 was queried to the time that all the data was sent to the IBM
Spectrum Protect server. Check the dsmerror.log file for a list of files
that were added, removed, or changed.

System action:

The backup fails.

User response:

Try the backup again. Do not install new WebSphere applications or
change the WebSphere configuration while in the backup window.

------------------------------------------------------------------------
ANS9092E

An operation is attempted that is only supported for an primary server.
However the server 'option-value' is the failover server.



Explanation:

Only primary server is allowed to use for reconciliation and
dsmmigundelete.

System action:

Processing stops.

User response:

Specify the primary server.

------------------------------------------------------------------------
ANS9093W

program-name: cannot update migration candidates list file-name.



Explanation:

IBM Spectrum Protect cannot update the migration candidates list because
not enough memory is available to create a temporary file.

System action:

Processing stops.

User response:

Make some memory available by ending some processes, and then retry the
operation.

------------------------------------------------------------------------
ANS9094W

program-name: no candidates found in file system file-system.



Explanation:

IBM Spectrum Protect found no files eligible for migration in the file
system after running dsmreconcile.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9098E

program-name: space management does not support file system file-system.



Explanation:

The space management 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 support other types of file systems (AFS, NFS,
etc).

System action:

Processing of the file system stopped.

User response:

None.

------------------------------------------------------------------------
ANS9099E

program-name: space management is not active for file system
file-system.



Explanation:

IBM Spectrum Protect found the file system did not have space management
activated.

System action:

Processing of that file system stopped.

User response:

Reactivate space management for the file system.

------------------------------------------------------------------------
ANS9100E

Unable to open file 'filename' for output.



Explanation:

The file name specified cannot be opened.

System action:

Make sure that user has access to write to specified file, or use
different file name.

User response:

Output will not be saved. Please specify different file or check
permissions on chose file.

------------------------------------------------------------------------
ANS9101E

Migrated files matching 'file-name' could not be found.



Explanation:

File name for search pattern can not be found in the IBM Spectrum
Protect server database as a migrated file.

System action:

No query result.

User response:

Verify that the search patter is correct.

------------------------------------------------------------------------
ANS9117E

Virtual machine 'VM_name' contains one or more of the following
unsupported special characters special_characters_list.



Explanation:

The specified virtual machine name contains characters that are not
supported for virtual machine backup and restore operations. The
following characters are not supported in names of restored virtual
machines: ":;'\"*?,<>/\\|"

System action:

The backup or restore for the specified virtual machine failed.

User response:

Rename the virtual machine without using unsupported special characters.

------------------------------------------------------------------------
ANS9121I

Activate completed.



Explanation:

A Domino activate databases operation was completed.

System action:

IBM Spectrum Protect activated the databases.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS9126E

program-name: cannot determine whether space management is active or
inactive for file-system due to error: error.



Explanation:

The program 'program-name' indicated in the message text was unable to
obtain statistics for file system 'file-system'. Therefore the program
cannot determine whether space management is activated, deactivated, or
globally deactivated on that file system. The message text includes a
description of the Unix errno error that occurred while trying to get
the state of space management.

System action:

IBM Spectrum Protect stops the operation.

User response:

Verify that the file system is mounted and accessible. Using the
appropriate tools for that file system, check whether there are any I/O
or other integrity errors on that file system. Then try the operation
again. If the operation fails, then a system reboot might clear the
error condition. If, after taking these actions the problem persists,
contact IBM technical support for assistance.

------------------------------------------------------------------------
ANS9128I

Inactivate logs completed.



Explanation:

A Domino inactivate log operation was completed.

System action:

IBM Spectrum Protect inactivated the log.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS9130E

The virtual machine name contains only whitespace characters.



Explanation:

The virtual machine name that was specified contains only whitespace
characters. A name consisting of only whitespace characters is not
supported for virtual machine backup and restore operations.

System action:

The backup or restore for the specified virtual machine failed.

User response:

Rename the virtual machine using valid characters. Try the operation
again.

------------------------------------------------------------------------
ANS9133E

program name: space management already active for filesystem.



Explanation:

This message is issued when trying to add space management to a
filesystem with space management already activated.

System action:

The action was cancelled.

User response:

Check the filesystem's space management configuration and consider
updating it in case it does not match your needs. It is not possible to
add space management for a filesystem that already has space management
activated.

------------------------------------------------------------------------
ANS9134E

program name: space management not active for filesystem.



Explanation:

The program requested the space management configuration for a file
system where space management is not active.

System action:

The action was cancelled.

User response:

In case you entered the filesystem specification, check for correct
spelling. It is not possible to perform space management actions on a
filesystem with space management not activated.

------------------------------------------------------------------------
ANS9135E

program name: space management for filesystem not controlled by the
local node.



Explanation:

The program requested the space management configuration for a file
system where space management is active, but not controlled by the local
node. In cluster environments, some space management actions are allowed
from the owner node only.

System action:

The action was cancelled.

User response:

Determine the controller node for this filesystem and retry.

------------------------------------------------------------------------
ANS9136E

program name: could not remove configuration file for filesystem.



Explanation:

During removal of space management for the given filesystem, this
configuration file could not be removed.

System action:

Space management could not be deactivated for this filesystem.

User response:

Determine the reason why the file could not be removed and retry.

------------------------------------------------------------------------
ANS9137I

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 files requires that the file is in
premigration state.

------------------------------------------------------------------------
ANS9140E

The migration options premigration and stub cannot be combined.



Explanation:

The migration option premigration and stub are mutual exclusive. Both
options end in different results for the same file.

System action:

Command ends without changes to the file.

User response:

Use the migration options premigration and stub in different instances
of the command.

------------------------------------------------------------------------
ANS9145E

Virtual machine will not be backed up because it has an empty name.



Explanation:

The specified virtual machine name is empty. This is not supported for
virtual machine backup and restore operations.

System action:

The backup for the specified virtual machine fails.

User response:

Rename the virtual machine so that its name contains supported
characters.

------------------------------------------------------------------------
ANS9146E

The dsmrecalld daemon process running on node local-node cannot reach
the counterpart on node remote-node. RPC error code: rpcStat-value,
reason: rpcStat-explanation



Explanation:

IBM Spectrum Protect dsmrecalld executable running on the local node was
unable to connect to the remote counterpart executable via RPC.

System action:

Processing of the current operation is stopped.

User response:

Login to the indicated remote node and ensure that the dsmrecalld daemon
processes are running. If the daemon processes are running but the
warning continues, make sure that the appropriate RPC services are up
and running on both nodes. To do so: - on Linux, run 'service portmap
status' or 'service rpcbind status' or 'systemctl status rpcbind'
command depending on the Linux distribution in use; - on AIX, run 'lssrc
-s portmap' command. If the RPC error reason is "Program not registered"
or the RPC error persists even upon the RPC service restart, restart all
the HSM daemons via 'dsmmigfs restart' command on both nodes.

------------------------------------------------------------------------
ANS9147E

program-name: cannot read file-spec: error.



Explanation:

IBM Spectrum Protect cannot read this file.

System action:

IBM Spectrum Protect cannot fully complete the requested operation.

User response:

An error occurred reading an HSM managed file system status file. Verify
that the file system is mounted and enabled for HSM and is actually
managed by HSM and then try the operation again. If the problem
persists, contact IBM technical support for further assistance. Provide
the output from the mount, dsmdf and ls -l [file system name] commands.

------------------------------------------------------------------------
ANS9148E

program-name: cannot find mount point for file system file-system.



Explanation:

IBM Spectrum Protect cannot find file system mount point.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

The specified file system is not currently mounted. Mount the file
system and try the operation again.

------------------------------------------------------------------------
ANS9150I

Archive log completed.



Explanation:

A Domino archive log operation was completed.

System action:

IBM Spectrum Protect archived the log.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS9151E

An unexpected program error was encountered . IBM Spectrum Protect
function name : function-name IBM Spectrum Protect function :
function-desc IBM Spectrum Protect return code : TSM-rc IBM Spectrum
Protect file : file-name (line-number)



Explanation:

None.

System action:

Processing stops.

User response:

Check error log for more information. Contact the IBM Spectrum Protect
administrator with the information provided in this message.

------------------------------------------------------------------------
ANS9152E

program-name: cannot deactivate space management for whole system:
error.



Explanation:

Space management cannot be deactivated for the whole machine.

System action:

IBM Spectrum Protect cannot deactivate space management support.

User response:

The HSM global status is inaccessible, possibly due to concurrent
access. Try the operation again. If the problem continues, examine the
output of the shell command ps -aef as well as the contents of
/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. If a pid is stored in
this file and it does correspond to a running process, remove the
dmiFSGlobalState.pid file and retry the operation. If the problem
persists, reboot the system and repeat the appropriate analysis for your
file system type.

------------------------------------------------------------------------
ANS9153E

program-name: cannot reactivate space management for whole system:
error.



Explanation:

Space management cannot be reactivated for the whole machine.

System action:

IBM Spectrum Protect cannot reactivate space management support.

User response:

The HSM global status is inaccessible, possibly due to concurrent
access. Try the operation again. If the problem continues, examine the
output of the shell command ps -aef as well as the contents of
/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. If a pid is stored in
this file and it does correspond to a running process, remove the
dmiFSGlobalState.pid file and retry the operation. If the problem
persists, reboot the system and repeat the appropriate analysis for your
file system type.

------------------------------------------------------------------------
ANS9154E

program-name: cannot deactivate space management for file system
file-system: error.



Explanation:

Space management cannot be deactivated for the file system.

System action:

IBM Spectrum Protect unable to deactivate space management support for
the file system.

User response:

The HSM file system status is inaccessible, possibly due to concurrent
access. Try the operation again. If the problem continues verify that
the file system is mounted and that HSM is enabled on the file system
with the Unix shell commands mount and dsmdf. If the problem persists,
reboot the system and try the operation again.

------------------------------------------------------------------------
ANS9155E

program-name: cannot reactivate space management for file system
file-system: error.



Explanation:

Space management cannot be reactivated for the file system.

System action:

IBM Spectrum Protect cannot reactivate space management support to the
file system.

User response:

The HSM file system status is inaccessible, possibly due to concurrent
access. Try the operation again. If the problem continues, verify that
the file system is mounted and that HSM is enabled on the file system
with the Unix shell commands mount and dsmdf. If the problem persists,
reboot the system and try the operation again.

------------------------------------------------------------------------
ANS9156I

Rollforward completed.



Explanation:

A Domino DB2 rollforward operation was completed.

System action:

IBM Spectrum Protect rollforward the Domino DB2 database log.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS9159E

program-name: unable to create temporary file.



Explanation:

IBM Spectrum Protect cannot create a temporary file.

System action:

IBM Spectrum Protect cannot complete its operation.

User response:

Check with the Unix mount shell command that /tmp and /etc exist as
separate file systems on your system. Use the df command to check
whether they are full. Create additional space by deleting files or
increasing the file system size.

------------------------------------------------------------------------
ANS9160E

program-name: cannot write to temporary file or status filefile-spec:
error.



Explanation:

IBM Spectrum Protect cannot complete writing to the temporary file.

System action:

IBM Spectrum Protect cannot complete the requested operation.

User response:

The Unix error code may provide guidance as to why the write failed. Use
the Unix mount and df shell commands to verify that the associated file
system is mounted and has space available. If this message resulted from
a shell command, mount the file system and create additional space if
necessary, then retry the operation. If the message did not result from
a shell command, restart the daemons. If the problem persists, reboot
the system.

------------------------------------------------------------------------
ANS9161E

Invalid backupset file or device name entered.



Explanation:

The backupset file or device name specified does not contain a valid
backupset.

System action:

Processing stopped.

User response:

Specify a file name or device that contains a valid backupset and retry
the operation.

------------------------------------------------------------------------
ANS9162W

Object: 'dir-name' is skipped for recall: It is a directory.



Explanation:

The object is a directory. Space management does not recall directories.

System action:

IBM Spectrum Protect does not recall this object because it is a
directory.

User response:

None.

------------------------------------------------------------------------
ANS9163W

program-name: Could not acquire the recall daemon session id.



Explanation:

Could not set up the event disposition for the file system, because the
recall daemon session could not be acquired. It seems the recall daemon
is not running. Recall requests will not be handled, which means the IBM
Spectrum Protect client for space management can't react to recall
requests for this file system.

System action:

IBM Spectrum Protect could not set up the recall event handling. The
recall event handling is not enabled for this filesystem.

User response:

Start or restart the recall daemon.

------------------------------------------------------------------------
ANS9164W

program-name: Could not acquire the monitor daemon session id.



Explanation:

Could not set up the event disposition for the file system, because the
monitor daemon session could not be acquired. It seems the monitor
daemon is not running. Thus the thresholds for file system usage will
not be monitored and the NOSPACE event will not be handled, which means
the file system may run out of space.

System action:

IBM Spectrum Protect could not set up the NOSPACE event handling. The
NOSPACE event handling is not enabled for this filesystem.

User response:

Start or restart the monitor daemon.

------------------------------------------------------------------------
ANS9165E

program-name cannot open directory directory-spec due to the following
error: error.



Explanation:

The directory indicated in the message text cannot be opened. The
message text includes a description of the error that occurred.

System action:

The requested operation is not completed.

User response:

Try to correct the error condition that is indicated in the message
text, then try the operation again. If the problem persists, contact IBM
technical support for further assistance.

------------------------------------------------------------------------
ANS9166I

A 'backup type' backup version backup date 'datetime' is not consistent
with local repository and has been deleted from the server (object
name='filespace namepath-namefile-name', ID = 'object-id:object-id').



Explanation:

The specified backup instance of the named object is not valid with
local repository contents. This could happen if local repository is
modified or got corrupted on the client system. This backup can not be
restored, therefore it will be deleted on the server.

System action:

The specified backup object will be deleted on the server. Processing
will continue.

User response:

None.

------------------------------------------------------------------------
ANS9167W

The client cache for adaptive subfile backup is corrupt and cannot be
used.



Explanation:

The adaptive subfile cache has become corrupt. While the backup client
can detect the corruption, the reason for the corruption cannot be
determined.

System action:

The IBM Spectrum Protect client will proceed with standard selective or
incremental backup. The cache will be rebuilt so that subsequent backups
will use the adaptive subfile technique.

User response:

If the problem persists, contact IBM technical support for assistance.
Be prepared to provide the client error log, which will contain
additional messages that might be useful for support to help identify
the problem.

------------------------------------------------------------------------
ANS9169E

program-name: cannot create directory directory-spec, reason.



Explanation:

IBM Spectrum Protect cannot create this directory.

System action:

IBM Spectrum Protect does not create this directory.

User response:

Verify that this directory does not already exist, and that its parent
directory has proper permissions.

------------------------------------------------------------------------
ANS9170E

program-name: file-system is not a mounted local file system.



Explanation:

IBM Spectrum Protect did not find that this file system is properly
mounted.

System action:

IBM Spectrum Protect ignores the file system.

User response:

Verify that this file system is local and mounted and activated
properly.

------------------------------------------------------------------------
ANS9171E

An error internal to IBM Spectrum Protect has occurred. The following
string is too long: error.



Explanation:

None.

System action:

The requested operation does not complete.

User response:

A system reboot might clear up the problem, after which the operation
should be tried again. If the problem persists, contact IBM technical
support for further assistance.

------------------------------------------------------------------------
ANS9174I

A backup delete completed.



Explanation:

A Backup delete was completed.

System action:

IBM Spectrum Protect deleted backup files.

------------------------------------------------------------------------
ANS9177W

All data events for remote recalls running on node: 'cluster node ID',
hostname: 'cluster node hostname' are going to be aborted.



Explanation:

The remote node is not responding, so all DMAPI data events which are
currently being processed on this remote node should be aborted. This
warning is likely caused by an RPC communication issue between the local
node and the specified remote node.

System action:

The dsmrecalld distributor process is going to abort all data events (if
any) which are currently being processed on the specified remote node.

User response:

Ensure that the network and host connection are configured correctly.
Then, retry the recall operation.

------------------------------------------------------------------------
ANS9178E

program-name cannot open file file-spec due to the following error:
error.



Explanation:

The program indicated in the message text was unable to open the
specified file. The message text also includes a description of the
error that occurred when it tried to open the file.

System action:

The requested operation does not complete.

User response:

Verify that the file system on which the file resides is mounted, then
try the operation again. A system reboot might clear up the problem. If
the problem persists, contact IBM technical support for further
assistance.

------------------------------------------------------------------------
ANS9179W

The operation completed successfully. However, some error occurred on
creation of the required vApps list.



Explanation:

One or more of the items included in the vApps specification were not
found. This can be caused by a change in the vCD organizations
configuration or a user mistake in the provided vApp spec.

System action:

The operation completes successfully

User response:

Check the local client error log for a reason for the failure and check
the command specification. Correct any issues and execute the command
again.

------------------------------------------------------------------------
ANS9180W

An entry in the password file could not be decrypted.



Explanation:

The password failed decryption validation.

System action:

The password in the password file will be ignored. You will be prompted
for the password, unless the process is running in the background, such
as in scheduling mode.

User response:

Enter the password when prompted.

------------------------------------------------------------------------
ANS9184E

program-name cannot allocate memory due to the following error: error.



Explanation:

A memory allocation error occurred. The message text includes a
description of the error that occurred.

System action:

The requested operation does not complete.

User response:

Try the operation again. If the problem occurs in an HSM daemon, restart
the daemon, then try the operation again. If the problem continues to
occur, use your operating system's administrative tools to check virtual
memory (swap space) on your system, and increase it if necessary. Check
whether an application is consuming available virtual memory. A system
reboot might also clear up the problem. If the problem persists, contact
IBM technical support for further assistance.

------------------------------------------------------------------------
ANS9186E

program-name: cannot open mounted file system file-system: error.



Explanation:

IBM Spectrum Protect cannot open mounted file system.

System action:

IBM Spectrum Protect ignores the file system.

User response:

Verify that this file system is mounted and activated properly.

------------------------------------------------------------------------
ANS9201W

LAN-free path failed.



Explanation:

A LAN-free connection could not be made.

System action:

The system will connect to the server without using the LAN-free path.

User response:

Verify your LAN-free setup.

------------------------------------------------------------------------
ANS9203E

ENABLELANFREE can not be used when HSM is installed.



Explanation:

The IBM Spectrum 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

System action:

An invalid option is detected and processing stops.

User response:

Remove the ENABLELANFREE option from the system option file.
ENABLELANFREE can only be used when HSM is not installed.

------------------------------------------------------------------------
ANS9220E

The name of the virtual machine 'VM_name' contains 'VM_name_length'
characters. This length exceeds the maximum allowed by the hypervisor
'hypervisor_name' which is 'max_hypervisor_VM_name_length' characters.



Explanation:

The length of the name of the virtual machine exceeds the maximum length
allowed by the hypervisor.

System action:

The restore of the specified virtual machine failed.

User response:

Rename the virtual machine with a name that does not exceed the maximum
length set by the hypervisor. Try the restore operation again.

------------------------------------------------------------------------
ANS9240W

Could not acquire the serial number of disk 'disk-name' at LUN LUN-id.



Explanation:

IBM Spectrum Protect was not able to determine the serial number of the
specified disk. The disk may not support SCSI inquiries of the Vital
Product Data on page 0x80.

System action:

Server-free data movement will not be possible for data residing on the
specified disk.

User response:

None.

------------------------------------------------------------------------
ANS9249E

File 'file-namefile-namefile-name' accessed during migration. File
skipped.



Explanation:

The specified file-name was not migrated because the file was accessed
by another process during the attempt to migrate it.

System action:

IBM Spectrum Protect left the file resident.

User response:

If you want the file migrated, stop the process which is accessing the
file and retry the migration.

------------------------------------------------------------------------
ANS9250I

File system 'file-system' reconciliation completed.



Explanation:

IBM Spectrum Protect has finished reconciling the file system.

System action:

Processing continues.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS9251E

ProgramName: Cannot parse command-line options correctly.



Explanation:

An internal program error occurred trying to parse the command-line
arguments.

System action:

The program is not able to process the request.

User response:

Use the -h or -help option to see what options are allowed on the
command-line, then retry the request.

------------------------------------------------------------------------
ANS9252I

Value of environment variable: envVar.



Explanation:

None.

System action:

This message is informational.

User response:

None.

------------------------------------------------------------------------
ANS9255I

An empty status file will be generated.



Explanation:

The HSM status file is missing or can not be opened. An empty status
file will be created.

System action:

File data migration will continue to work normally.

User response:

Please run dsmreconcile to create a complete status file.

------------------------------------------------------------------------
ANS9256E

File 'file-namefile-namefile-name' is currently opened by another
process.



Explanation:

The file is locked by a migration or recall operation. A file can be the
object of only one recall process or one recall operation at a time.

System action:

The file is skipped.

User response:

If this error is not a result of a parallel file migration or recall
operation, then this error might be due to the previous cancelled
migration or recall operation. In this case, restart the dsmrecalld
daemon and try the operation again.

------------------------------------------------------------------------
ANS9263W

You cannot restore both active and inactive versions of System State.



Explanation:

Restoring an active copy and inactive copy of System State is not
allowed.

System action:

No processing takes place.

User response:

Select either the active copy or the inactive copy to perform restore
operation.

------------------------------------------------------------------------
ANS9264E

Incremental backup of Virtual Machine 'vmname' failed with RC rc



Explanation:

The incremental backup of virtual machine volumes failed.

System action:

The backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS9267E

program-name: File system file-system has exceeded its quota.



Explanation:

IBM Spectrum Protect detects that the file system has exceeded its
quota. No more data can be migrated out of this file system.

System action:

IBM Spectrum Protect will not migrate files from this file system.

User response:

Recall some files, or ask the system administrator to increase the quota
for this file system.

------------------------------------------------------------------------
ANS9278E

Failure processing vmList option. RC=rc



Explanation:

Failure processing vmList option.

System action:

The backup can not continue.

User response:

Check for errors in the vmList option value. Refer to the documentation
for the vmList option for more information.

------------------------------------------------------------------------
ANS9279E

Failure locating Virtual Machine 'vmname' volumes. Failed with RC=rc



Explanation:

Virtual machine volumes can not found. Volume mount points are not
available on Backup Proxy machine.

System action:

The backup of the virtual machine can not continue. The next virtual
machine in the vmlist will be processed. The output of the vcbMounter
command will show the reason for the failure.

User response:

Issue a vcbMounter command for the virtual machine to determine the
reason for the failure. Refer to the documentation for that message for
more information.

------------------------------------------------------------------------
ANS9280E

'vmname' option must be set when running this operation.



Explanation:

A required option for the command is missing.

System action:

The operation can not continue.

User response:

Set the missing option using the Preference Editor or the command line.

------------------------------------------------------------------------
ANS9283E

No virtual machines have been associated with the Schedule Tag
'schedule'.



Explanation:

The command cannot execute because no virtual machines were found using
the provided schedule name. This error can also be caused by incorrect
settings for the 'Excluded' tag.

System action:

Processing stopped.

User response:

Try the operation again. Specify a schedule name that matches a relevant
schedule.

------------------------------------------------------------------------
ANS9287E

Invalid or unsupported device.



Explanation:

The logical volume device is either invalid or unsupported. Refer to the
documentation for device type support for image backup.

System action:

The logical volume operation is not performed.

User response:

For image backup source or image restore destination, specify a device
of one of the supported types.

------------------------------------------------------------------------
ANS9288W

File: file-name of logical size file-logical-size and allocated size
file-allocated-size is too small to qualify for migration.



Explanation:

To be eligible for migration, a file must satisfy all of the following
size criteria: - The file logical size is larger than the value of the
stubsize option. - The space that a file occupies (the allocated size)
is at least as great as the value of the minmigfilesize option.

System action:

IBM Spectrum Protect does not migrate this file because migration does
not free additional space.

User response:

Verify that the settings of the stubsize option and the minmigfilesize
option are appropriate for your migration requirements.

------------------------------------------------------------------------
ANS9289W

Object: 'dir-name' is skipped for migration: It is a directory.



Explanation:

The object is a directory. Space management does not migrate
directories.

System action:

IBM Spectrum Protect does not migrate this object because it is a
directory.

User response:

None.

------------------------------------------------------------------------
ANS9290W

File: file-name is skipped for migration: The file type is either
unknown or unsupported.



Explanation:

The file either cannot be read, is not a regular file, or its type is
unknown to the HSM client. The HSM client migrates only regular files
and does not migrate directories, symbolic links, and special files.

System action:

IBM Spectrum Protect does not migrate this file.

User response:

None.

------------------------------------------------------------------------
ANS9291E

program-name: A conflicting space management program is already running
in the file-system file system. Re-run this program later in this file
system.



Explanation:

IBM Spectrum Protect detected another program running in the file system
that cannot run at the same time as the program your tried to initiate.
The following programs cannot run at the same time for a file system:

   dsmreconcile
   dsmautomig
   dsmmigfs remove.

Also, dsmmigfs remove cannot run while a migration process is running in
the file system.

System action:

IBM Spectrum Protect will not run the program at this time.

User response:

Try running the program later.

------------------------------------------------------------------------
ANS9292E

program-name: Cannot access lock file lock-file/lock-filelock-file:
error



Explanation:

IBM Spectrum Protect cannot access a lock file due to an error. The lock
file provides serialization of certain programs to prevent conflicting
processes from running at the same time.

System action:

IBM Spectrum Protect will not run the program at this time.

User response:

Check the permissions on the directories leading up to the lock file and
also the permissions on the program executable.

------------------------------------------------------------------------
ANS9293E

The space management cannot access ERRORPROG error-program: error



Explanation:

IBM Spectrum Protect encountered an error trying to access the program
specified with the ERRORPROG option in your client system options file
(dsm.sys). This message will appear only the first time this error
occurs.

System action:

IBM Spectrum Protect cannot send a severe error message to the specified
error message program.

User response:

Check to make sure the program exists and that it accepts standard input
when run. It is usually best if ERRORPROG specifies the fully qualified
file name of the program.

------------------------------------------------------------------------
ANS9294I

No files matching 'file-name' were found.



Explanation:

You entered a search pattern or file name that cannot be found in the
local file system.

System action:

Processing stopped.

User response:

Ensure that your search pattern is correct, or specify a new search
string.

------------------------------------------------------------------------
ANS9296W

Performing image backup of the entire volume for volume name. The
IMAGEGAPSIZE option and used block image backup is not supported for
non-JFS2 file systems on AIX.



Explanation:

None.

System action:

The entire volume is backed up.

User response:

Refer to the client manual for additional information regarding the
IMAGEGAPSIZE option and used block image backup.

------------------------------------------------------------------------
ANS9297W

File file-name is skipped for migration: No backup copy found.



Explanation:

A management class is assigned to the file with the attribute
MIGREQUIRESBKUP set to YES. This option requires that there exists a
current backup copy of the file before migration. However, there is no
backup copy found on the migration server. This file is not migrated.
Note: IBM Spectrum Protect checks only the migration server for a backup
copy. If the migration server and backup server are different servers,
IBM Spectrum Protect does not find a backup copy of the file.

System action:

The file is skipped.

User response:

Back up this file on the migration server, or assign a management class
to this file that does not require a current backup copy. Try the
operation again.

------------------------------------------------------------------------
ANS9298W

File file-name is skipped for migration: Backup copy found is not
current.



Explanation:

A management class is assigned to the file with the attribute
MIGREQUIRESBKUP set to YES. This option requires that there exists a
current backup copy of the file before migration. However, the backup
copy found on the migration server is an old version. This file is not
migrated. Note: IBM Spectrum Protect checks only the migration server
for a backup copy. If the migration server and backup server are
different servers, there must be a valid backup copy of the file on the
migration server.

System action:

The file is skipped.

User response:

Back up the current file on the migration server, or assign a management
class to this file that does not require a current backup copy. Retry
the operation.

------------------------------------------------------------------------
ANS9299I

Cannot get the number of migrated files for file system file-system.



Explanation:

Failed to get the number of migrated files on the file system. The
number is stored in the status file for the file system.

System action:

If you are removing space management from the file system, processing
stops. Space management is not removed.

User response:

Run reconciliation to reconcile the file system. Retry operation.

------------------------------------------------------------------------
ANS9300I

Migrated files found in file system file-system. Check for any error
encountered during recall.



Explanation:

Remove space management failed because there are migrated files in the
file system. IBM Spectrum Protect was unable to recall any files, or
some of the migrated files may have failed during a recall operation.

System action:

IBM Spectrum Protect remove processing stops.

User response:

Check for error messages that occurred during the recall process,
correct any problems, and retry the remove process.

------------------------------------------------------------------------
ANS9301E

Full VM backup of Virtual Machine 'vmname' failed with RC rc



Explanation:

The Full VM backup of virtual machine failed.

System action:

The full backup of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS9302E

The Restore VM command does not support VMBACKUPTYPE=FILE data. VM File
level restore must be run from inside the virtual machine or with the
'asnodename' option.



Explanation:

The Restore VM function not supported for file level data.

System action:

The system does not process your requested action.

User response:

Virtual machine File level restore must be run from inside the virtual
machine or with the asnodename option. To process a full virtual machine
restore, issue the command with VMBACKUPTYPE=FULLVM.

------------------------------------------------------------------------
ANS9303E

Full VM restore of Virtual Machine 'vmname' failed with RC rc



Explanation:

The Full VM restore of virtual machine failed.

System action:

The full restore of the virtual machine finished with failures. The next
virtual machine in the vmlist will be processed. The reason for the
failure is written to the local client error log.

User response:

Check the local client error log for reason for the failure.

------------------------------------------------------------------------
ANS9304E

VMware Converter tool not installed on system.



Explanation:

VMware Converter tool install could not be detected on system.

System action:

The full virtual machine image files have been restored successfully at
the specified location.

User response:

No further action is necessary. The full virtual machine images files
can be used by various tools. VMware Converter tool can be installed on
system.

------------------------------------------------------------------------
ANS9305E

An invalid Hyper-V VM name 'string' was entered.



Explanation:

You entered a Hyper-V VM name that contains incorrect characters or
contains wildcard characters.

System action:

Processing stopped.

User response:

Enter a correct Hyper-V VM name.

------------------------------------------------------------------------
ANS9306E

An invalid Hyper-V VM list 'string' was entered.



Explanation:

You entered a Hyper-V VM list that contains incorrect characters or
contains wildcard characters.

System action:

Processing stopped.

User response:

Enter a correct Hyper-V VM list.

------------------------------------------------------------------------
ANS9307E

No Hyper-V VM name or VMList entered



Explanation:

No Hyper-V VM name or VMList parameter was specified.

System action:

Processing stopped.

User response:

Specify a correct Hyper-V VM name or VMList parameter.

------------------------------------------------------------------------
ANS9308E

No match found for the Hyper-V VM name or VMList 'string' entered



Explanation:

No match found for the Hyper-V VM name or VMList parameter entered.

System action:

Processing stopped.

User response:

Specify a correct Hyper-V VM name or VMList parameter.

------------------------------------------------------------------------
ANS9309E

Pick option specified but also a value for the Hyper-V VM name or VMList
'string' entered



Explanation:

You cannot specify the -pick option and also include a Hyper-V VM name
or VMList parameter.

System action:

Processing stopped.

User response:

Specify the -pick option without a Hyper-V VM name or VMList parameter.

------------------------------------------------------------------------
ANS9311E

No Hyper-V VMs exist on the IBM Spectrum Protect server



Explanation:

No filespaces representing a Hyper-V Virtual Machine currently exist on
the IBM Spectrum Protect server.

System action:

Processing stopped.

User response:

You must successfully backup a Hyper-V Virtual Machine before using this
command.

------------------------------------------------------------------------
ANS9312S

program-name: Cannot change owner/group on file: file-name: error



Explanation:

IBM Spectrum Protect cannot change the ownership or group, or both for
the specified file. This change is necessary for space management to run
properly.

System action:

Processing stops.

User response:

Ensure that directory permissions allow the file owner or group to be
changed. Reissue the command.

------------------------------------------------------------------------
ANS9313E

program-name: The TMP directory is full.



Explanation:

The TMP directory from the operating system is full.

System action:

Process stops.

User response:

Delete some files in the TMP directory and retry the operation.

------------------------------------------------------------------------
ANS9316T

File system 'file-system' undelete completed.



Explanation:

IBM Spectrum Protect has finished undeleting the file system.

System action:

Processing continues.

User response:

Continue with normal operations.

------------------------------------------------------------------------
ANS9330E

The virtual machine that was specified on the string command could not
be found or was excluded from the operation.



Explanation:

The command cannot complete because the virtual machine could not be
found or was excluded from the operation.

System action:

Processing stopped.

User response:

Try the operation again. Specify a correct VM name or DOMAIN option.
This error can also be caused by incorrect settings for the VMHOST,
VMHOSTCLUSTER, VMFOLDER, VMDATASTORE, -VM options, or the 'Excluded'
tag. The VMHOST option value must be specified as an IP address or as a
server name that is in fully qualified domain name (FQDN) format. The
host name that you specify must match the host name as it is displayed
in the vCenter server in the Host and Clusters view. This host name
could can be the fully qualified host name (FQDN), the shortened domain
name, or the host IP address.

------------------------------------------------------------------------
ANS9331W

VMware vCenter or ESX Server userid and password for VMC Host <host> VMC
Userid <userid> could not be read from encrypted pwd file.



Explanation:

VMware vCenter or ESX Server userid and password could not be read from
encrypted password file.

System action:

Processing stops.

User response:

Use dsmc SET PASSWORD -type=VM 'vCenter hostname' 'userid' 'password' to
save encrypted password.

------------------------------------------------------------------------
ANS9332E

VMware vCenter or ESX Server userid and password not set. Use dsmc SET
PASSWORD -type=VM 'vCenter hostname' 'userid' 'password' to save
encrypted password.



Explanation:

VMware vCenter or ESX Server userid and password could not be read from
encrypted password file.

System action:

Processing stops.

User response:

Use dsmc SET PASSWORD -type=VM 'vCenter hostname' 'userid' 'password' to
save encrypted password.

------------------------------------------------------------------------
ANS9333E

Unable to re-create 'file-name' as a stub file due to Unix-system-call()
failure; errno: error; reason: 'error-reason'.



Explanation:

IBM Spectrum Protect was unable to re-create the specified file as a
stub due to an error.

System action:

The processing continues with the next file.

User response:

Please, look into the dsmerror.log for further error details. If the
affected file path doesn't exist, restore it from your backup (if any)
or re-create it manually, then re-try the operation. Make sure that the
specified file system is IBM Spectrum Protect space managed, writable
and in consistent state.

------------------------------------------------------------------------
ANS9334E

Wrong alias 'alias-name' received from the server.



Explanation:

IBM Spectrum Protect could not build a valid pathname for a migrated
file due to the invalid alias received from the server.

System action:

The processing continues with the next file.

User response:

If possible, perform either an orphan check reconcile or an inline
incremental backup of the initial file, so that the alias is updated on
the server. Then, retry the operation. Otherwise, contact IBM Spectrum
Protect support for further investigation and problem resolution.

------------------------------------------------------------------------
ANS9347W

Warning:'domain-keyword' specified on Domain will be ignored when
connecting to VMware ESX/ESXi host. Connect to VMware vCenter to process
this domain.



Explanation:

None.

System action:

Domain keyword is ignored.

User response:

Connect to VMware vCenter to process this domain.

------------------------------------------------------------------------
ANS9350E

Backup operation failed due to volume mixture. Please refer to
explanation section for additional information.



Explanation:

IBM Spectrum Protect failed to create the backup because of the mixture
of volumes was detected. Some volumes selected meet the requirements for
importing snapshots only when needed and some do not. This situation
occurs when a backup operation is requested and the "Import VSS
snapshots Only When Needed" feature is enabled and not all the volumes
involved in the backup operation are managed by a VSS Hardware Provider
that supports transportable snapshots. Additionally the situation can
also occur in a clustered environment during a backup operation, when
not all the volumes involved in the backup operation are managed by a
VSS Hardware Provider that supports transportable snapshots.

System action:

processing stops.

User response:

Try the operation again by splitting the backup operation. Ensure that
all the volumes involved in the backup operation are either managed by a
Hardware Provider that supports transportable snapshots or that all the
volumes involved in the operation do not support transportable
snapshots. Additionally you may also turn off the "Import VSS snapshots
Only When Needed" feature to allow the backup to allow the mixure.

------------------------------------------------------------------------
ANS9351E

Data was not available on server and was skipped.



Explanation:

The data to be restored is not available on the server, so it will not
be restored.

System action:

The data is skipped, and the restore processing continues with the next
object to be restored.

User response:

Contact your IBM Spectrum Protect administrator.

------------------------------------------------------------------------
ANS9352E

SAN was chosen as the transport for at least one of the disks in the
operation, but the SAN policy is not OnlineAll for this datamover. SAN
cannot be used unless the SAN policy is OnlineAll.



Explanation:

SAN was chosen as the transport because either the default transport
setting was used, or it was specified in the VMVSTORTRANSPORT option. In
order to use SAN as the transport mode, the SAN policy must be set to
OnlineAll.

System action:

Restore processing stops.

User response:

Set the SAN policy to OnlineAll, or set VMVSTORTRANSPORT to something
other than SAN, such as NBD. Then try the restore operation again.

------------------------------------------------------------------------
ANS9354E

The node or owner name 'node' specified in the SET ACCESS command
exceeds the maximum allowed length (64).



Explanation:

An invalid node or owner name has been entered in the SET ACCESS
command.

System action:

Processing stops.

User response:

Enter the SET ACCESS command using the correct node or owner name.

------------------------------------------------------------------------
ANS9355E

VMware vStorage VI Web Service API reported error message: vstor-api-msg



Explanation:

The VMware vStorage VI Web Service API reported an error with the
specified message text.

System action:

Processing stops.

User response:

Check the dsmerror log file for additional information, and contact the
IBM Spectrum Protect administrator with the information provided in this
message.

------------------------------------------------------------------------
ANS9356E

A VMware vStorage API error was reported.



Explanation:

A VMware vStorage API was reported. See other messages displayed and
logged for additional information about the problem.

System action:

Processing stops.

User response:

Check the dsmerror log file for additional information, and contact the
IBM Spectrum Protect administrator with the information provided in this
message.

------------------------------------------------------------------------
ANS9357E

HOTADD was chosen as the transport for at least one of the disks in the
operation, but the SAN policy is not OfflineAll for this datamover.
HOTADD cannot be used unless the SAN policy is OfflineAll.



Explanation:

HOTADD was chosen as the transport because either the default transport
setting was used, or it was specified in the VMVSTORTRANSPORT option. In
order to use HOTADD as the transport mode, the SAN policy must be set to
OfflineAll.

System action:

Restore processing stops.

User response:

Set the SAN policy to OfflineAll, or set VMVSTORTRANSPORT to something
other than HOTADD, such as NBD. Then try the restore operation again.

------------------------------------------------------------------------
ANS9359W

program-name: file-system: high threshold high-threshold exceeds
recommended maximum max-threshold maximum percentage.



Explanation:

System performance can be impacted. There can be delays from waiting for
demand migration.

System action:

Processing continues.

User response:

Set the migration high threshold lower than the file system capacity.

------------------------------------------------------------------------
ANS9360W

program-name: file-system: configured low-threshold low threshold is
below the recommended minimum floor-percent low threshold.



Explanation:

IBM Spectrum Protect low threshold is not recommended to be less than
teh minimum space required by this file system and may result in endless
attempts to find migration candidates. Usage of the file system may be
higher than the recommended minimum of low threshold on GPFS and Veritas
because these types of file system allocate some space for metadata.

System action:

Processing continues.

User response:

Set the migration low threshold higher than the recommended-minimum size
of the file system.

------------------------------------------------------------------------
ANS9361W

program-name: file-system: the configured pre-mig premigration is
greater than the difference between the configured low-threshold low
threshold and the recommended-minimum size of the file system Min_size.



Explanation:

IBM Spectrum Protect premigration percentage below the low threshold may
not leave sufficient space for the file system, and can result in
endless attempts to find migration candidates. Usage of the file system
may be higher than the recommended minimum of low threshold on GPFS and
Veritas because these types of file system allocate some space for
metadata.

System action:

Processing continues.

User response:

Lower the premigration setting.

------------------------------------------------------------------------
ANS9362W

program-name: file-system: MAXFILES max-files is less than used inodes
used inodes in the file system. MAXFILES will be set to the minimum
possible value.



Explanation:

The specified MAXFILES value is below the number of files already
existing in the file system. The value will be ignored, and CFI will
default to the minimum possible size according to the number of
currently used inodes.

System action:

Processing continues.

User response:

Increase the value of MAXFILES.

------------------------------------------------------------------------
ANS9363W

program-name: file-system: MAXFILES max-files is more than files total
available inodes in the file system. MAXFILES will be set to the maximum
possible value.



Explanation:

The specified MAXFILES value is above the number of available inodes in
the file system. The value will be ignored, and CFI will default to the
maximum size that corresponds to the number of available inodes.

System action:

Processing continues.

User response:

Decrease the value of MAXFILES.

------------------------------------------------------------------------
ANS9364E

Failure initializing virtual machine environment. Refer to dsmerror.log
for detailed error messages.



Explanation:

Failure initializing virtual machine environment. Refer to dsmerror.log
for detailed error messages.

System action:

The backup can not continue.

User response:

Refer to dsmerror.log for detailed error message.

------------------------------------------------------------------------
ANS9365E

VMware vStorage API error for virtual machine 'VM-name'. IBM Spectrum
Protect function name : function-name IBM Spectrum Protect file :
file-name (line-number) API return code : TSM-rc API error message :
function-desc



Explanation:

None.

System action:

Processing stops.

User response:

If virtual machine backup fails and the error message points to function
ReadEnvironmentVariableInGuest(), verify the validity of guest virtual
machine login credentials, update virtual machine login credentials on
data mover if necessary. Contact the IBM Spectrum Protect administrator
with the information provided in this message.

------------------------------------------------------------------------
ANS9368W

WARNING: VMware Host Userid <hostuserid> read from pwd file different
than VMCUSER option value <vmcuserid>. Using VMCUSER option value.



Explanation:

None.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS9369W

WARNING: VMware VirtualCenter or ESX Server User Password for VMC Host
<host> VMC Userid <userid> set in options file.



Explanation:

None.

System action:

Processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS9370W

Use Preferences Editor or dsmc SET PASSWORD -type=VM 'VirtualCenter
hostname' 'userid' 'password' to save encrypted password.



Explanation:

The VMCPW option was found either in an option file or on the command
line. While this method of entry is allowed, it presents a security risk
because the password is in plain text and not encrypted.

System action:

The option is accepted and the VMC password is used in the current
session.

User response:

To save the encrypted password, use the Preferences Editor VM Backup
panel or the command: dsmc SET PASSWORD -type=VM 'VirtualCenter
hostname' 'userid' 'password'

------------------------------------------------------------------------
ANS9371I

program-name: file-system: The specified MAXFILES value is 0. The CFI
size will be calculated automatically now.



Explanation:

IBM Spectrum Protect The specified maxfiles value is 0, which means that
the CFI size is managed automatically now.

System action:

IBM Spectrum Protect continues.

User response:

none.

------------------------------------------------------------------------
ANS9372E

Unable to create the virtual machine to be restored due to an invalid
host name, datacenter name, or datastore name.



Explanation:

IBM Spectrum Protect was unable to create the virtual machine to be
restored because an invalid host name, datacenter name, or datastore
name was specified. Check the dsmerror log file for information on the
specific reason for the failure.

System action:

Processing stops.

User response:

Check the dsmerror log file for additional information, and contact the
IBM Spectrum Protect administrator with the information provided in this
message.

------------------------------------------------------------------------
ANS9373E

The backup of virtual machine 'vm-name' stopped because the backup
operation was not progressing.



Explanation:

IBM Spectrum Protect detected a deadlock, which prevents the backup
operation of the virtual machine to finish. The backup operation was
cancelled.

System action:

The backup of the virtual machine was cancelled.

User response:

Retry the backup of the virtual machine. If the problem persists,
contact IBM Software Support.

------------------------------------------------------------------------
ANS9374E

VMware vStorage virtual storage driver service is not running or could
not be found. Make sure VMware 'vstor2-mntapi20-shared.sys' service is
installed and running. Install the VMware vStorage API runtime files.



Explanation:

Failure initializing VMware vStorage API environment.

System action:

The backup can not continue.

User response:

Make sure the VMware 'vstor2-mntapi20-shared.sys' service is installed
and running. Install the VMware vStorage API runtime files.

------------------------------------------------------------------------
ANS9376E

The Backup VM command domain keyword 'domain-keyword' was specified, but
this domain does not contain any virtual machines. This error can also
occur if the value for the VMHOST parameter is not specified as an IP
address or as a fully qualified domain name.



Explanation:

The command cannot complete because the virtual machine could not be
found.

System action:

Processing stops.

User response:

Try the operation again. Ensure that the value for the VMHOST parameter
is specified as an IP address or as a fully qualified domain name. The
host name that you specify must match the host name as it is displayed
in the vCenter server in the Host and Clusters view. This could be the
fully qualified host name (FQDN), the shortened domain name, or the host
IP address.

------------------------------------------------------------------------
ANS9377E

No virtual machine is specified on the string command or the virtual
machine domain list could not be processed.



Explanation:

No virtual machine found with name or specified in domain option.

System action:

Processing stops.

User response:

Specify a correct VM name or domain option.

------------------------------------------------------------------------
ANS9378E

Unexpected error while fingeprinting the data



Explanation:

There was an error while fingerprinting the data. See the error log for
more information.

System action:

The object is not backed up.

User response:

Retry the operation. Retry the operation without client-side
deduplication. If the problem persists, contact IBM Spectrum Protect
technical support.

------------------------------------------------------------------------
ANS9379E

Unexpected error while deduplicating the data



Explanation:

There was an error while deduplicating the data. See the error log for
more information.

System action:

The object is not backed up.

User response:

Retry the operation. Retry the operation without client-side
deduplication. If the problem persists, contact IBM Spectrum Protect
technical support.

------------------------------------------------------------------------
ANS9380E

The virtual machine that was specified on the string command could not
be found.



Explanation:

The command cannot complete because the virtual machine could not be
found.

System action:

Processing stopped.

User response:

Try the operation again. Specify a correct VM name or DOMAIN option.
This error can also be caused by incorrect settings for the VMHOST,
VMHOSTCLUSTER, VMFOLDER or VMDATASTORE options. The VMHOST option value
must be specified as an IP address or as a server name that is in fully
qualified domain name (FQDN) format. The host name that you specify must
match the host name as it is displayed in the vCenter server in the Host
and Clusters view. This could be the fully qualified host name (FQDN),
the shortened domain name, or the host IP address.

------------------------------------------------------------------------
ANS9381I

The value set for vmlist option will be migrated to the new domain
option.



Explanation:

New option has been set.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------
ANS9383E

The required files for the virtual machine operations were not found.
The files are installed only if the client is defined as a data mover in
IBM Spectrum Protect for Virtual Environments.



Explanation:

A failure occurred when initializing the virtual machine environment.

System action:

The operation cannot continue.

User response:

Install IBM Spectrum Protect for Virtual Environments package to use the
client to back up virtual machines.

------------------------------------------------------------------------
ANS9384W

Unable to get VMware Changed Block Tracking(CBT) data for virtual
machine 'virtual machine name'. Full VM backup continues, and includes
both used and unused areas of the disk.



Explanation:

IBM Spectrum Protect was unable to obtain Changed Block Tracking(CBT)
data for the specified virtual machine. The backup continues, but
instead of backing up just the used blocks (in the full VM backup case),
or just the changed blocks (in the incremental VM backup case), the
entire virtual machine is backed up. This backup includes both the used
and unused blocks of the disk.

System action:

The backup continues.

User response:

See the error log dsmerror.log for information about why the changed
block data is not obtained.

------------------------------------------------------------------------
ANS9385W

Error returned from VMware vStorage API for virtual machine 'VM-name' in
vSphere API function __ns2__QueryChangedDiskAreas. RC=API return code,
Detail message: API message



Explanation:

None.

System action:

CBT processing stops.

User response:

Contact the IBM Spectrum Protect administrator with the information
provided in this message.

------------------------------------------------------------------------
ANS9386W

Changed block tracking is not supported for virtual machine 'virtual
machine name'. A FULL backup of the disk will be performed and will
include both used and unused areas of the disk.



Explanation:

IBM Spectrum Protect was unable to obtain Changed Block Tracking(CBT)
data for the specified virtual machine because changed block tracking is
not supported. RDM disks in physical mode, virtual disks attached to
shared virtual SCSI bus, and VMs with hardware version 6 or earlier are
not supported. The backup continues, but instead of backing up just the
used blocks (in the full VM backup case), or just the changed blocks (in
the incremental VM backup case), the entire virtual machine is backed
up. This backup includes both the used and unused blocks of the disk.

System action:

The backup continues.

User response:

See the error log dsmerror.log for information about why the changed
block data is not obtained.

------------------------------------------------------------------------
ANS9387W

An incremental backup for virtual machine 'virtual machine name' is not
possible because changed block information cannot be obtained. A full VM
backup is attempted instead.



Explanation:

Changed block information is required to perform an incremental backup,
but the information could not be obtained from the virtual machine. The
information can be missing if two nodes back up the same virtual
machine. One node runs a daily incremental backup, and the other node
runs a weekly full backup. After the weekly full backup runs, the next
daily backup cannot obtain changed block information, so a full backup
is run instead of an incremental backup. Subsequent daily backups will
be incremental until the next weekly full backup.

System action:

The backup continues as a full backup instead of an incremental backup.

User response:

Search the IBM Spectrum Protect support site IBM Spectrum Protect
Support Portal
(https://www.ibm.com/mysupport/s/topic/0TO50000000IQWvGAO/spectrum-protect)
for this message number, for other possible causes of this error.

------------------------------------------------------------------------
ANS9388E

The management class 'management class name' specified for the 'option
name' option is invalid, or does not have a backup copy group.



Explanation:

The management class name for the specified option does not exist, or it
exists but does not have a valid backup copy group.

System action:

Processing stops.

User response:

Verify that the specified management class name is valid, and that it
contains a valid backup copy group.

------------------------------------------------------------------------
ANS9389W

The DEDUP backup attempt was unsuccessful for virtual machine 'virtual
machine name'. Retry #retry attempt number with DEDUP disabled.



Explanation:

The attempt to backup the virtual machine with DEDUP enabled was
unsuccessful. Instead of failing the backup right away, an attempt is
being made to backup the virtual machine with DEDUP disabled.

System action:

Processing continues with DEDUP disabled.

User response:

Check the log files for messages as to why DEDUP failed. If future
attempts to backup using DEDUP fail, contact your system administator.

------------------------------------------------------------------------
ANS9390W

The DEDUP backup attempt was unsuccessful for virtual machine 'virtual
machine name'. Retry #retry attempt number with DEDUP still enabled.



Explanation:

The attempt to backup the virtual machine with DEDUP enabled was
unsuccessful. Instead of failing the backup right away, an attempt is
being made to retry the backup of the virtual machine with DEDUP still
enabled.

System action:

Processing continues with DEDUP still enabled.

User response:

Check the log files for messages as to why DEDUP failed. If future
attempts to backup using DEDUP fail, contact your system administator.

------------------------------------------------------------------------
ANS9391W

Linux guest OS with EFI Boot enabled is not fully supported by IBM
Spectrum Protect VMware backup. Manual steps may be required following
restore to enable the virtual machine to power on correctly.



Explanation:

A restored Linux guest OS with EFI boot enabled may not successfully
start. Manual steps are required to successfully boot the guest OS.

System action:

Restore processing continues.

User response:

Following guest OS restore: remove and reattach the guest Linux boot
disk, select Guest Boot Option to enter EFI setup configuration on next
boot, power on the guest, enter EFI Boot Maintenance, add Boot Device,
select unnamed volume, give it a label, save and commit changes,
continue with boot.

------------------------------------------------------------------------
ANS9392W

No backupset name entered.



Explanation:

You must provide a backupset for this operation.

System action:

Processing stops.

User response:

Specify a valid backupset name.

------------------------------------------------------------------------
ANS9393W

Incorrect backupset name entered.



Explanation:

The backupset name provided was invalid. Wildcards are not allowed.

System action:

Processing stops.

User response:

Specify a valid backupset name.

------------------------------------------------------------------------
ANS9394W

No backupset file or device name entered.



Explanation:

You must provide a backupset file or device name for this operation.

System action:

Processing stops.

User response:

Specify a valid backupset file or device name.

------------------------------------------------------------------------
ANS9395E

The filespace has been migrated to the incremental forever model;
MODE=FULL and MODE=INCR are not valid.



Explanation:

You must run only incremental forever backup types (IFINCR or IFFULL) if
the filespace has been migrated to the incremental forever type.

System action:

Processing stops.

User response:

Specify either MODE=IFFULL or MODE=IFINCR.

------------------------------------------------------------------------
ANS9396W

Virtual machine 'VM' is not running. IBM Spectrum Protect Application
Protection will not be used while backing up this VM.



Explanation:

IBM Spectrum Protect Application Protection can only protect VMs that
are running.

System action:

IBM Spectrum Protect Application Protection uses the VMWare tools to
provide application consistency.

User response:

Turn on the virtual machine or exclude it from IBM Spectrum Protect
application protection by removing the INCLUDE.VMTSMVSS option for this
virtual machine. If you want logs to be truncated use INCLUDE.VMTSMVSS
to protect this machine.

------------------------------------------------------------------------
ANS9397W

IBM Spectrum Protect application protection cannot protect this machine.
Virtual machine 'VM' does not have operating system or applications
supported by IBM Spectrum Protect application protection.



Explanation:

The application protection can be used only for virtual machines that
have operating systems or applications that are supported by IBM
Spectrum Protect application protection. Refer to the product
documentation for the list of supported operating systems and
applications.

System action:

IBM Spectrum Protect will use the VMware Tools to provide application
consistency.

User response:

Exclude the virtual machine from application protection by removing the
INCLUDE.VMTSMVSS option for this virtual machine.

------------------------------------------------------------------------
ANS9398E

IBM Spectrum Protect application protection failed to initialize on
virtual machine 'VM'. See the error log for more details.



Explanation:

IBM Spectrum Protect application protection encountered an error during
initialization.

System action:

Processing stops.

User response:

See the error log for more details. Correct the error(s) and try the
operation again.

------------------------------------------------------------------------
ANS9399W

program-name: lock file access error for operation value on path value
value with errno text value.



Explanation:

A lock file operation has failed.

System action:

IBM Spectrum Protect logs the condition and continues processing, or
exits if directory not found.

User response:

Correct the configuration.

------------------------------------------------------------------------
ANS9400W

Unable to restore NVRAM file for vm 'virtual machine name'. Manual steps
may be required following restore to enable the virtual machine to power
on correctly.



Explanation:

IBM Spectrum Protect was unable to upload NVRAM file for the specified
virtual machine. The restore continues, but a restored guest OS with EFI
boot enabled may not successfully start. Manual steps may be required to
successfully boot the guest OS.

System action:

The restore continues.

User response:

Following guest OS restore if guest OS fails to boot: remove and
reattach the guest OS boot disk, select Guest Boot Option to enter EFI
setup configuration on next boot, power on the guest, enter EFI Boot
Maintenance, add Boot Device, select unnamed volume, give it a label,
save and commit changes, continue with boot.

------------------------------------------------------------------------
ANS9401E

program-name: Cannot kill recall daemon.



Explanation:

IBM Spectrum Protect A request for killing the recall daemon failed.
This may occur during node failover.

System action:

none.

User response:

Continue with normal operation unless further errors occur.

------------------------------------------------------------------------
ANS9402E

program-name: Cannot notify process name to recover HSM operations on a
failing node.



Explanation:

In order to assume the functionality of a failing partner node, the
dsmwatchd daemon must notify the local daemons.

System action:

none.

User response:

Communication cannot be established with the HSM daemon specified in
this message. Check whether the target daemon is running. Start or
restart the target daemon as appropriate. If the problem persists,
restart the GPFS cluster.

------------------------------------------------------------------------
ANS9403E

IBM Spectrum Protect has detected that the data to back up does not
match the list of data to back up that was sent from the virtual
machine. The backup of 'VM-Name' cannot continue.



Explanation:

The data that IBM Spectrum Protect would have backed up for a virtual
machine would not match the data needed for a correct backup. The backup
has been cancelled to prevent data loss.

System action:

The backup is cancelled to prevent data loss.

User response:

Retry the backup. If this error occurs again, contact IBM Software
Support.

------------------------------------------------------------------------
ANS9404E

Error creating the specified Virtual Machine. See log files for more
information.



Explanation:

An error was encountered creating the Virtual Machine. Look in the
dsmerror.log for additional information on why the Virtual Machine could
not be created.

System action:

Processing stops.

User response:

Check the dsmerror.log for more specific messages on why the virtual
machine could not be created.

------------------------------------------------------------------------
ANS9405I

program-name: The takeover of filesystem file system started.



Explanation:

The local activation of the specified file system started successfully.

System action:

IBM Spectrum Protect on the local node will try to activate the file
system that is space managed on another node.

User response:

None.

------------------------------------------------------------------------
ANS9410W

VMware Tools are either not runnning or out-of-date on virtual machine
'VM'. IBM Spectrum Protect application protection cannot be used.



Explanation:

IBM Spectrum Protect application protection requires that VMware tools
are installed and running with an up-to-date version on the virtual
machine.

System action:

IBM Spectrum Protect will not provide application consistency.
Application logs are not truncated.

User response:

Install and/or upgrade and/or start VMware Tools on the virtual machine
or exclude it from the application protection by removing the
INCLUDE.VMTSMVSS option for this virtual machine.

------------------------------------------------------------------------
ANS9411E

VSS provider registration failed. Command 'command' failed with Windows
RC=return code



Explanation:

IBM Spectrum Protect was unable to register the VSS provider on the
virtual machine.

System action:

Processing stops.

User response:

Restart the virtual machine and try the operation again.

------------------------------------------------------------------------
ANS9412E

program-name: Failover is disabled on the local machine. Aborting
failover ...



Explanation:

IBM Spectrum Protect Failover operations were disabled either by the
system or the user.

System action:

None.

User response:

Check failover policy if necessary.

------------------------------------------------------------------------
ANS9413E

The instant restore or instant access operation failed because these
operations do not support virtual machines that are in virtual volume
(VVOL) datastores.



Explanation:

The instant restore and instant access operations do not support
restores of virtual machines that are in VVOL datastores. VVOL
datastores do not support Raw Device Mapping (RDM), which is required
for these operations.

System action:

The operation fails.

User response:

For instant restore operations, specify a datastore and temporary
datastore that is not a VVOL datastore.For instant access operations,
specify a datastore that is not a VVOL datastore.

------------------------------------------------------------------------
ANS9414E

Application protection is enabled for virtual machine 'VM-name',
however, this virtual machine resides on a Virtual Volume (VVol)
datastore. Application protection needs to be disabled in order to back
up this virtual machine.



Explanation:

Application protection is not supported for virtual machines that reside
on VVol datastores.

System action:

The operation fails.

User response:

Disable application protection by removing the include.vmtsmvss option
from the options file and back up the virtual machine again.

------------------------------------------------------------------------
ANS9415E

Failed to copy 'source' to 'destination' with VMware RC=rc on virtual
machine 'guest VM name'.



Explanation:

IBM Spectrum Protect was unable to copy a file to the virtual machine.

System action:

Processing stops.

User response:

Verify that the source file exists and the destination is accessible.
Restart the virtual machine and try the operation again.

------------------------------------------------------------------------
ANS9416E

Cannot create the directory 'source' on the virtual machine with Windows
RC=rc



Explanation:

IBM Spectrum Protect client was unable to create the specified directory
on the virtual machine. It is possible that the directory exists and is
locked by a process.

System action:

Processing stops.

User response:

Verify the the specified directory does not exist on the virtual
machine. Restart the virtual machine and try the operation again.

------------------------------------------------------------------------
ANS9417E

IBM Spectrum Protect application protection could not freeze the VSS
writers on the virtual machine named 'VM'. See the error log for more
details.



Explanation:

IBM Spectrum Protect application protection encountered an error while
freezing the VSS writers.

System action:

Processing stops

User response:

Use the 'vssadmin list writers' command to determine if any VSS writers
detect errors on the virtual machine. Restart the VM. Retry the
operation. If the retry fails, see the error log for details about the
errors.

------------------------------------------------------------------------
ANS9418E

SAN was chosen as the transport for at least one of the disks in the
operation, but VMware Changed Block Tracking (CBT) is enabled on the
target VM. SAN cannot be used to update existing VM, when CBT is
enabled.



Explanation:

SAN was chosen as the transport because either the default transport
setting was used, or it was specified in the VMVSTORTRANSPORT option. In
order to use SAN as the transport mode, VMware Changed Block Tracking
(CBT) has to be disabled on the target VM.

System action:

Restore processing stops.

User response:

Disable VMware Changed Block Tracking (CBT) on the target VM, or set
VMVSTORTRANSPORT to something other than SAN, such as NBD. Then try the
restore operation again.

------------------------------------------------------------------------
ANS9419E

VM backup failed for virtual machine 'virtual machine name' because
VMware Changed Block Tracking(CBT) cannot be enabled or reset due to an
existing snapshot.



Explanation:

VMware does not allow changing state of Changed Block Tracking(CBT),
when a snapshot exists.

System action:

The backup stops.

User response:

Delete snapshot on the target vm to allow CBT to be enabled or reset or
set the VMNOCBTCONTINUE YES option then try the backup again. If you set
VMNOCBTCONTINUE YES, then used and unused blocks on each disk of the VM
are backed up.

------------------------------------------------------------------------
ANS9420W

VMware Changed Block Tracking(CBT) cannot be enabled or reset for
virtual machine 'virtual machine name' due to an existing snapshot. Full
VM backup continues, and includes both used and unused areas of the
disk.



Explanation:

VMware does not allow changing state of Changed Block Tracking(CBT),
when a snapshot exists. The backup continues, but instead of backing up
just the used blocks (in the full VM backup case), or just the changed
blocks (in the incremental VM backup case), the entire virtual machine
is backed up. This backup includes both the used and unused blocks of
the disk.

System action:

The backup continues.

User response:

Delete snapshot on the target vm to allow CBT to be enabled or reset.

------------------------------------------------------------------------
ANS9421E

VM backup failed for virtual machine 'virtual machine name' because one
of the disks has size that is not multiple of 1MB.



Explanation:

VMware does not support backup of disks with size that is not multiple
of 1MB. The backup fails.

System action:

The backup fails.

User response:

Increase the affected disk size to be a multiple of 1MB.

------------------------------------------------------------------------
ANS9422I

program-name: The rollback of filesystem file system started.



Explanation:

The local activation of the specified file system started successfully.

System action:

IBM Spectrum Protect on the local node will try to activate the file
system that is space managed on another node.

User response:

None.

------------------------------------------------------------------------
ANS9427E

The virtual machine 'virtual machine name' disk 'virtual machine disk
name' could not be opened because none of the allowed transports
('allowed transport modes') is available.



Explanation:

The disk can only be opened using one of the transport modes specified
in the VMVSTORTRANSPORT option. However, none of the specified transport
modes were available, so the disk cannot be opened.Since none of the
specified transport modes was available, the disk could not be opened.

System action:

The virtual machine is not backed up. Processing continues with the next
virtual machine.

User response:

Carry out one or more of the following actions and then try the backup
again.

*  Check the VMVSTORTRANSPORT option value and verify that the desired
   transport modes are available.

*  Add NBD or NBDSSL to the VMVSTORTRANSPORT option.

*  Check the "%TEMP%/VMWARE-%USER%" directory for leftover files from a
   previous backup. Leftover files can prevent the use of advanced
   transport modes. This directory can be safely deleted as long as no
   other VM operations are running.



------------------------------------------------------------------------
ANS9428E

program-name: The takeover of filesystem file system failed to start.



Explanation:

The local activation of the specified file system failed to start.
Please, note that only file systems which are space managed on another
node within the same cluster can be taken over. Additionally, the file
system must be mounted locally.

System action:

IBM Spectrum Protect will not take over the file system.

User response:

Make sure the file system is mounted locally and managed with the IBM
Spectrum Protect client for space management on another node within the
same cluster and retry the operation.

------------------------------------------------------------------------
ANS9431E

IBM Spectrum Protect application protection failed to thaw VSS writers
on virtual machine 'VM'. See the IBM Spectrum Protect error log for more
details.



Explanation:

IBM Spectrum Protect application protection encountered an error while
thawing VSS writers.

System action:

Processing stops

User response:

See the error log for more details. Verify that all VSS writers are not
reporitng errors by running command 'vssadmin list writers'. Restart the
virtual machine and try the operation again. If the retry fails, see the
error log for details about the errors.

------------------------------------------------------------------------
ANS9432W

IBM Spectrum Protect application protection failed to truncate
application logs on virtual machine 'VM'.



Explanation:

IBM Spectrum Protect application protection encountered an error while
completing VSS backup operation. The applications were successfully
quiesced, but their logs were not truncated.

System action:

Application logs are not truncated.

User response:

See the error log for more details. Verify that all VSS writers are not
reporting errors by running command 'vssadmin list writers'. Restart the
virtual machine and try the operation again. If the retry fails, see the
error log for details about the errors. On the guest VM, verify that a
mounted volume is not online. Use the Recovery Agent to dismount and
remove any existing mount directories. Then, try the backup operation
again.

------------------------------------------------------------------------
ANS9433E

program-name: dm_send_msg failed with errno Errno.



Explanation:

Unable to execute DMApi call.

System action:

Aborting operation.

User response:

Check consistency of the GPFS daemon.

------------------------------------------------------------------------
ANS9443E

program-name: The operation cannot be executed in a deactivated failover
environment.



Explanation:

The operation relies on an active failover environment.

System action:

Aborting operation.

User response:

Run dsmmigfs enableFailover on the local node and repeat the operation.

------------------------------------------------------------------------
ANS9447E

The virtual machine 'virtual machine name' disk could not be opened
because none of the allowed transports is available.



Explanation:

The disk can only be opened using one of the transport modes specified
in the VMVSTORTRANSPORT option. However, none of the specified
transports modes was available, so the disk cannot be opened.

System action:

The virtual machine is not backed up. Processing continues with the next
virtual machine.

User response:

Carry out one or more of the following actions and then try the backup
again.

*  Check the console output and error logs for information about which
   transport modes are allowed.

*  Check the VMVSTORTRANSPORT option value and verify that the desired
   transport modes are available.

*  Add NBD or NBDSSL to the VMVSTORTRANSPORT option.

*  Check the "%TEMP%/VMWARE-%USER%" directory for leftover files from a
   previous backup. Leftover files can prevent the use of advanced
   transport modes. This directory can be safely deleted as long as no
   other VM operations are running.



------------------------------------------------------------------------
ANS9450W

program-name: No eligible filesystem for takeover.



Explanation:

None of the locally mounted GPFS filesystems matches with the remotely
managed filesystems of the failure node.

System action:

Aborting takeover operation.

User response:

Check that the filesystems of the remote failure node get managed
elsewhere within the node set.

------------------------------------------------------------------------
ANS9451E

program-name: GPFS or the SP switch is down locally. Aborting takeover
activities ...



Explanation:

IBM Spectrum Protect GPFS is not functional locally.

System action:

Aborting takeover operation.

User response:

Check switch and VSD status. The local system must be unfenced.

------------------------------------------------------------------------
ANS9452E

program-name: The DMApi is not functional locally. Aborting takeover
activities ...



Explanation:

The operation stopped because the DMApi interface is not accessible.

System action:

Aborting takeover operation.

User response:

Check GPFS status.

------------------------------------------------------------------------
ANS9453E

program-name: Could not determine the GPFS storage pool id for file
'file-path'. Reason: reason



Explanation:

The processed file does not exist or is located on a file system without
storage pool support.

System action:

The requested operation stops.

User response:

Please check the input parameters and if DMAPI is enabled on the file
system.

------------------------------------------------------------------------
ANS9457E

program-name: Could not determine the storage pools of file system
'file-system'. Reason: reason



Explanation:

The specified file system is not a GPFS file system or has an old GPFS
version.

System action:

The requested operation stops.

User response:

Please update to a supported version of GPFS.

------------------------------------------------------------------------
ANS9459E

Using the specified MAXCANDIDATES parameter would produce an
out-of-space condition in the parent filesystem of
/etc/adsm/SpaceMan/candidatesPool. Based on the current free space
situation the maximum value for the MAXCANDIDATES parameter is value.



Explanation:

The automigration candidate pools for the selected filesystem require
MAXCANDIDATES per 10 KB plus a safety buffer of 5 MB of memory under
/etc/adsm/SpaceMan/candidatesPool , which exceeds the available space.

System action:

IBM Spectrum Protect Abort operation.

User response:

Increase the filesystem size or choose a smaller value for the
MAXCANDIDATES parameter. You may also create a dedicated filesystem with
sufficient space for the migration pools under
/etc/adsm/SpaceMan/candidatesPool. Kill the dsmscout processes after
performing this option.

------------------------------------------------------------------------
ANS9462E

Failover functionality is not supported with this HSM release.



Explanation:

The IBM Spectrum Protect user ran dsmmigfs with the failover flag on an
unsupported platform.

System action:

IBM Spectrum Protect ends the operation.

User response:

None.

------------------------------------------------------------------------
ANS9469E

Warning! Unable to write a complete migration candidate list due to low
space in the parent filesystem of name.



Explanation:

IBM Spectrum Protect Low space in filesystem which stores the migration
candidates files.

System action:

IBM Spectrum Protect The executable writes a partial migration
candidates list.

User response:

Increase the filesystem size or create a dedicated filesystem with
sufficient size under the given path.

------------------------------------------------------------------------
ANS9474E

program-name: Lost my session with errno: errno . Trying to recover.



Explanation:

The DMAPI session is not valid.

System action:

Trying to recover session.

User response:

Check the failure node. You might have to recover the local GPFS daemon.

------------------------------------------------------------------------
ANS9475W

IBM Spectrum Protect application protection failed to cleanup after a
VSS backup on virtual machine VM.



Explanation:

IBM Spectrum Protect application protection encountered an error while
cleaning up after a VSS backup operation.

System action:

None

User response:

See the error log for more details. Restart the virtual machine and try
the operation again. If the problem persists, contact IBM technical
support for further assistance.

------------------------------------------------------------------------
ANS9476I

program-name: Recovered my DM session sid.



Explanation:

DMAPI session is recovered.

System action:

This message is for informational purposes only.

User response:

No action is required.

------------------------------------------------------------------------
ANS9480E

program-name: The rollback of filesystem file system failed to start.



Explanation:

The local activation of the specified file system failed to start.
Please, note that a rollback can only be performed after the space
management of the file system was moved from the local node to another
node during failover. Additionally, the file system must be mounted
locally.

System action:

IBM Spectrum Protect will not roll back the file system.

User response:

Make sure the file system is mounted locally and managed with the IBM
Spectrum Protect client for space management on another node within the
same cluster and retry the operation.

------------------------------------------------------------------------
ANS9487W

program-name: cannot query the right on session session for file handle
= filehandle token = token. Reason : error



Explanation:

The Space Management cannot query the right on a file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9488E

IBM Spectrum Protect uses the Java Runtime Environment (JRE), but either
the JRE could not be found in the 'jrePath' directory, or the JRE
version could not be determined. Possible reasons are that there is a
problem with the product installation, or the TEMP or TMP environment
variables are set to a directory that is inaccessible by the user.



Explanation:

JRE was not found in the IBM Spectrum Protect installation directory.

System action:

Processing stops

User response:

Re-install the product or install a required version of JRE and try
again. If JRE is already installed on your machine, then make sure the
PATH environment variable contains path to javaw.exe. In addition to
that, verify that the TEMP and TMP environment variables each point to
an existing directory, and that the user has sufficient permissions to
access the directory.

------------------------------------------------------------------------
ANS9489E

Java Runtime Environment (JRE) was not found.



Explanation:

JRE was not found.

System action:

Processing stops

User response:

If you have already installed JRE, verify that the \"java\" executable
can be reached via an appropriate PATH environment variable setting.
Otherwise, install the required JRE version. For more details on the
hardware and software requirements, see the following technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21505139 For more
details on how to configure the data mover nodes in a vSphere
environment, see "Advanced configuration tasks" appendix of the IBM
Spectrum Protect for Virtual Environments "Data Protection for VMware
Installation Guide".

------------------------------------------------------------------------
ANS9490E

Cannot find httpagent.jar in the IBM Spectrum Protect client
installation directory.



Explanation:

The required file was not found.

System action:

Processing stops

User response:

Re-install the product or install a required version of JRE and try
again.

------------------------------------------------------------------------
ANS9491E

The password credentials for virtual machine 'guest VM name' could not
be found. Use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid'
'password' to save encrypted password.



Explanation:

The required password was not found.

System action:

Processing stops

User response:

Use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password'
to save encrypted password. And then retry the 'backup vm' operation.

------------------------------------------------------------------------
ANS9492E

Destination size is not equal to source



Explanation:

The space allocation for the selected destination is not the same as the
source.

System action:

The restore operation is not performed.

User response:

Choose a different destination which is equal in size to the source.

------------------------------------------------------------------------
ANS9493E

The credentials found for virtual machine 'guest VM name' are incorrect.
Verify the credentials and use dsmc SET PASSWORD -type=VMGUEST 'VM guest
name' 'userid' 'password' to update the username and password.



Explanation:

The supplied credentials are incorrect. Failed to authenticate to guest
VM using these credentials.

System action:

Processing stops

User response:

Use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password'
to update the username and password. And then retry the 'backup vm'
operation.

------------------------------------------------------------------------
ANS9494E

Command 'command' completed with RC=return code on virtual machine
'guest VM name'.



Explanation:

A remote command either timed out or failed.

System action:

Processing stops

User response:

Increase the value of VMTIMEOUT option and try the operation again.

------------------------------------------------------------------------
ANS9495E

Failed to login to virtual machine 'guest VM name' because the VMware
Tools are not running in the guest machine. Verify that the VMware tools
are running and that no other program has access or is making any
changes to this VM.



Explanation:

Failed to login to virtual machine because the VMware Tools are not
running in the guest machine.

System action:

Processing stops

User response:

Make sure that the VMware tools are running and that no other program
has access or is making changes to this VM. And then retry the 'backup
vm' operation.

------------------------------------------------------------------------
ANS9496E

Unable to lock virtual machine VM for application protection.



Explanation:

The virtual machine is being backed up by another process. Only one
process is allowed to use IBM Spectrum Protect application protection
during a backup of a virtual machine at a time.

System action:

Processing stops

User response:

There is already another virtual machine backup in process via another
datamover. Please wait for the other virtual machine backup to complete
and re-try the operation. Or there was a crash or CTRL+C during the
previous virutal machine backup. Please wait 10 minutes and re-try the
operation.

------------------------------------------------------------------------
ANS9497W

Virtual machine 'VM' resides on an ESX Server or vCenter that is not
supported by IBM Spectrum Protect application protection. IBM Spectrum
Protect application protection will not be used.



Explanation:

Refer to the product documentation for the list of supported ESX and
vCenter versions.

System action:

IBM Spectrum Protect will use the VMware Tools to provide application
consistency.

User response:

Exclude the virtual machine from application protection by removing the
INCLUDE.VMTSMVSS option for this virtual machine.

------------------------------------------------------------------------
ANS9498W

A valid IBM Spectrum Protect for Virtual Environments license file
(license-file) cannot be located. IBM Spectrum Protect application
protection will not be used.



Explanation:

The license file was not found, or cannot be opened because of
permissions, or the file is corrupted.

System action:

IBM Spectrum Protect will use the VMware Tools to provide application
consistency.

User response:

Check permissions on file. See if the license file is in the correct
place.

------------------------------------------------------------------------
ANS9499W

VMware tools on virtual machine 'VM' need to be updated. IBM Spectrum
Protect application protection will still be used.



Explanation:

IBM Spectrum Protect application protection requires that VMware Tools
are up to date.

System action:

IBM Spectrum Protect will use the VMware Tools to provide application
consistency.

User response:

Update VMware Tools on the virtual machine

------------------------------------------------------------------------
ANS9500W

program-name: cannot disposition the mount event. Reason: error



Explanation:

The system wide mount event could not be dispositioned. Mount events
will not be received by this daemon.

System action:

Processing continues.

User response:

Try to resolve the problem and restart the recall daemon. If the problem
cannot be resolved immediately, kill and restart the recall daemon after
an Space Management supported file system has been added using dsmmigfs
or after a file system has been mounted using the mount command.

------------------------------------------------------------------------
ANS9501W

program-name: cannot set event disposition on session session for file
system mountdir token = token. Reason : error



Explanation:

Events could not be dispositioned on the file system. No events will be
received for this filesystem. HSM is not enabled for this file system.

System action:

Processing continues.

User response:

The file system must be one of the supported native file systems in
order for the Space Management to support it. Verify that the mount
options the file system are correct. Correct the problem and remount the
file system.

------------------------------------------------------------------------
ANS9502W

program-name: cannot remove event disposition on session session for
file system mountdir token = token. Reason : error



Explanation:

Event dispositions could not be removed from the file system.

System action:

Processing continues.

User response:

Verify that the file system is mounted and that dmapi is enabled on that
file system. If the problem persists, unmount and remount the file
system, then try the operation again. If the problem still persists,
reboot the system.

------------------------------------------------------------------------
ANS9503I

program-name: events have been set and dispositioned on session session
for file system filesystem-name



Explanation:

Setting events and dispositioning these on a DM session enables the file
system for Space Management support.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9504W

program-name: The file system filesystem-name is not mounted or is
mounted with wrong options.



Explanation:

Either the file system is not mounted or it has been mounted with
incorrect options.

System action:

IBM Spectrum Protect continues.

User response:

Mount the file system or remount it with corrected mount options.

------------------------------------------------------------------------
ANS9505E

program-name: cannot initialize the DMAPI interface. Reason: error



Explanation:

IBM Spectrum Protect client failed to perform implementation-defined
initialization of the DMAPI interface.

System action:

The dm_init_service() function failed.

User response:

If you are running IBM Spectrum Protect as a non-root user and you have
IBM Spectrum Protect Space Management client installed, make sure that
the dsmrootd daemon is up and running, then retry the operation. If you
don't have the Space Management client installed, retry the operation
under the root user authority.

------------------------------------------------------------------------
ANS9506E

program-name: The provided filespace argument 'argument' has an invalid
format.



Explanation:

Occurs if you are on a GPFS file system and the file system parameter
was not in the correct format.

System action:

The requested operation stops.

User response:

See the dsmautomig documentation for the correct syntax.

------------------------------------------------------------------------
ANS9507E

program-name: cannot request the right on session session for file
handle filehandle token = token. Reason : error



Explanation:

Space Management cannot request the required right on a file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9508W

program-name: cannot release the right on session session for file
handle = filehandle token = token. Reason : error



Explanation:

Space Management cannot release the right on a file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9509W

program-name: received an unexpected event of type event-type on session
session.



Explanation:

The Space Management daemon received an unexpected event. This event has
not been dispositioned.

System action:

IBM Spectrum Protect ignores event and continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9510E

program-name: cannot get event messages from session session, expected
max message-length = msglen, returned message-length = return-length.
Reason : error



Explanation:

Space Management encountered an error while trying to receive a message
on a DM session.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9511E

program-name: cannot read DM attributes on session session for file:
name = name handle = handle token = token. Reason : error



Explanation:

Space Management cannot read the DM attributes of a DM object, usually a
file. If the file name is not available, it will be displayed as an
empty string or as <NA>.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9512E

program-name: cannot set DM attributes on session session for file
handle = filehandle token = token. Reason : error



Explanation:

Space Management cannot set DM attributes for a DM object, usually a
file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9513E

program-name: cannot remove DM attributes on session session for file
handle = filehandle token = token. Reason : error



Explanation:

Space Management cannot remove DM attributes for a DM object, usually a
file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9514E

program-name: cannot create a file handle from path. Reason: error



Explanation:

Space Management cannot create a file handle from the given file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9515E

program-name: cannot set the migration information. Reason: error



Explanation:

Space Management cannot set the migration information of a file, because
Space Management cannot create a file handle from the file or from the
file system.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9516E

program-name: cannot create an user event message on session session.
Reason: error



Explanation:

Space Management cannot create an user event message, needed to
reference rights on a file to be processed.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9518E

program-name: cannot respond to an event message on session session
using token token Reason : error



Explanation:

An event message could not be responded to (returned to the system).

System action:

Space Management continues.

User response:

If a user process is unexpectedly blocked and cannot be killed, see your
system administrator.

------------------------------------------------------------------------
ANS9519W

program-name: cannot set eventlist for a file system on session session
token = token fs-handle = fs-handle. Reason : error



Explanation:

An eventlist could not be set on a file system. None of the events will
be generated by the system on this file system.

System action:

Space Management continues.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
reboot the system.

------------------------------------------------------------------------
ANS9520E

program-name: cannot set a managed region on session session for file
handle = filehandle token = token. Reason : error



Explanation:

A managed region could not be set on a file. No events will be generated
for this file.

System action:

Processing of the file is interrupted.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
reboot the system.

------------------------------------------------------------------------
ANS9521E

program-name: cannot get the file attributes on session session for file
handle = handle token = token. Reason : error



Explanation:

Space Management cannot read the attributes of a file.

System action:

Processing of the file is interrupted.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
reboot the system.

------------------------------------------------------------------------
ANS9522E

program-name: can not create a file system handle from path. Reason:
error



Explanation:

The program can not create a file system handle from the file system
name. If Reason is Operation not permitted, the dmapi functionality may
be disabled for the file system.

System action:

Processing of the file system is interrupted.

User response:

If Reason is Operation not permitted, enable dmapi functionality for the
file system and retry.

------------------------------------------------------------------------
ANS9523E

program-name: is unable to verify the stub size for the file on session
session file handle = filehandle token = token. Reason : error



Explanation:

A correct stub size could not be determined by the system.

System action:

The system stops migration of the file.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9524W

program-name: adjusted stubsize to an allowed value on session session
file handle = filehandle token = token old stubsize = old-size new
stubsize = new-size



Explanation:

The predefined stubsize for the file should be corrected to accommodate
to the boundary and rounding constraints imposed by the DMAPI
implementation. Space Management can also change the stubsize during
migration if the predefined stubsize value is larger than the logical
file size.

System action:

Space Management continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9525E

program-name: is unable to create a stub file on session session for
file handle = handle token = token. Reason : error



Explanation:

An error occurred while creating a stub file.

System action:

Processing of the file is interrupted.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9526E

program-name: cannot open the state file filename for writing. Reason:
error



Explanation:

The global or file system state file could not be opened.

System action:

Processing stops.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9527E

program-name: cannot write to the state file filename. Reason: error



Explanation:

Space Management could not write to the state file.

System action:

Processing stops.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9528W

program-name: cannot read from the state file filename. . The file is
corrupted and will be recreated.



Explanation:

Space Management could not read from the state file.

System action:

Processing stops.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9529W

program-name: cannot obtain the handle of a file system state file



Explanation:

IBM Spectrum Protect space management could not find the handle of a
file system state file that is stored in the global state file. This can
occur if either space management is querying a file system that has no
HSM support added, or the file system state file is corrupted, or the
global state file is corrupted.

System action:

IBM Spectrum Protect continues or stops processing, depending on the
situation.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9530W

program-name: cannot remove an entry for file-system from the global
state file.



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.

System action:

IBM Spectrum Protect does not remove the entry from the global state
file.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9531E

program-name: cannot create a DM session: old session = oldsession
session info = session-info. Reason : error



Explanation:

Space Management could not create a DM session.

System action:

Processing stops.

User response:

Try the operation again. If the problem persists restart the system.

------------------------------------------------------------------------
ANS9532W

program-name: cannot destroy the session session. Reason: error



Explanation:

Space Management could not destroy a DM session.

System action:

Processing continues.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9533W

program-name: failed getting all sessions. Reason: error



Explanation:

Space management could not get all DM sessions on the system.

System action:

Processing stopped.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9534W

program-name: cannot find existing DMAPI session for the program.
Reason: error



Explanation:

The Space Management program cannot find a previously used DMAPI session
on the system

System action:

The Space Management program will open a new DMAPI session

User response:

Continue with normal operation if a new DMAPI session can be created.
Issue error if a new DMAPI session cannot be created.

------------------------------------------------------------------------
ANS9535E

program-name: a file handle could not be created from the file
descriptor file-descriptor. Reason: error



Explanation:

Space management could not create a file handle.

System action:

Processing of the file is interrupted.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9536E

program-name: cannot query an event message on session session. Reason:
error



Explanation:

The space management recall service was not able to identify whether a
recall request was initiated from the NFS daemon.

System action:

Processing of the file is interrupted.

User response:

Verify the NFS daemon is properly running and retry the recall
operation.

------------------------------------------------------------------------
ANS9537E

program-name: Invalid storage pool 'storagepool' for file system
'filesystem'.



Explanation:

No storage pool with that name exists on the specified file system.

System action:

The requested operation stops.

User response:

Please make sure the storage pool exists on the specified file system.

------------------------------------------------------------------------
ANS9538W

program-name: request request for DM file attributes not recognized



Explanation:

An unknown request type has been encountered that cannot be handled.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9539E

program-name: cannot create a file system handle from the file handle =
filehandle. Reason : error



Explanation:

A file system handle could not be created from a file handle.

System action:

Processing continues.

User response:

Continue with normal operation.

------------------------------------------------------------------------
ANS9542E

program-name: the file attributes could not be set on session session
for file handle = filehandle token = token flag = flag Reason : error



Explanation:

Space management could not update file attributes.

System action:

Processing of the file is interrupted.

User response:

Try the operation again. If the problem persists, verify that the file
system is mounted with dmapi enabled. If the problem still persists,
restart the system.

------------------------------------------------------------------------
ANS9543W

program-name: The IBM Spectrum Protect client needs blocks-num1 free
file system blocks to be able to handle the nospace condition on file
system filesystem-name, errno: error-num, reason: error-str. Currently
blocks-num2 blocks with a block size of block-size bytes are available.



Explanation:

Either the client is not able to get status information for the file
system or there is insufficient space in the file system. The message
reports zero blocks if the file system status information is not
available.

System action:

Processing continues.

User response:

If there is insufficient space in the file system, free the required
space or increase the file system capacity. If this is due to an input
output error, perform an appropriate file system check (e.g. fsck). Then
try the operation again.

------------------------------------------------------------------------
ANS9545E

program-name: cannot get a lock for lockdirlockfile to continue
processing.



Explanation:

Space management could not obtain a lock for a file.

System action:

processing stops.

User response:

Try the operation again. If problem persists, restart HSM. If problem
still persists, restart the system.

------------------------------------------------------------------------
ANS9546E

IBM Spectrum Protect cannot perform instant restore because Microsoft
Active Directory Domain Controller was detected on virtual machine.



Explanation:

The virtual machine contains Microsoft Active Directory Domain
Controller. It cannot be recovered using instant restore.

System action:

Processing stops.

User response:

Use a regular restore to recover the virtaul machine.

------------------------------------------------------------------------
ANS9548W

Cannot complete remote file access for inode:'inode number', alias:'file
name'.



Explanation:

Space management cannot complete the remote file access. The file may be
migrated to an IBM Spectrum Protect migration server that could be
temporarily unavailable. The file may be an orphan stub.

System action:

Process terminates the current operation.

User response:

Check to see whether the server has been disabled by the system
administrator, then retry the operation. To check whether the file is an
orphan stub or not, run dsmreconcile for the affected file system. Note:
the file alias may be displayed as 'unavailable' if the connection to
server is unavailable or 'orphan' if the appropriate file copy cannot be
located on a particular migration server.

------------------------------------------------------------------------
ANS9550W

File recall has been discontinued.



Explanation:

Recall stops because the file being recalled would cause the file system
to run out of space.

System action:

Process terminates the current operation.

User response:

Increase the file system space, or remove unneeded files, or wait until
space management has migrated files off the file system by demand or
threshold migration, or manually migrate files. Then retry the
operation.

------------------------------------------------------------------------
ANS9551E

Incorrect use of the dsmmigrate command with the recover parameter. The
filelist is not set.



Explanation:

The filelist is not specified.

System action:

Processing stopped.

User response:

Ensure that you specified the filelist.

------------------------------------------------------------------------
ANS9552E

program-name: cannot add space management to file-system; path includes
non-local file system.



Explanation:

An attempt was made to add space management to a file system whose path
contains non-local elements.

System action:

Processing stopped.

User response:

File system must be entirely local.

------------------------------------------------------------------------
ANS9554E

program-name: command for file system mountdir Reason : error



Explanation:

An attempt to enable or disable xdsm api functionality on the file
system failed. If the attempt was to enable HSM, then HSM is not enabled
for this file system.

System action:

Processing continues.

User response:

The file system must be of type JFS2 in order for the Space Management
to successfully set the managed attribute. Verify that the file system
is of the correct type.

------------------------------------------------------------------------
ANS9556E

Number of CTL files on disk (number of CTLs on disk) do not match the
expected value (number of CTLs in cache).



Explanation:

The number of CTLs files counted in VCM lib cache should be equal to
that in the local disks.

System action:

Processing is aborted.

User response:

None.

------------------------------------------------------------------------
ANS9576E

Not enough space in filesystem to create meta data file!At least space
space required!



Explanation:

A disk full error occurred attempting to create the metadata file.
Please migrate some files in filesystem to free at least space kb.

System action:

Processing stops.

User response:

None.

------------------------------------------------------------------------
ANS9577E

An exception "msg"!Unable to use meta file!



Explanation:

An internal error occurred. The dsmscout is unable to use the meta data
file!

System action:

Processing stops.

User response:

None.

------------------------------------------------------------------------
ANS9578E

An unknown error occurred!



Explanation:

An internal error has occurred. The dsmscout is unable to use the meta
data file! The file has been deleted. A new meta data file will be
created.

System action:

Processing stops.

User response:

None.

------------------------------------------------------------------------
ANS9590E

The SOAP error information: message failed, reason: message



Explanation:

The detailed SOAP error message is created from gSOAP communication
module and does not exist in the chosen language!

System action:

Processing continues.

User response:

Verify your system and retry the operation.

------------------------------------------------------------------------
ANS9591E

A SOAP UDP connection error has happened!



Explanation:

The SOAP communication system had an UDP error. Please see errorlog file
for more detailed information!

System action:

Processing ends.

User response:

None.

------------------------------------------------------------------------
ANS9592E

A SOAP TCP connection error has happened!



Explanation:

The SOAP communication system had an TCP error. Please see errorlog file
for more detailed information!

System action:

Processing ends.

User response:

None.

------------------------------------------------------------------------
ANS9593E

A SOAP HTTP communication error has happened!



Explanation:

The SOAP communication system had an HTTP error. Please see errorlog
file for more detailed information!

System action:

Processing ends.

User response:

None.

------------------------------------------------------------------------
ANS9594E

An internal SOAP error has happend!



Explanation:

The SOAP communication system had an internal error. Please see errorlog
file for more detailed information!

System action:

Processing ends.

User response:

None.

------------------------------------------------------------------------
ANS9595E

The SOAP communication system is out of memory!



Explanation:

The SOAP communication system had an memory error. Please see errorlog
file for more detailed information!

System action:

Processing ends.

User response:

None.

------------------------------------------------------------------------
ANS9596E

The SOAP communication ended unexpected!



Explanation:

The SOAP communication system had an EOF error. Please see errorlog file
for more detailed information!

System action:

Processing ends.

User response:

None.

------------------------------------------------------------------------
ANS9613E

program-name: Stub size of stubsize bytes is not supported on
filesystem.



Explanation:

The given stub size value not a multiple of the file system block size
and cannot be supported.

System action:

The program aborts the operation.

User response:

Use a correct stub size.

------------------------------------------------------------------------
ANS9616E

program-name: cannot get migration information for migrated-file-alias
on file-system-name



Explanation:

Space management cannot access the specified file system object using
the system DMAPI functions. This condition might occur if DMAPI support
is not enabled for the file system, or if there is an inconsistency in
the file system. This message is typically preceded by other messages
that have more specific information about the error.

System action:

Processing of the file is interrupted. Processing continues with the
next file.

User response:

Review dsmerror.log for preceding messages that might have more specific
information about the error. Verify that the file system is consistent
and mounted with DMAPI support enabled. Then retry the operation. If the
problem persists, contact IBM technical support for further assistance.

------------------------------------------------------------------------
ANS9618W

The mount point of HSM managed file system has been changed from 'old
mount point' to 'new mount point'.



Explanation:

The mount event of HSM managed file system on a different mount point
has been received.

System action:

The dsmrecalld master process is going to proceed with mounting of the
HSM managed file system.

User response:

Ensure that the HSM file space is renamed on the IBM Spectrum Protect
server in accordance with the new HSM managed file system mount point.
Otherwise, a subsequent reconciliation job will report all previously
migrated files (if any) as orphans.

------------------------------------------------------------------------
ANS9645W

The vApps backup operation completed. However, one or more vApp backups
failed.



Explanation:

There were successfull vApp backups but there were backup failures as
well. The operation is considered successfull.

System action:

The backup operation completed successfully.

User response:

Check the console output and error logs for information about why the
backups failed. Correct any issues and try backing up the failed vApps
again.

------------------------------------------------------------------------
ANS9669W

program-name: file-system CFI is out of range.



Explanation:

IBM Spectrum Protect CFI is out of range on the specified file system.
The scout daemon could not insert a new file entry into the CFI during
the file system scan. As a result, it may not provide enough candidates
for the next automigration.

System action:

Processing continues.

User response:

Please, reconsider the MAXFILES option setting for the file system. The
CFI size should likely be increased via 'dsmmigfs update /fs
-MAXFiles=n' command.

------------------------------------------------------------------------
ANS9674W

One or more of the required vApps could not be retreived.



Explanation:

Not all of the vApps that were required by the given specification could
be retreived. This can be caused by a change in the vCD vApps definition
or a user mistake in the provided vApp spec.

System action:

The operation will proceed, as there are still existing items to operate
on.

User response:

Check the provided vApps specification to make sure the specification
matches the existing configuration. Correct any issues and try the
operation again.

------------------------------------------------------------------------
ANS9733E

File: File-name excluded by the Include/Exclude list



Explanation:

You tried to back up the named file-name that was specified to be
excluded from backup.

System action:

IBM Spectrum Protect did not back up the file.

User response:

Specify the file using the Include option and retry the operation.

------------------------------------------------------------------------
ANS9778E

Error(s) were detected in options file: '' Do you want IBM Spectrum
Protect to comment out the line with errors and continue?



Explanation:

Invalid options or option values were encountered while reading the
options file.

System action:

This message is displayed. Further action depends on your response.

User response:

Click "Yes" to allow the process to turn the invalid line into comments.
If you click "No", you will exit immediately.

------------------------------------------------------------------------
ANS9779E

Unable to open options file '' for writing.



Explanation:

An error occurred while tried to open options file for writing to update
it.

System action:

Program exits.

User response:

Check file and directory access permissions or correct invalid entries
in your options file manually.

------------------------------------------------------------------------
ANS9780I

The vCenter does not have NSX-T setup, the virtual machine NIC cannot be
restored. Use the VMDEFAULTNETWORK option to define the network to
create the NIC in.



Explanation:

The virtual machine NIC was defined as an opaque NSX-T device and NSX-T
can not be found in the location the virtual machine is being restored
to.

System action:

The virtual machine can be restored but the NIC cannot be restored.

User response:

After the virtual machine has been restored a new NIC card can be added.

------------------------------------------------------------------------
ANS9782S

The selected backupset was generated by a newer version of the backup
server, and the new backupset version is not supported by this client;
The backupset data cannot be restored by this version of the client.



Explanation:

The backupset you are attempting to restore was generated by a newer
server that has a different level of functionality. The client you are
using does not recognize this newer format so it cannot restore the data
from the backupset.

System action:

Processing stopped.

User response:

Restore the backupset with a client that is at the same or higher level
as the server that was used to generate the backupset.

------------------------------------------------------------------------
ANS9806W

The file system type is not supported.



Explanation:

The file system is not a type supported by space management.

System action:

Unable to add space management to the file system.

User response:

There is a mismatch between the HSM client and the file system type
specified. If the file system type is consistent with the intent,
install an HSM client that supports it, then try the operation again.
Only one HSM client can be installed at a time.

------------------------------------------------------------------------
ANS9807W

The specified backupset file does not contain a backupset of type "file"
for the specified nodename.



Explanation:

Local backupset support is limited to backupsets that contain file data;
Image backupsets are not supported locally. The specified backupset does
not contain a backupset with file data for the node name specified.

System action:

Processing stopped.

User response:

Specify a different backupset file to restore file data from a
backupset. To restore an image from a backupset, access the backupset
from a IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS9827W

Error accessing the Recall daemon lock file: file name.



Explanation:

There is a problem accessing the recall daemon lock file.

System action:

Unable to determine if the recall daemon is running. Because the recall
daemon is needed to perform file recalls, the recall fails.

User response:

Check with the system administrator. The recall process needs read
access to the /etc/adsm/SpaceMan/dsmrecalld.pid file.

------------------------------------------------------------------------
ANS9828W

File: file-name is skipped for migration: The file is either AFM
uncached or dirty.



Explanation:

If using GPFS Active file management, the file could either be uncached
or dirty. Uncached (no file data available in cache. Access would cause
replication from home) Dirty (changed file data in cache. No valid
replication in home)

System action:

The file is skipped from processing.

User response:

Uncached (fetch the file from home to cache and rerun the processing)
Dirty (replicate the file from cache to home and rerun the processing)

------------------------------------------------------------------------
ANS9829W

Recall daemon is not running.



Explanation:

The recall daemon is not running.

System action:

IBM Spectrum Protect recall fails.

User response:

Ask the system administrator to start a recall daemon by issuing the
dsmrecalld command.

------------------------------------------------------------------------
ANS9842E

The watch daemon is not running properly.



Explanation:

The watch daemon is either not running, has no dmapi session, or is not
connected to group services.

System action:

The IBM Spectrum Protect action fails.

User response:

Ask the system administrator to check GPFS, the group services, and to
restart a watch daemon by issuing the dsmwatchd command.

------------------------------------------------------------------------
ANS9845E

Space management action ends.



Explanation:

The requested space management operation is ended because the watch
daemon is not working properly.

System action:

Processing Ends.

User response:

Look for previous messages.

------------------------------------------------------------------------
ANS9849W

Local backupset cannot be expanded; Only full backupset restore is
supported locally.



Explanation:

Local backupsets cannot be expanded to show volumes, directories, and
files. Only full backupset restore is supported from local backupsets.

System action:

Processing stopped.

User response:

To restore specific volumes, directories, and files from a backupset,
restore the backupset from the IBM Spectrum Protect server.

------------------------------------------------------------------------
ANS9850E

Tape read error; Max Blocksize is blocksize. Attempted to read blocksize
blocksize. Run dsmmaxsg to update scsi driver max blocksize allowed and
retry operation.



Explanation:

An attempt to read from tape at the specified blocksize failed; Tha
maximum blocksize allowed for the scsi driver is shown.

System action:

Processing stopped.

User response:

If the maximum blocksize is less than the blocksize used by the
operation, run the dsmmaxsg utility to update the maximum blocksize
allowed for the scsi driver, and then retry the operation. If the
maximum blocksize is greater than or equal to the blocksize used, then
verify that the tape installed and operating correctly and retry the
operation.

------------------------------------------------------------------------
ANS9857W

The restored HSM for Windows stub file may be an orphan: stub file name



Explanation:

The restored stub file may not be accessible in the HSM client archive
and thus it possibly cannot be recalled.

System action:

Stub file is restored.

User response:

Check if the stub file can be accessed.

------------------------------------------------------------------------
ANS9858E

The backup-archive operation did not run. The backup-archive operation
involves stub files that were migrated with the HSM for Windows client.
The installed HSM for Windows client version version. release. level is
incompatible with installed backup-archive client version version.
release. level.



Explanation:

The backup-archive client uses the HSM for Windows client for
backup-archive operations that involve migrated files. The HSM for
Windows client and the backup-archive client must be at the same PTF
level.

System action:

The backup-archive operation does not run for any files. Migrated files
and resident files are not processed.

User response:

Uninstall the current HSM for Windows client and install an HSM for
Windows client at the same PTF level as the backup-archive client.

------------------------------------------------------------------------
ANS9890W

program-name: The file system filesystem is already owned by that node.



Explanation:

The file system is already owned by that node..

System action:

None.

User response:

None.

------------------------------------------------------------------------
ANS9891E

The release file for the Linux mount proxy node cannot be validated. A
common reason is that the Linux distribution is not supported.



Explanation:

IBM Spectrum Protect examines the Linux release file on the mount proxy
node to determine if the mount proxy node is running on a supported
Linux distribution. Either the release file for a supported Linux
distribution could not be found, or the release file content could not
be validated.

System action:

The operation stops.

User response:

Check the product requirements for the installed version of IBM Spectrum
Protect to ensure that the Linux distribution is supported for use as a
mount proxy node.

------------------------------------------------------------------------
ANS9892E

Unable to find snapshot(s) in the local repository.



Explanation:

The requested volume snapshot(s) were not found in the local repository.

System action:

Processing stops.

User response:

Ensure the operation is issued with the proper nodename and/or server
address. In a non-cluster environment perform the operation from a
different host with the expected hostname. Retry the operation.

------------------------------------------------------------------------
ANS9895W

Space management in file system file system is not active.



Explanation:

You tried to select a file in a file system for which space management
is inactive.

System action:

The process continues with normal operation.

User response:

Reactivate space management for the file system, and then proceed with
selecting files.

------------------------------------------------------------------------
ANS9910E

The stream of data to backup guest vm name was sent in the wrong order.
The backup cannot continue.



Explanation:

The backup verification system detected the stream of data of the
virtual machine was being sent to the server in the wrong order. The
backup has ended to prevent data loss.

System action:

The backup operation for this VM ends.

User response:

Try the backup again. If the error persists, contact IBM Software
Support.

------------------------------------------------------------------------
ANS9911E

The backup verification system detected that some data was not sent
during the backup of virtual machine vm_name. The backup has been
halted.



Explanation:

The backup verification system detected that some data on one of the
objects sent to the server is missing. The backup has been halted to
prevent data loss.

System action:

The backup operation for this virtual machine ends.

User response:

Try the backup again. If the error persists, contact IBM Software
Support.

------------------------------------------------------------------------
ANS9912E

An error occurred when attempting to create a VMware vSphere Virtual
Volume (VVol) object. This could be the result of an incompatibility
between the virtual machine and the datastore or insufficient available
storage space.



Explanation:

An error occurred when attempting to create an object in a VVol
datastore.

System action:

The operation fails.

User response:

Specify a different destination datastore and retry the operation.

------------------------------------------------------------------------
ANS9913W

The VM backup operation that uses SAN transport mode failed.



Explanation:

This issue typically occurs when the data mover that specifies the SAN
transport mode does not have SAN access to the VMware datastore.

System action:

The operation fails.

User response:

Specify a different transport mode and retry the operation.

------------------------------------------------------------------------
ANS9914W

The VM backup operation may fail because SAN transport mode is not
supported for vVol datastores.



Explanation:

The data mover specifies the SAN transport mode. This transport mode is
not supported in an environment that contains VMware Virtual Volume
(Vvol) datastores.

System action:

The operation fails.

User response:

Specify a different transport mode and retry the operation.

------------------------------------------------------------------------
ANS9915E

The guest vm name is missing expected data files from the previous
backups. The backup operation continues based on the setting of the
VMVERIFYAction option.



Explanation:

During the verify operation, the number of data files that were found on
the server are insufficient to match the requirements of the control
files.

System action:

The backup operation for this VM continues based on the setting of the
VMVERIFYIFAction option.

User response:

Run a full VM backup for this virtual machine. Or, specify the
VMVERIFYAction option to force a full VM backup.

------------------------------------------------------------------------
ANS9916I

VMCUSER does not have one or more required vSphere privileges to
create/update/cancel Tasks in vSphere related to this operation. The
operation will continue.



Explanation:

VMCUSER does not have one or more required vSphere privileges to
create/update/cancel Tasks related to this operation. This is
informational only and does not affect the Backup/Restore operation.

System action:

A Task related to this operation may not show up in the vSphere Client
due to missing privileges. The operation will continue.

User response:

The vSphere Task provides additional information about IBM Spectrum
Protect initiated VM Backup/Restore operations including progress as
well as the ability to cancel these tasks from the vSphere Client.
Please refer to the 'VMware vCenter Server user privilege requirements'
section of the 'IBM IBM Spectrum Protect for Virtual Environments: Data
Protection for VMware User's Guide.'

------------------------------------------------------------------------
ANS9917E

Size estimates that correspond to the expected control files for vm name
do not match.



Explanation:

During the verify operation, the control files that were found on the
server do not match the expected size estimate of the data files for one
or more disks.

System action:

The backup operation for this VM continues based on the setting of the
VMVERIFYIFAction option.

User response:

Run a full VM backup for this virtual machine. Or, specify the
VMVERIFYAction option to force a full VM backup.

------------------------------------------------------------------------
ANS9918E

Cannot open migration candidates list for file-system.



Explanation:

Cannot access the migration candidates list for the specified file
system.

System action:

The system continues normal operation.

User response:

Select OK to return.

------------------------------------------------------------------------
ANS9919E

Failed to find the expected control files for vm name.



Explanation:

During a verify operation, the number of control files that were found
on the server do not match the expected amount for one or more disks.

System action:

The backup operation for this VM continues based on the VMVERIFYIFAction
option.

User response:

Perform a full VM backup for this virtual machine or specify the
VMVERIFYAction option to force a full VM backup.

------------------------------------------------------------------------
ANS9920W

Forcing a full vm backup for vm name.



Explanation:

During a verify operation, the number of control files that were found
on the server do not match the expected amount for one or more disks. As
a result, a full VM backup is performed.

System action:

The backup operation for this VM is a full backup instead of an
incremental backup.

User response:

Ensure the VERIFYIFAction option is set to the wanted value.

------------------------------------------------------------------------
ANS9921E

Virtual machine disk, vm name (disk label), verification check failed
(size on disk/ ctl size). If the disk is on an NFS datastore and the
disk size was recently changed or the disk was moved from non-NFS
datastore to NFS datastore, the verification failure is expected and a
full backup is required.



Explanation:

During a verify operation, the number of control files that were found
on the server do not match the expected number for this disk. For disks
on NFS datastores: Because of how VMware processes disk size changes and
because the Change Block Tracking (CBT) QueryChangedDiskAreas API does
not support change ID "*", the backup operation cannot determine whether
the the disk size was changed, the disk was moved to NFS datastore or
some other error occurred.

System action:

The backup operation for this VM proceeds based on the VMVERIFYIFAction
option.

User response:

Perform a full VM backup for this virtual machine or specify the
VMVERIFYIFAction option to force a full VM backup.

------------------------------------------------------------------------
ANS9922I

VMVERIFYIFLatest is enabled for vm name (action: type).



Explanation:

This VM operation verifies the control files from the previous backup to
ensure that all expected files are on the server.

System action:

The operation proceeds based on the value of the VMVERIFYIFAction
option.

User response:

Ensure the VERIFYIFAction option is set to the wanted value.

------------------------------------------------------------------------
ANS9923W

Forcing a full backup for vm name.



Explanation:

The MAX capacity of MBLK is not enough for the disks in the incremental
backup. A full backup will be performed.

System action:

The backup operation for this VM is a full backup instead of an
incremental backup.

User response:

None.

------------------------------------------------------------------------
ANS9924W

A full backup for the vm name virtual machine will be performed because
of added disk capacity.



Explanation:

The disk capacity of the virtual machine has increased since the last
backup. A full backup and a Changed Block Tracking (CBT) reset will be
performed.

System action:

The backup operation for this virtual machine is a full backup instead
of an incremental backup.

User response:

No action is required.

------------------------------------------------------------------------
ANS9950W

Streaming and partial recall modes can not be set for files migrated
using external backend.



Explanation:

Streaming or partial recall modes are not supported for files in this
mode.

System action:

Operation aborted.

User response:

Special recall modes are only available for files migrated using IBM
Spectrum Protect Server as a backend.

------------------------------------------------------------------------
ANS9951I

File: file-name has already been migrated.



Explanation:

You tried to migrate a file that is already migrated. Note that you may
get this message if the file is hard linked with another, already
migrated file.

System action:

The file is skipped.

User response:

None.

------------------------------------------------------------------------
ANS9958E

File 'file-namefile-namefile-name has not yet reached the age for
migration. File skipped.



Explanation:

This file cannot be migrated because it has not yet reached the age for
migration.

System action:

The file resides in state resident.

User response:

The minimal age of a file to be eligible for migration is two minutes.
Retry the migration operation after two minutes or use processing option
HSMENABLEIMMediatemigrate YES to force the migration.

------------------------------------------------------------------------
ANS9959W

IBM Spectrum Protect acceptor received a non-critical network error
errno, IBM Spectrum Protect return code : TSM-rc.



Explanation:

The communication problem happened while listening for inbound
connection but the IBM Spectrum Protect acceptor continues running.

System action:

Processing continues.

User response:

No further action is required, it can be safely ignored.

------------------------------------------------------------------------
ANS9984W

PFR plugin library was not found.



Explanation:

PFR plugin library should have been installed when the client was
installed, but it cannot be found.

System action:

The selected operation is not performed.

User response:

None.

------------------------------------------------------------------------
ANS9987W

Partial recall mode is not set for full-file-name



Explanation:

Partial recall mode is not set for the specified file.

System action:

The recall is not performed for the specified file. Processing stopped.

User response:

Set the partial recall mode on the file ("dsmattr
-recallmode=partialrecall" command) and re-try the operation.

------------------------------------------------------------------------
ANS9989W

Management class mcName specified on the INCLUDEstatement in file-name
at line line-number does not exist.



Explanation:

Management class named on the INCLUDE statement in the file-name file
does not exist in your assigned policy set on the server.

System action:

The object is bound to the default management class.

User response:

*  Update the INCLUDE statement so that it specifies a valid management
   class.

*  Define the management class named on the INCLUDE statement (if it is
   intended to have a management class with that name).

*  Verify that the node is in the correct policy domain (perhaps the
   node was accidentally put in the wrong policy domain, and the correct
   domain has the management class).

*  Remove the INCLUDE statement if it is no longer necessary to bind the
   files to the management class.

------------------------------------------------------------------------
ANS9990W

Management class mcName specified on INCLUDE statementin client option
set does not exist.



Explanation:

Management class named on the INCLUDE statement in client option file
does not exist in your assigned policy set on the server.

System action:

The object is bound to the default management class.

User response:

*  Update the INCLUDE statement so that it specifies a valid management
   class.

*  Define the management class named on the INCLUDE statement (if it is
   intended to have a management class with that name).

*  Verify that the node is in the correct policy domain (perhaps the
   node was accidentally put in the wrong policy domain, and the correct
   domain has the management class).

*  Remove the INCLUDE statement if it is no longer necessary to bind the
   files to the management class.

------------------------------------------------------------------------
ANS9992E

The following options must be set before running this operation: VMCHOST
or VMCUSER.



Explanation:

VMCHOST or VMCUSER is missing from the options file.

System action:

Operation cannot continue without options being set.

User response:

Manually edit the options file or use the preferences editor to set
these options.

------------------------------------------------------------------------
ANS9993E

Not able to override options.



Explanation:

The process can not override the options.

System action:

The command is not processed.

User response:

None.

------------------------------------------------------------------------
ANS9994W

Can not get response message, timeout reached.



Explanation:

The timeout was reached before getting response message. The option
override could be successful.

System action:

The command processed.

User response:

None.

------------------------------------------------------------------------
ANS9995W

The value of the VMMAXBACKUPSESSIONS option is 'ivmMaxBackupSessions'.
This value must be greater than or equal to the value of the
VMMAXPARALLEL option, which is 'ivmMaxParallel'.The value will be set to
the value of the VMMAXPARALLEL option.



Explanation:

The number of server sessions that are specified by the
VMMAXBACKUPSESSIONS option must be equal to or greater than the number
of virtual machines that are specified by the VMMAXPARALLEL option.

System action:

The operation continues.

User response:

Set the value of the VMMAXBACKUPSESSIONS option to a value that is
greater than or equal to the value of the VMMAXPARALLEL option.

------------------------------------------------------------------------
ANS9996W

The node has exceeded the maximum tape mounts that are allowed. No new
sessions will be added for 'vm-name'.



Explanation:

The node has exceeded the maximum tape mounts that are allowed. No new
sessions will be added for the backup VM.

System action:

The backup operation continues.

User response:

Use the MAXNUMMP parameter for the UPDATE NODE command on the server to
increase the number of allowed tape mounts for this node.

------------------------------------------------------------------------
ANS9997W

The dsmwatchd daemon failed to register failover mode: 'failover-mode'
on nodeID: 'node-ID'.



Explanation:

The dsmwatchd daemon was unable to register an appropriate HSM failover
callback on the mentioned node.

System action:

The dsmwatchd daemon operation continues without HSM failover support.

User response:

To register the HSM failover callback, restart the dsmwatchd daemon on
the affected node: - on AIX: run "kill -15 dsmwatchd_pid" command; - on
Linux: run "systemctl restart hsm" command.

------------------------------------------------------------------------
ANS9998W

The DMAPI dm_punch_hole() function failed to discard local file data
blocks during migration of 'file-name' file.



Explanation:

The migration operation succeeded, but it was unable to discard the file
local file data blocks due to a DMAPI dm_punch_hole() function issue. As
a result, the file system occupation didn't change upon such a
migration.

System action:

The migration operation continues.

User response:

To re-stub the file, perform a subsequent normal recall operation,
followed by one more migrate operation. If the cause of this message can
not be determined or resolved, contact your support representative.

------------------------------------------------------------------------
ANS9999E

():



Explanation:

This message carries diagnostic text relating to a client process or
algorithm. This information is intended for reporting processing
exceptions and other non-standard situations that occur on the IBM
Spectrum Protect client. The (component), (code), and (text) will vary
depending upon the cause of the message and the client process or
algorithm that issues the message.

System action:

Client processing may or may not continue depending upon the cause of
this message.

User response:

Examine error messages that may have been displayed before and/or after
this message and correct any problems, if possible. If the cause of this
message can not be determined or resolved, contact your support
representative. If you contact your support representative, the entire
text of this message should be reported.