Marco Histórico

SRVOPTSETENCRYPTIONDISABLED has been set to YES on the client thereby preventing the TSM administrator from setting one of the following client options - ENCRYPTKEY GENERATE,

EXCLUDE.ENCRYPT, INCLUDE.ENCRYPT.

System action: The option will be ignored.

User response: None required.

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 ofnumber of VMs in vAppVMs 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.

ANS2231E Failed to back up vApp properties for vApp 'vApp name'

Explanation: A backup was not created for the specified vApp.

System action: Back up of the specified vApp stops. Processing continues to the next vApp.

User response: Check the dsmerror.log file for additional information.

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.

ANS2233E Failed to get information from the vSphere server for the VMs that compose vApp 'vApp name'.

Explanation: The VM information for the specified vApp was not retrieved from the vSphere server. This

failure might be caused by incorrect option settings.

System action: VMs for the specified vApps are not backed up. Processing continues to the next vApp.

User response: Make sure the VMCHost option specifies a vSphere host that belongs to the protected vCloud Director. Verify that VMCUser and VMCPW settings are correct. Also check the dsmerror.log file for information that is related to this issue.

ANS2236I The virtual machine 'VM-name' contains one or more disks that exceed the maximum size limit. These disks will be excluded from the backup.

Explanation: The IBM Tivoli Storage Manager client does not support backing up VMDKs that are greater than the supported limit.

System action: The virtual machine is backed up, however the disks exceeding the limit are skipped.

User response: Keep VMDKs below the maximum size limit to avoid having them skipped during VM backups. Alternatively, remove the

'-VMSKIPMAXVMDKS=yes' option to have VM backups fail if they contain VMDKs exceeding the size limit.

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.

ANS2239W The annotations field contained too many characters and had to be truncated.

Explanation: vSphere limits the size of the annotations to 2000 characters. Some special characters, such as new lines, get encoded as multiple characters. This can lead to exceeding the limit even though the size may appear to be within the limit.

System action: The annotation field is truncated to less than 2000 characters so that the vSphere API will not reject it.

User response: Take care to avoid creating large annotations that may exceed the 2000 character limit after special characters are encoded.

ANS2240T The basic verification of vApp 'vApp name' succeeded.

ANS2241T The extended verification of vApp 'vApp name' succeeded.

ANS2242E No nodes were found that matched the input specification:node specification

Explanation: An invalid node specification was entered.

System action: The operation was stopped.

User response: Check documentation how to specify nodes.

ANS2243W An incompatible disk configuration is detected. Individual SQL Database Restore of some databases on this guest VM is not supported.

Explanation: One or more SQL database files in this operation are located on Dynamic and/or Guid Partition Table (GPT) style disks. Individual SQL Database Restore is not supported from disks that are configured in this manner.

System action: Backup of the full VM continues.

User response: Issue a full VM restore to retrieve a previous state of the SQL Server environment.

ANS2244W The virtual machine contains one or more disks that exceed the maximum size limit. Specify the

'-VMSKIPMAXVMDKS=yes' option to exclude these disks from the backup. Explanation: The IBM Tivoli Storage Manager client does not support backing up VMDKs that are greater than the supported limit.

System action: The virtual machine is not backed up.

User response: Specify the

'-VMSKIPMAXVMDKS=yes' option to exclude these disks from the backup.

ANS2245E Virtual machine backups and restores are not supported on 32 bit data movers. 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 vAppvApp 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.

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 forVM-Name. Explanation: The TSM 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 objectVMnamefailed. 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 Commandwith -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