May 31

Using MAXSESSIONS and MAXSCHEDSESSIONS to control sessions

TSM Server 6 Comments Off on Using MAXSESSIONS and MAXSCHEDSESSIONS to control sessions
Question
Controlling Tivoli Storage Manager sessions with Maxsessions and Maxschedsessions
 
 
Answer
A session established between a Tivoli Storage Manager client and Tivoli Storage Manager server can be either INBOUND or OUTBOUND. An INBOUND session is one where the client initiated the session (client contacted the server). An OUTBOUND connection is where the server initiates the session (server contacts the client, usually for a scheduled action like a backup).
The server option MAXSESSIONS is used to control the number of inbound sessions that can be active at one time. For example, when MAXSESSIONS is 55, this means that only 55 inbound sessions can be active at one time. Because each client can have multiple inbound sessions by adjusting the client option RESOURCEUTILIZATION, care is needed when determining a proper MAXSESSIONS value. Assume the default value of RESOURCEUTILIZATION 2 is used and 55 clients execute dsmc at one time. MAXSESSIONS should be set to 110 so that all 55 clients can use two sessions when connecting to the server.The maximum number of outbound sessions that can be active at one time is set by the server command SET MAXSCHEDSESSIONS. The value specified is a percentage of MAXSESSIONS. For example, when MAXSESSIONS is set to 220 and MAXSCHEDSESSIONS is set to 40(%), then the maximum number of outbound sessions that can be active at one time is 88. This number does not affect the maximum number of inbound sessions. For example, say MAXSESSIONS is set to 220 and MAXSCHEDSESSIONS is set to 40(%). This means the total number of inbound and outbound sessions is 308, or the sum of 220 + 88 (where 88 is 40% of 220).

NOTE: Sessions established for Tivoli Storage Manager server administration and Server/StorageAgent to Server communications are not counted against the maximum sessions. In the example above, a total of 308 non-admin client inbound and outbound sessions can be active at one time; but there is no set number of administrative client sessions that can be active at one time.

The conclusion is that the number of sessions that can be active at one time (as shown by the QUERY SESSIONS command) can be larger than the MAXSESSIONS value.

written by Bosse

May 17
Abstract
Tivoli Storage Manager V6.2 servers that were configured using the configuration wizard or upgrade wizard on Windows systems might have database backups that fail.When the database backup command is issued it might fail and display this message: “ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 406.”
 
 
Content
If the upgrade wizard or configuration wizard is used to configure or set up a Tivoli Storage Manager V6.2 server on a Windows system, when the BACKUP DB command is issued, it might fail due to a problem with the setup of the DSMI_api environment variable.
The database backup does not occur, and the server issues this message: “ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 406”.
To resolve this problem you must set the DSMI_api environment variable configuration for the database instance.Note: These examples use server1 for the database instance and d:\tsmserver1 for the Tivoli Storage Manager server instance directory. Replace these values with your actual values when issuing the commands.Perform these steps to set the DSMI_ api environment-variable configuration for the database instance:

1. Navigate to the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage Manager in a different location, go to the db2\bin subdirectory in your main installation directory and issue this command to open a DB2 command window:

db2cmd
2. Issue this command:
db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env

Additional information can be found in the Tivoli Storage Manager, Version 6.2 Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=/com.ibm.itsm.srv.install.doc/t_srv_prep_dbmgr.html.

written by Bosse

May 14
  • Issue the SET SERVERHLADDRESS command to identify the host or IP address of the server so you can see the deployment results.
  • Enable any applicable client events and assess their appropriate size and pruning duration. By enabling the events, the deployment manager can propagate the deployment messages to the server activity log. Determine an appropriate activity log size and pruning duration that can give you enough time to observe and react to the deployment results.
  • Configure the server for client automatic deployments. If you are using the Administration Center, access the Configure Client Auto Deployment wizard. Click Tivoli Storage Manager > Manage Servers. Select a server from the table and then select Configure Client Auto Deployment from the table actions. If you use the command-line interface to deploy client packages, issue the following example commands to configure the server:
    define devclass ibm_client_deploy_import devtype=file directory=import_directory
    
    define stgpool stgpool_name storage_dc_name maxscratch=20
    
    define domain ibm_client_deploy
    
    define policyset ibm_client_deploy ibm_client_deploy
    
    define mgmtclass ibm_client_deploy ibm_client_deploy ibm_client_deploy
    
    define copygroup ibm_client_deploy ibm_client_deploy ibm_client_deploy
    standard type=archive destination=stgpool_name retver=retention_value
    
    assign defmgmtclass ibm_client_deploy ibm_client_deploy ibm_client_deploy
    
    activate policyset ibm_client_deploy ibm_client_deploy
    
    set serverhladdress=server.serveraddress.com
    where:
    • ibm_client_deploy_import is the temporary location from where the deployment packages are imported. This parameter is defined by the deployment manager.
    • import_directory is a previously defined directory that is accessible from the server.
    • stgpool_name is the name of a storage pool of your choosing where the deployment packages are stored on the server. The storage pool name is based on a previously defined device class. That device class is different from the one that is used to import data.
    • storage_dc_name represents the device class where the deployment packages are stored on the server.
    • retention_value sets the retention time for the package. You can set it to NOLimit or to a number of days. The default for the Administration Center is 5 years. If you specify a value other than the default value, take into account the number of days that the package is on the FTP site. The days spent on the FTP site are included in the number.
    • server.serveraddress.com is the server IP address or host name from which you scheduled the client automatic deployment.
  • written by Bosse

    May 14
    Question
    Upgrading the Tivoli Storage Manager server from 5.4.x or 5.5.x to version 6.X can fail during dsmserv insertdb. The error seen is:
    ANR2020E INSERTDB: Invalid parameter – \MANIFEST
     
     
    Cause
    Incorrect use of dsmserv insertdb syntax can cause this error
     
     
    Answer
    The 6.X info center has the following example syntax for the Dsmserv Insertdb command:

    “c:\Program Files\Tivoli\TSM\server\dsmserv” insertdb \
    manifest=.\manifest.txt 1>>insert.out 2>&1The “\” character after insertdb tells Windows to go to the next line. But if you enter the following ( all on the same line):”c:\Program Files\Tivoli\TSM\server\dsmserv” insertdb \manifest=.\manifest.txt 1>>insert.out 2>&1

    The dsmserv insertdb will fail with the error :

    ANR2020E INSERTDB: Invalid parameter – \MANIFEST

    If you use this syntax , all on the same line, do not include the “\” after insertdb. For example:

      … dsmserv insertdb manifest=.\manifest.txt 1>>insert.out 2>&1

    written by Bosse

    May 14

    IC67043: ANS4013E ERROR PROCESSING ‘\SYSTEMSTATE\NULL\SYSTEM STATE\SYSTEMSTATE’: INVALID FILE HANDLE DURING SYSTEM STATE BACKUP

    Windows 2008 Comments Off on IC67043: ANS4013E ERROR PROCESSING ‘\SYSTEMSTATE\NULL\SYSTEM STATE\SYSTEMSTATE’: INVALID FILE HANDLE DURING SYSTEM STATE BACKUP

    Error description

    During backup of Windows 2008 systems, if Windows Deployment
    Service (WDS) is running, then the VSS WDS Writer might
    enumerate directories that do not exist. As a result, the
    system state backup will stop.
    
    This APAR is distinguished from IC65828, which addressed files
    reported by the VSS System Writer that do not exist.
    Local fix
    Create the directory that is reported as missing, then try the
    backup operation again.

    written by Bosse

    May 14

    Error description

    The TSM Administrator guide provides instructions for moving
    the active, archive and archive failover logs under section
    titled “Moving the database and recovery logs on a server”.

    After moving the active and archive logs, the database backup
    fails with following error :

    ANR2971E Database backup/restore/rollforward terminated –
    DB2 sqlcode -2428 error.

    In the case of a TSM server running on windows where the logs
    are moved from one drive to another (E: to F: for example), the
    db2diag.log shows :

    2010-02-11-11.24.17.120000-480 E2521076F450  LEVEL: Error
    PID     : 2892                 TID  : 3564   PROC : db2syscs.exe
    INSTANCE: SRV1                 NODE : 000
    EDUID   : 3564                 EDUNAME: db2lfr (TSMDB1)
    FUNCTION: DB2 UDB, data protection services,
    sqlpSearchForLogArchiveOnDisk, probe:4000
    MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH “an invalid path”
              DIA8514C An invalid file path, “”, was specified.

    2010-02-11-11.24.17.120000-480 E2522362F437  LEVEL: Warning
    PID     : 2892                 TID  : 3540   PROC : db2syscs.exe
    INSTANCE: SRV1                 NODE : 000
    EDUID   : 3540                 EDUNAME: db2logmgr (TSMDB1)
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4165
    MESSAGE : ADM1847W  Failed to retrieve log file “SXXX.LOG” on
    chain “0” from “E:\archlog\RstDbLog\”.

    The db2diag.log shows that the path of the log at the old
    location is still referenced.

    NOTE: This behavior can also happen when the ARCHLOGFAILOVERDIR
          option is removed completely, as opposed to just changed.
    .
    Customer/L2 Diagnostics:
    Review the server options file for the log options using the
    “QUERY OPTION” TSM administrative command. For example :

    ActiveLogDir          F:\log
    ArchiveLogDir         F:\archlog
    ArchFailOverLogDir

    Review the DB2 database configuration parameters for the logs
    using the “db2 get db cfg for TSMDB1”. For example :

    Path to log files                         = F:\log\
    Overflow log path       (OVERFLOWLOGPATH) = E:\archlog\RstDbLog\
    Failover log archive path  (FAILARCHPATH) = E:\archlog\failarch\
    First log archive method
                         (LOGARCHMETH1) = DISK:F:\archlog\archmeth1\

    The DB2 database configuration still shows the “old” path
    for the Overflow and Failover log paths.

    UNIX reported that the following DB2 setting also had the old
    path.  Ex:
    First log archive method (LOGARCHMETH1) =
    DISK:/tsm2/tsmarchlog/archmeth1/

    Local fix

    Follow the below steps to manually correct the configuration.
    1. Create missing directories. For example :
    F:\archlog\RstDbLog
    F:\archlog\failarch
    2. Stop the TSM server
    3. Start DB2 with “db2start”
    4. Update the DB2 database configuration with the following
       two commands :
    a) db2 update db cfg for TSMDB1 using OVERFLOWLOGPATH
       “F:\archlog\RstDbLog\”
    b) db2 update db cfg for TSMDB1 using FAILARCHPATH
       “F:\archlog\failarch\”

    UNIX example of the corrected path for LOGARCHMETH1, do:
    db2 update db cfg for TSMDB1 using LOGARCHMETH1
    DISK:/tsm2a/tsmarchlog/archmeth1/

    5.  Start TSM server

    written by Bosse

    May 12

    The TSM Administrator guide provides instructions for moving
    the active, archive and archive failover logs under section
    titled “Moving the database and recovery logs on a server”.

    After moving the active and archive logs, the database backup
    fails with following error :

    ANR2971E Database backup/restore/rollforward terminated –
    DB2 sqlcode -2428 error.

    In the case of a TSM server running on windows where the logs
    are moved from one drive to another (E: to F: for example), the
    db2diag.log shows :

    2010-02-11-11.24.17.120000-480 E2521076F450  LEVEL: Error
    PID     : 2892                 TID  : 3564   PROC : db2syscs.exe
    INSTANCE: SRV1                 NODE : 000
    EDUID   : 3564                 EDUNAME: db2lfr (TSMDB1)
    FUNCTION: DB2 UDB, data protection services,
    sqlpSearchForLogArchiveOnDisk, probe:4000
    MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH “an invalid path”
              DIA8514C An invalid file path, “”, was specified.

    2010-02-11-11.24.17.120000-480 E2522362F437  LEVEL: Warning
    PID     : 2892                 TID  : 3540   PROC : db2syscs.exe
    INSTANCE: SRV1                 NODE : 000
    EDUID   : 3540                 EDUNAME: db2logmgr (TSMDB1)
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4165
    MESSAGE : ADM1847W  Failed to retrieve log file “SXXX.LOG” on
    chain “0” from “E:\archlog\RstDbLog\”.

    The db2diag.log shows that the path of the log at the old
    location is still referenced.

    NOTE: This behavior can also happen when the ARCHLOGFAILOVERDIR
          option is removed completely, as opposed to just changed.
    .
    Customer/L2 Diagnostics:
    Review the server options file for the log options using the
    “QUERY OPTION” TSM administrative command. For example :

    ActiveLogDir          F:\log
    ArchiveLogDir         F:\archlog
    ArchFailOverLogDir

    Review the DB2 database configuration parameters for the logs
    using the “db2 get db cfg for TSMDB1”. For example :

    Path to log files                         = F:\log\
    Overflow log path       (OVERFLOWLOGPATH) = E:\archlog\RstDbLog\
    Failover log archive path  (FAILARCHPATH) = E:\archlog\failarch\
    First log archive method
                         (LOGARCHMETH1) = DISK:F:\archlog\archmeth1\

    The DB2 database configuration still shows the “old” path
    for the Overflow and Failover log paths.

    UNIX reported that the following DB2 setting also had the old
    path.  Ex:
    First log archive method (LOGARCHMETH1) =
    DISK:/tsm2/tsmarchlog/archmeth1/

    FIX

    Follow the below steps to manually correct the configuration.
    1. Create missing directories. For example :
    F:\archlog\RstDbLog
    F:\archlog\failarch
    2. Stop the TSM server
    3. Start DB2 with "db2start"
    4. Update the DB2 database configuration with the following
       two commands :
    a) db2 update db cfg for TSMDB1 using OVERFLOWLOGPATH
       "F:\archlog\RstDbLog\"
    b) db2 update db cfg for TSMDB1 using FAILARCHPATH
       "F:\archlog\failarch\"
    
    UNIX example of the corrected path for LOGARCHMETH1, do:
    db2 update db cfg for TSMDB1 using LOGARCHMETH1
    DISK:/tsm2a/tsmarchlog/archmeth1/
    
    5.  Start TSM server

    written by Bosse

    May 12

    SQL6028N error with catalog command

    Uppgradering Comments Off on SQL6028N error with catalog command
    Problem(Abstract)
    Running the db2 catalog command in order to catalog the Tivoli Storage Manager server database fails with error SQL6028N.
     
     
    Cause
    Incorrect database directory path was used with the db2 catalog command.
     
     
    Environment
    Tivoli Storage Manager Server V6.1 and V6.2 on Unix and Linux.
     
     
    Diagnosing the problem
    The catalog command fails to catalog the Tivoli Storage Manager database (TSMDB1). For example :

    $db2 catalog tsmdb1 on /home/tsminst1
    SQL6028N Catalog database failed because database “TSMDB1” was not found in
    the local database directory.
     
     
    Resolving the problem
    Follow the below steps to correct the issue.

    1. Find the correct instance directory. For example:
      $cat /etc/tivoli/tsm/instance.info
      ...
      <Database>
      <DatabaseName>TSMDB1</DatabaseName>
      <DatabasePath>/home/tsminst1/tsminst1 </DatabasePath>
      </Database>
      ...

      In above example, the database path is “/home/tsminst1/tsminst1 “
    2. Re-run the failed command using the correct Database path. For example :
      $db2 catalog tsmdb1 on /home/tsminst1/tsminst

    written by Bosse

    May 12
    Abstract
    If a connection cannot be established using SSH, RSH, REXEC, or SMB, manually upgrade the IBM® Tivoli® Storage Manager server instance from Version 6.1 to 6.2.
     
     
     
    Content
    To use a wizard, the upgrade from IBM® Tivoli® Storage Manager Version 6.1 to Version 6.2 requires one of the following protocols on the default port, and that port cannot be blocked by a firewall:
    -Secure shell (SSH)
    -Remote shell (RSH)
    -Remote Execution Protocol (REXEC)-Windows® server message block (SMB)If a connection cannot be established using SSH, RSH, REXEC, or SMB, manually upgrade the Tivoli Storage Manager server instance from Version 6.1 to 6.2.AIX®, Linux®, and UNIX®:
    Close the installation wizard if you receive an error message indicating that the
    wizard could not connect to your system using SSH, RSH, or REXEC:
    All attempts to establish a connection as the instance user ID have failed. This might be due to an inability to connect to the local machine through the SSH, RSH, REXEC, or Windows SMB protocols.Then, use the following procedure to manually upgrade the server instance from Version 6.1.

    First, rename the instance file. You can find this file in the following location:
    /etc/tivoli/tsm/instance.info

    The instance file looks similar to this example and contains DB2 environment
    variables as configured for your server instance . Use the
    values in this file for the commands necessary to manually upgrade the server
    instance.

    <Instance>
    <InstanceName>tsminst1</InstanceName>
    <InstanceUser>tsminst1</InstanceUser>
    <DefaultDatabasePath>/home/tsminst1/tsminst1</DefaultDatabasePath>
    <Database>
    <DatabaseName>TSMDB1</DatabaseName>
    <DatabasePath>/home/tsminst1/tsminst1</DatabasePath>
    </Database>
    <Variables>
    <Variable>DB2_SKIPINSERTED=ON></Variable>
    <Variable>DB2_KEEPTABLELOCK=ON</Variable>
    <Variable>DB2_EVALUNCOMMITTED=ON</Variable>
    <Variable>DB2_SKIPDELETED=ON</Variable>
    <Variable>DB2CODEPAGE=819</Variable>
    <Variable>DB2_PARALLEL_IO=*</Variable>
    </Variables>
    </Instance>

    After renaming the instance file, complete the following steps.
    Important: Complete steps 1-6 for each one of your Tivoli Storage Manager server instances.

    1. Issue the following command:
    /opt/tivoli/tsm/db2/instance/db2idrop InstanceName

    2. Start the installation wizard again and step through it to upgrade the Tivoli
    Storage Manager server.

    3. After the upgrade, recreate each of the instances using the following command:
    /opt/tivoli/tsm/db2/instance/db2icrt –u InstanceUser InstanceName

    4. Recreate the variables in the instance file using the db2set -i command. Issue
    this command for each variable in your instance file. Ensure that the variable is
    in quotation marks:
    /opt/tivoli/tsm/db2/instance/db2iset –i InstanceName “Variable”

    For example, to recreate the first variable in the example instance file, issue the
    following command:
    db2set -i tsminst1 “DB2_SKIPINSERTED=ON”

    5. Stop and start the database instance.
    Connect as the user ID that owns the server instance, then issue the following
    commands:

    a. Start DB2®:
    db2start

    b. Catalog and upgrade each database:
    “db2 catalog db DatabaseName on DatabasePath
    “db2 upgrade db DatabaseName

    c. Stop DB2:
    db2stop

    6. Start and run the Tivoli Storage Manager server.

    Windows®:

    Close the installation wizard if you receive an error message indicating that the
    wizard could not connect to your system using SSH, RSH, REXEC, or SMB:
    All attempts to establish a connection as the instance user ID have failed. This might be due to an inability to connect to the local machine through the SSH, RSH, REXEC, or Windows SMB protocols.

    Then, complete the following procedures to manually upgrade the server instance from Version
    6.1.

    Before starting the upgrade, rename the instance file. The instance
    file (Instance.dat) is in the Tivoli Storage Manager server installation directory

    The instance file looks similar to this example and contains DB2 environment
    variables as configured for your server instance. Use the
    values in the instance file for the commands necessary to manually upgrade the server
    instance.

    <Instance>
    <InstanceName>server1</InstanceName>
    <InstanceUser>server1</InstanceUser>
    <DefaultDatabasePath>d:\tsm\server1</DefaultDatabasePath>
    <Database>
    <DatabaseName>TSMDB1</DatabaseName>
    <DatabasePath>d:\tsm\server1</DatabasePath>
    </Database>
    <Variables>
    <Variable>DB2_SKIPINSERTED=ON></Variable>
    <Variable>DB2_KEEPTABLELOCK=ON</Variable>
    <Variable>DB2_EVALUNCOMMITTED=ON</Variable>
    <Variable>DB2_SKIPDELETED=ON</Variable>
    <Variable>DB2CODEPAGE=819</Variable>
    <Variable>DB2_PARALLEL_IO=*</Variable>
    </Variables>
    </Instance>

    After renaming the instance file, complete the following steps.
    Important: Complete steps 1-6 for each one of your Tivoli Storage Manager server instances.

    1. Issue the following command:
    installation_directory\db2\instance\db2idrop InstanceName

    2. Start the installation wizard again and step through it to upgrade the Tivoli
    Storage Manager server.

    3. After the upgrade, recreate each of the instances using the following command:
    installation_directorydb2\instance\db2icrt InstanceName –u
    InstanceUser, password

    4. Recreate the variables in the instance file using the db2set -i command. Issue
    this command for each variable in your instance file. Ensure that the variable is
    in quotation marks:
    installation_directory\db2\instance\db2iset –i InstanceName “Variable”

    For example, to recreate the first variable in the example instance file, issue the
    following command:
    db2set -i server1 “DB2_SKIPINSERTED=ON”

    5. Stop and start the database instance:

    a. Open a DB2 command window. One method of doing this is by going to
    the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed
    Tivoli Storage Manager in a different location, go to the db2\bin
    subdirectory in your main installation directory. Then, issue this command:
    db2cmd

    b. Set the database instance:
    set db2instance=InstanceName

    c. Start DB2:
    db2start

    d. Catalog and upgrade each database name:
    “db2 catalog db DatabaseName on DatabasePath
    “db2 upgrade db DatabaseName

    e. Stop DB2:
    db2stop

    6. Start and run the Tivoli Storage Manager server.

    written by Bosse

    May 12
    Abstract
    Tivoli Storage Manager V6.2 servers that were configured using the configuration wizard or upgrade wizard on Windows systems might have database backups that fail.When the database backup command is issued it might fail and display this message: “ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 406.”
     
     
    Content
    If the upgrade wizard or configuration wizard is used to configure or set up a Tivoli Storage Manager V6.2 server on a Windows system, when the BACKUP DB command is issued, it might fail due to a problem with the setup of the DSMI_api environment variable.
    The database backup does not occur, and the server issues this message: “ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 406”.
    To resolve this problem you must set the DSMI_api environment variable configuration for the database instance.Note: These examples use server1 for the database instance and d:\tsmserver1 for the Tivoli Storage Manager server instance directory. Replace these values with your actual values when issuing the commands.

    Perform these steps to set the DSMI_ api environment-variable configuration for the database instance:

    1. Navigate to the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage Manager in a different location, go to the db2\bin subdirectory in your main installation directory and issue this command to open a DB2 command window:

    db2cmd
    2. Issue this command:
    db2set -i server1 DB2_VENDOR_INI=d:\tsmserver1\tsmdbmgr.env

    Additional information can be found in the Tivoli Storage Manager, Version 6.2 Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=/com.ibm.itsm.srv.install.doc/t_srv_prep_dbmgr.html.

    written by Bosse