IBM Troubleshooting Operations Center client updates
ii Troubleshooting Operations Center client updates
Contents Troubleshooting Operations Center client updates............ 1 iii
i Troubleshooting Operations Center client updates
Troubleshooting Operations Center client updates Complete the following steps to troubleshoot client update issues: 1. Ensure that the configuration requirements are met. For information about client requirements, serer requirements, and restrictions, see Scheduling client updates. 2. In the Operations Center, use the following pages to monitor client updates and identify issues: Scheduled Updates page (Updates > Scheduled) In the Status column, hoer oer failed updates to iew details. See the online help for further explanation. In the Target column, use the ersion number to determine whether a client was successfully updated. Clients page In the Last Access column, use the date and time to determine whether a client is still connecting to the serer as expected. Serer Details page Click the Actie Tasks or Completed Tasks tab and filter by the client name to iew status details for the update processes. 3. Reiew the serer actiity log for detailed error messages. For more information, see Table 1 on page 4. 4. Reiew the following client log files: Backup-archie client scheduler log (dsmsched.log) Setup log (setup.log) Update manager log (updatemgr.log) Update manager trace (trace.txt) Installation log (installba.lob - Windows only) The following scenarios describe how to troubleshoot specific client update issues: Scheduled updates fail Symptoms The schedule status is Failed. The detailed result is Requires. The backup-archie client no longer functions. Troubleshooting steps 1. In the Operations Center, open the Completed Tasks page for the affected serer (Details > Completed Tasks). Filter on the client name and reiew the complete sequence of messages from the update manager processing. 2. On the client system, reiew the update manager log files for additional details. 3. (Windows only) Look for message ANE4210 in the serer actiity log and e the Microsoft installer error code. The following IBM Tioli Monitoring (ITM) serice can preent client updates from completing successfully: 1
Monitoring Agent for Windows OS - Watchdog If the serice is running on the client system, the update fails with one of the following error messages: Error 13003.The installer has insufficient priileges to access this directory: C:\ProgramData\IBM\CAP. ANS4210E The Deployment Manager failed to install package: Backup-Archie Client. The Microsoft Installer error code was 1603 For instructions about temporarily disabling this serice, see Using Agent Management Serices. 4. (Windows only) Reiew the installation log file (installba.log) for more details. 5. After correcting the issues, manually install the new client. The updated client does work (Windows only) Symptoms The schedule status is Success. The detailed result is Success. The backup-archie client does function properly. Troubleshooting steps 1. Verify that the autodeploy client option has a alue of yes. This is the default setting. 2. Reiew the serer actiity log. Message ANE4230 indicates that the update manager initiated a reboot for the client system. 3. Check the system eent log on the client computer. A warning eent can indicate that the reboot was interrupted. Manually restart the client system to complete the update installation. The update succeeded but Symptoms The schedule status is Requires. The detailed result is Success. Troubleshooting steps The update did complete Symptoms 1. Check the serer actiity log for the ANE4297 message. This message contains one or more of the following reason codes: ANE4234: Indicates that support for one or more languages was installed successfully. ANE4212: Indicates that the client serice was restarted. The schedule status is Not. The detailed result is Stopped. Troubleshooting steps 2 Troubleshooting Operations Center client updates 1. Check the serer actiity log for the ANE4298 message. This message contains one or more of the following reason codes: ANE4213: Indicates that the autodeploy parameter is set to noreboot and a reboot is required. Reschedule the update at a different time or set autodeploy parameter to yes. ANE4215: Indicates that the upgrade path is supported.
Deployment does start Symptoms ANE4248: Indicates that the client is already at the target leel. Reiew the current and target ersions and reschedule with a different target ersion. ANE4232: Indicates that an installation image is missing. Check the client scheduler log for errors when the installation packages were retrieed. After correcting the issue, reschedule the update. ANE4206: Indicates that an error occurred when extracting installation images. Ensure that there is sufficient disk space. Also check the client scheduler log for errors when the installation packages were retrieed. After correcting the issue, reschedule the update. ANE4253: Indicates that there is enough disk space aailable. After correcting the issue, reschedule the update. ANE4221: Indicates that there is an architecture mismatch. The schedule status is Unknown. No additional details are aailable in the serer actiity log. Troubleshooting steps Actiity log messages 1. Reiew the serer actiity log to see if the schedule was processed. If, change the schedmode client option to prompted to immediately process schedules. 2. If the schedule was successfully processed, wait a few minutes and check the deployment status again. 3. Reiew the scheduler log of the backup-archie client. Look for errors related to the retrieal of installation images. For example, errors indicating that there is enough disk space aailable. 4. Reiew the setup.log file on the client system for the following messages: ANE4225: Indicates that the client password was generated properly. ANE4250: Indicates that there is aher update manager running on the same system. Only one instance can be actie at a time. ANE4253: Indicates that there is insufficient disk space aailable. ANE4252: Indicates that the update manager missed the start time. If the client node is configured to send messages to the serer, you can iew error messages in the IBM Spectrum Protect serer actiity log. Use the following table to map the schedule status to the update manager messages. Troubleshooting Operations Center client updates 3
Table 1. Map schedule status to update manager messages Schedule status Detailed result Update Manager message Reason code description User action Success Success ANE4300 No action required. No action required. Failed Failed - Failed Failed - Failed Failed - Failed Failed - Failed Failed - Success Warning - Reboot required Warning - ANE4299 with reason code ANE4210 (Windows) ANE4263 with reason code ANE4210 ANE4264 with reason code ANE4210 ANE4207 ANE4242 ANE4297 with reason code ANE4242 or ANE4212 ANE4295 (Windows) ANE4274 ANE4213 (Windows) ANE4210 Installation of client failed with an MSI error code. ANE4263 The update manager failed to uninstall the backup-archie client. ANE4264 The update manager failed to install the backup-archie client. ANE4207 The update manager failed to initiate the final connect to the serer with the updated BA client. ANE4242 The setup script encountered a warning or error while retrieing the client package. ANE4242 There was an error retrieing the client package. The upgrade failed. ANE4212 The update manager failed to restart the client scheduler or client acceptor daemon. No action required. ANE4274 The update manager can stop the scheduler or the CAD processes. ANE4213 The client option autodeploy=noreboot was detected. Automatic restart of the client computer is required. Inestigate MSI error. Manually uninstall and reinstall the new client. Reiew the update manager log and trace files on the client workstation for more details about the error. You might hae to manually uninstall the client. Reiew the update manager log and trace files on the client workstation for more details about the error. Manually install the new client after the issue is resoled. Log in to the backup-archie client system and reiew the backup-archie client error log file. Ensure that client packages for all architectures are aailable on the serer. Log in to the backup-archie client system and reiew the backup-archie client error log file. Ensure that client packages for all architectures are aailable on the serer. Reiew the backup-archie client error log for more detailed error messages. Resole any network connection problems between the client and serer. Restart the client system. Reschedule the client update. Restart the client system. 4 Troubleshooting Operations Center client updates
Table 1. Map schedule status to update manager messages (continued) Schedule status Detailed result Update Manager message Reason code description User action ANE4220 (Windows) ANE4215 ANE4248 ANE4260 ANE4259 ANE4273 (Linux) ANE4276 ANE4271 ANE4232 (Windows) ANE4220 The update manager is unable to determine whether any IBM Spectrum Protect processes are running. ANE4215 The upgrade path is supported. ANE4248 The client is already at the target leel. ANE4260 The installation file system is writable. ANE4259 The client scheduler is started as a root user. ANE4273 The update manager detected a journal-based backup (JBB) client on the workstation where it must deploy the backup-archie client. ANE4276 The update manager can obtain information about the scheduler or the CAD processes. ANE4271 The update package is missing one or more required installation image files. ANE4232 Windows self-extracting installation image can be found. Enable the automatic restart function by setting autodeploy=yes in the schedule definition. Restart the client update. See the IBM Spectrum Protect backup-archie client documentation in the IBM Knowledge Center. Reschedule the client update. No action required. Reiew the installation file system permissions. It is possible that the current client node runs in a irtualized enironment using the client code installed in a shared storage of the physical enironment. Reschedule the client update with the client node in the physical enironment. Log in with the root user ID and start the client scheduler. Reschedule the client update. Uninstall the JBB client and reschedule the backup-archie client update. Log in to the backup-archie client workstation and reiew the error log file and the update manager error log file. Ensure that client packages are aailable on the serer. Reiew the backup-archie client error log file for more detailed error messages. Reiew the serer actiity log or the scheduler log on the client system. Reschedule the client update. Troubleshooting Operations Center client updates 5
Table 1. Map schedule status to update manager messages (continued) Schedule status Detailed result Update Manager message Reason code description User action ANE4206 ANE4253 ANE4206 The update manager receied an error while extracting from installation image. ANE4253 There was enough disk space on the client computer. Ensure that there is sufficient disk space on the client system. Make sure that all of the Windows self-extracting client images are alid. Reschedule the client update. Allocate the amount of free space that is required for the client software upgrade. Reschedule the client update. Client log files The default location of the client logs is shown in Table 2. Table 2. Default log file location Client Platform AIX Oracle Solaris x86_64 Oracle Solaris SPARC Linux on Power Systems Linux on Power Systems (little endian) Linux x86_64 Linux on System z HP-UX Itanium 2 Mac OS X Windows 64-bit Windows 32-bit Directory /usr/tioli/tsm/client/ibm_anr_unx/ppc/ deploy/log /opt/tioli/tsm/client/ibm_anr_unx/x86/ deploy/log /opt/tioli/tsm/client/ibm_anr_unx/ SPARC/deploy/log /opt/tioli/tsm/client/ibm_anr_unx/ppc/ deploy/log /opt/tioli/tsm/client/ibm_anr_unx/ PPCLE/deploy/log /usr/tioli/tsm/client/ibm_anr_unx/x86/ deploy/log /opt/tioli/tsm/client/ibm_anr_unx/390/ deploy/log /opt/tioli/tsm/client/ibm_anr_unx/ hp11ia64/deploy/log /Library/Application Support/tioli/tsm/ client/ibm_anr_mac/x86/deploy/log C:\Program Files\Tioli\TSM\IBM_ANR_WIN\ X64\deploy\log C:\Program Files\Tioli\TSM\IBM_ANR_WIN\ X86\deploy\log Log file locations for non-default installation locations for the Windows client If you did use the default installation directory when you installed the client, the log and trace data for the update operation is still copied to the IBM_ANR_WIN\X64\deploy\log or IBM_ANR_WIN\X86\deploy\log folder. This folder is created one directory leel up (../) from the installed location of the client executable files (dsm.exe, dsmc.exe, dsmcad.exe, and other files). 6 Troubleshooting Operations Center client updates
For example, if you originally installed the 64-bit client in the E:\IBM\Tioli\baclient directory, the log and trace files that result from the automatic update are created in E:\IBM\Tioli\IBM_ANR_WIN\X64\ deploy\log directory. Log file locations for non-default installation locations for other clients On AIX, Linux, Solaris, and HP-UX clients, when you define a schedule to deploy the client updates, you can specify a non-default retrieal target location. Specifying a non-default retrieal target location changes the location of the log and trace files. For example, the default retrieal target location for AIX is /usr/tioli/tsm/client/. If you specify /tmp/tioli/client as the target location, the log and trace files are created in the /tmp/tioli/client/ IBM_ANR_UNX/IBM_ANR_UNX/PPC/deploy/log directory. On the Mac OS X operating system, you can change the retrieal target location. The update manager's working directory is relatie to the working directory of the client scheduler. For example, if the user starts the client scheduler from the /mydir directory, the log and trace files are created in the /mydir/ibm_anr_unx/x86/log directory. Troubleshooting Operations Center client updates 7