IBM Tivoli Storage Manager V7. UNIX and Linux Backup- Archive Client known problems and limitations. If the passwordaccess generate is set in the client option file and if an invalid password is given at the first attempt during open registration with the client, the second attempt will fail as well. GPFS only: If a file is moved from one storage pool to another, the attributes of the files change and the ctime will be set. The ctime change causes a new backup of the file in the next backup run. Key database files match the following pattern: . The recommended way to delete the key database is to use following command: . Additionally, the Domain panel will not list the file systems to select for the domain option. The error dialog can be dismissed and the configuration wizard can be used without further error. Disk Thin Provisioning & its ease of use in VMware vSphere has been one of the most used features. Although Thin provisioning has allowed customers to avoid. After the intial configuration, use the preference editor to set the Domain option. Interrupt with CTRL- C During a command line client operation, pressing CTRL- C might result in a TSM client program exception or other unexpected behavior. To abort a command line client operation, press the 'Q' key instead of CTRL- C. StarWind Virtual SAN targets those who already have servers, or are bound to a particular vendor list to buy from. In case there is a new virtualization.Web Client tree expansion When using the Web Client, the browser can crash if you do the following, using the view menu item in the backup or restore tree window: Click on . Logfile out of space handling If any log file (dsmerror. End of processing return codes will reflect all errors and conditions, not just those we were able to log. To prevent this problem, set the ERRORLOGMAXSIZE (for dsmerror. SCHEDLOGMAXSIZE (for dsmsched. Note that using these options causes the log data that would exceed the maximum to be written at the beginning of the log, overwriting the oldest entries. ERRORLOGMAX and SCHEDLOGMAX behavior in out- of- space conditions: If the specified maximum error log file size is greater than the available free space on the specified file system and the log is being transitioned from a non- wrapped log to a wrapped log, the following error message will be issued: ANS1. E Failure writing to a Tivoli Storage Manager log or log- related file: < LOG FILE NAME> , errno = 2. There is not enough space in the file system This is correct behavior. However, the log header record might be incomplete or there may be no . After space has been made available, the TSM client will subsequently treat the log as unwrapped because a valid header record is not found. A new log will be created and this partial log will be written to the prune file. If there is insufficient space in the file system to append an entry to the log, the TSM client will continue to run, but the error message will not be logged. Some keywords have not been translated into Chinese for the backup- archive client: Some keywords, such as . This is most notably evident in the backup- archive client GUI. If client encryption is used and you choose to abort a command line backup or archive operation when prompted for an encryption key, the entire operation will immediately end with return code (RC) 1. When regional settings are updated in the Java GUI preference editor, the GUI needs to be restarted before the changes become effective. There are minor errors displaying ANS1. S in foreign languages: On all platforms Polish has an extra period on the second line, and on several platforms the format is incorrect. Handling spaces in file names in schedule definitions. When defining or updating a schedule objects parameter or the schedule options parameter with file specifications that contain blank spaces, use quotation marks around each file specification that contains blanks, then single quotes around all of the specifications. The following are some examples of proper usage of the objects parameter: For UNIX and Linux clients: objects=. Some examples of options parameter usage: options='- preschedulecmd=. Some examples of options parameter usage: options='- preschedulecmd=. Java GUI does not start with invalid option in options file In rare cases, when there is an error in the dsm. Java GUI will not start properly. The Java GUI will attempt to start, but at some point after 7. To work around the problem, refer to the dsmerror. Java GUI was issued for the offending option, and remove it manually from the options file. You should be able to restart the client without problems. Reset button does not function properly in Preference Editor Communications Panel On certain systems, the Communications panel in the Preference editor will not display correctly when the Reset button of the preference editor is invoked. When you click the Reset button, the list of communication methods might not display the proper list after the reset is complete. If there is a need to reset the communication panel back to the original settings, exit out of the preference editor and restart it. IMAGEGAPSIZE Option The value for the IMAGEGAPSIZE option should not be specified outside the listed ranges for MB and GB units. If it is, the client will not report it as an error. Select all after applying filter from Backup window After applying a filter to a directory in the Backup window, when you check the check box for this filtered directory, the corresponding files in the file view on the right are not checked (not selected). To select the files in that filtered directory, click on the name of the checked directory and the boxes next to the filtered files are checked. Connection Information dialog might not appear in certain situations The Connection Information dialog might not appear correctly in certain situations. An exception will be logged in the dsmj. This will occur when you do the following: 1. Change the password (Utilities - > Change Password). After successfully changing the password, click either the Backup, Restore, Archive, or Retrieve button. Attempt to open the Connection Information dialog (File - > Connection Information). Dsmagent can crash if it is killed during restore operation On Unix and Mac platforms, when TSM GUI (both Java and Web) is used to perform restore or retrieve operation and dsmj or dsmagent process is killed while the operation is still in progress, dsmagent can crash. There is no negative impact other than creating a core file. The recommended ways to terminate an application while an operation is in progress are either pressing the Stop button or cancelling the session by TSM administrator. NQR (no query restore) does not work for HSM (space managed) file systems, when the RESTOREMIGSTATE option is set to YES. Only classical restore is possible in this case. The Tivoli Storage Manager client will fail to perform snapshot- based image backup when mirror pool is enabled. The Tivoli Storage Manager client does not support mirror pools at the moment. Snapshot difference incremental backups are not supported for v. Filer volumes mounted using AIX NFS version 4. This problem is documented by Net. App BURT 6. 30. 20. Apply the fix for this once it is available from Net. App. If you perform snapshot difference incremental backup of N- Series or Net. App volumes, make sure that the volumes are defined with a security style of UNIX. TSM backups will complete successfully even if the security style is NTFS or MIXED. However, it is recommended that you use a security style of UNIX. During snapshot difference incremental backup of N- Series or Net. App volumes, if files are skipped due to any reason, such as TSM server media mount being unavailable, these files may not be backed up during subsequent backups either, unless the files have been modified. Such files will be logged to the TSM error log. You may back them up manually or perform a snapshot difference backup with the option . On AIX 6. 1, if the EFS user keystore password is different from the user login password, the EFS keystore is not automatically opened when the user logs in. In such a situation, the TSM client might fail to restore a non- EFS file into an EFS file system. If this happens, the user can either launch the TSM client with the efskeymgr - o command or synchronize the keystore password with the user login password with the efskeymgr - n command. For example: efskeymgr - o ./dsmjefskeymgr - n. When the NFS server corresponding to an NFS file system mounted on AIX is not reachable due to a network error or some other problem, the following error message is displayed on the console while performing TSM client operations: NFS getattr failed for server nfs. If you use the memoryefficient=diskcachemethod option for full incremental backup, you might need large amounts of disk space. Ensure that large file support is enabled on the file system that is being used for the disk cache file. AIX 6. 1 Encrypted File System (EFS) restore to an alternate destination might hang if the destination EFS file system runs out of disk space. To prevent this problem, apply the following AIX 6. APAR. 6. 10 (6. 1. IZ4. 23. 02 6. 1B (6. IZ4. 23. 01 6. 1D (6. IZ4. 23. 00 Incremental by date backups on AIX 6. Upgrade to the latest service pack for your AIX technology level as this problem has been resolved by AIX APAR IZ2. Resolving errors during AIX JFS2 snapshot based backup/archive and image backup: The TSM client supports snapshot based backup and archive operations to provide a consistent backup of files and online image backup by exploiting the integrated snapshot capability provided by JFS2. The TSM client deletes the AIX JFS2 snapshot created during the backup process during TSM termination. However, there are situations in which AIX may fail the snapshot delete request made by TSM. The following are some cases when a snapshot delete request might fail: 1. The user types Ctrl- C during a TSM snapshot backup process. In this case the JFS2 snapshot unmount request may fail with the . The user invokes two TSM snapshot backup requests concurrently for the same file system. For example: dsmc backup image /fs. In this case, if TSM process 1 from console 1 created the first snapshot for /fs. TSM process 2 from console 2 created the second snapshot for /fs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |