II. MARCO TEÓRICO
2.5. Marco Teórico
2.5.2. Fundamentación Teórica de la Investigación
2.5.2.5. Aspectos esenciales sobre Espacios Urbanos
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 Tivoli Storage Manager server was not added to the multi-server environment. There are several causes for this error:
v The file system is not managed by HSM. v The HSM management is not active for the file
v The file system is out of space.
v The default IBM Tivoli Storage Manager server for
the file system was not yet added to the multi-server environment.
v The IBM Tivoli Storage Manager 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 Tivoli Storage Manager server was not added to the multi-server environment. There are several causes for this error:
v The file system is not managed by HSM. v The HSM management is not active for the file
system.
v The IBM Tivoli Storage Manager server is the default
server for the file system and must be removed last.
v The IBM Tivoli Storage Manager 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 Tivoli Storage Manager server ('default-server-name') for this file system.
Explanation: The requested IBM Tivoli Storage Manager server was not added to the multi-server environment. The requested IBM Tivoli Storage Manager server is not the default server for the file system.
System action: HSM multi-server processing stops.
User response: Add the default IBM Tivoli Storage Manager server first.
ANS2159I The server 'server-name' was added to the environment.
Explanation: The requested IBM Tivoli Storage Manager 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 Tivoli Storage Manager 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 Tivoli Storage Manager server for this environment.
Explanation: The requested IBM Tivoli Storage Manager 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 Tivoli Storage Manager server name.
ANS2162E HSM cannot be removed from the file system. The IBM Tivoli Storage Manager 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 Tivoli Storage Manager servers from the multi-server list before removing HSM.
ANS2163E The default IBM Tivoli Storage Manager server ('server-name') for the file system will be removed.
Explanation: The default IBM Tivoli Storage Manager server will be removed. The IBM Tivoli Storage Manager 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 Tivoli Storage Manager server was removed from the multi-server environment.
System action: HSM multi-server processing continues.
ANS2166I The IBM Tivoli Storage Manager server 'server-name' is not included in the multi-server environment. Explanation: The requested IBM Tivoli Storage Manager 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 Tivoli Storage Manager 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 Tivoli Storage Manager 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 Tivoli Storage Manager 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 Tivoli Storage Manager 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 TSM 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 TSM 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 TSM 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 TSM 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 TSM Journal Engine setup wizard. The "baclient" and "config" directories can be found in the directory where you installed the Tivoli Storage Manager 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 Optionprimary 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 Tivoli Storage Manager Administator, sent to the client during logon, and are saved to the options file.
System action: Processing continues.
User response: None.
ANS2182I Optionsecondary 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 Tivoli Storage Manager 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.
ANS2186E Failed to log on to the vCloud Director on 'vCD host name' with user name 'vCD user name': User not found.
Explanation: The vCloud user specified by the VCDUser option does not exist on the vCloud Director.
System action: vCloud operations cannot be performed.
User response: Update the the VCDUser option with a valid vCloud user name 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.
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 TSM for Virtual Environments vCloud runtime library is installed. If neccessary, reinstall TSM 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 TSM client uses an VSS staging directory to store files related to to VSS snapshot operations. The TSM client was unable to create this directory structure.
System action: The TSM 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 TSM administrator for more information.
ANS2196W An incompatible disk configuration is detected. Individual SQL Database Restore of database 'database name' 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.
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 TSM 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 upout ofnumber of VMs in vAppVMs 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.
ANS2199W The virtual machine 'VM-name' contains one or more disks that are larger than the currently supported size so the individual disks will be excluded. Explanation: The virtual machine contains disks larger than the currently supported size so the individual
System action: The backup will continue without the larger disks.
User response: None.
ANS2200I ***** Filling Cachecountfiles ***** Explanation: TSM the specified number of files have been added to the disk cache.
System action: Processing continues.
User response: None.
ANS2201I ***** Inspecting Cachecountfiles ***** Explanation: TSM 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. TSM.
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.. TSM.
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.
ANS2213E Error while querying volume properties of volumevolserial. Please verify that the volume specified in the target volumes file exists.
Explanation: None.
System action: Processing stops.
User response: Contact the TSM administrator with the information provided in this message.
ANS2218I The encryption key password for node
node nameand serverserver namehas been migrated.
Explanation: The format of the TSM password file has