IBM E16RMLL-I Implementation Guide - Page 718
Server configuration considerations
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 718 highlights
Note for Tivoli Storage Manager for Databases, Data Protection for Oracle: The administrator must run the tdpoconf utility program to set the password before using Data Protection for Oracle. Note for Informix: The password specified in the register node command will be used with the tdpipswd program. Note for Tivoli Storage Manager for ERP, Data Protection for mySAP: Tivoli Data Protection for mySAP has several password handling options. See the Installation and User's Guide for more information about the options and their implications. The node that is used to back up Oracle or MS SQL database objects to Tivoli Storage Manager must be able to manually delete the backup objects. To do so, specify BACKDELETE=YES when registering the node. You can also update a node that has this value set to NO and set it to YES with the update node command. The MAXNUMMP option restricts the number of tape mounts that a client can initiate. In order for the Tivoli Storage Manager client to use multiple sessions when sending backups to tape, the parameter MAXNUMMP must be equal to or greater than the number of sessions involved in the backup. The MAXNUMMP option must not be set to a value greater than the actual number of physical drives defined to the Tivoli Storage Manager server. If the Data Protection module cannot acquire enough tape mounts, either because this value is set lower than the number of sessions or because sufficient tape drives are not available, the backups may fail, or have to wait for one session to finish. 21.4 Server configuration considerations The following are some recommendations for additional configuration on the Tivoli Storage Manager server to improve data protection backups and restores. Refer to the Data Protection module Installation and User's Guide for more information. Informix To back up large Informix databases, edit the dsmserv.opt and increase commtimeout to about 300 and idletimeout to 30. 688 IBM Tivoli Storage Manager Implementation Guide