Oct 29

Tivoli Storage Manager backend capacity-based licensing programs

Licensing Comments Off on Tivoli Storage Manager backend capacity-based licensing programs

What are the IBM Tivoli Storage Manager capacity-based licensing programs?

IBM Tivoli Storage Manager provides three capacity-based pricing programs. These are referred to as “Suite for Unified Recovery” (SUR) and “Suite for Unified Recovery – Archive Option” (SUR-Archive). Additional details and explanation about each can be found at:

License Program Link
SUR http://www-01.ibm.com/support/docview.wss?uid=swg21500482
SUR-Archive http://www-01.ibm.com/support/docview.wss?uid=swg21596104
SUR-ProtectTier http://www-01.ibm.com/support/docview.wss?uid=swg21647140

Note the following discussion in this document relates to the “SUR” and “SUR-Archive” licensing programs. The details about planning for and using the SUR-ProtectTier program are discussed in the document linked above.

What steps should I take to prepare for running the macro?

  • Read the information about the SUR and SUR-Archive programs to determine which is applicable and should be used. You can work with your IBM account team or sales specialist/representative to help understand which should be considered.
  • Download the appropriate macro(s) based on the license program. Consider that there are different versions of the macro depending upon the version of the TSM server.
    • Consider verifying that the downloaded macro looks correct by viewing it and comparing it to the example in this document.
  • If there is a non-production TSM server (test) in your environment, consider trying the macro on the test server to familiarize yourself with how it is invoked and used.
    • Consider verifying that the generated output is correct by comparing the output to the example in this document.
  • Plan to run the macro at a time when the server workload is light or when other administrative tasks are being performed.

Is is possible to do capacity-based license measurements for versions of the product that are no longer supported?

The instructions for how to perform a capacity-based measurement for TSM V5.5 or V6.1 are available using this link:

http://www-01.ibm.com/support/docview.wss?uid=swg21684142.

It is recommended that you upgrade your TSM servers to a supported version of the product. The table below also references how to download the capacity measurement macros for these no longer supported versions of the product.

How do I get the tool(s) that perform the capacity-based license measurement?

Macro Name Use For Server Version Used By FTP Link
tsm_tb_cap_v5.macro V5.5 SUR V5 Capacity Macro
tsm_tb_cap_v5_lite.macro V5.5 SUR V5 Capacity Macro (Lite)
(See below for when and why to consider using this version of the macro for a V5.5 server)
tsm_tb_cap_v6.macro V6.1, V6.2 SUR V6.1 and V6.2 Capacity Macro
tsm_tb_cap_v63.macro V6.3, V7.1, 7.1.1* SUR V6.3 and V7.1 Capacity Macro
tsm_ar_tb_cap_V63.macro V6.3, V7.1 SUR-Archive V6.3 and V7.1 SUR-Archive Capacity Macro
tsm_tb_cap_v711_tgt.macro V7.1.1* SUR V7.1.1 Replication Target Managing Data Using Different Policies
tsm_tb_cap_v711_rc.macro V7.1.1* SUR V7.1.1 Replication Source Manage Data Using Different Policies

*Note: TSM V7.1.1 introduces the ability for TSM servers that replicate data from a source to a target to manage the data using different policies at each site. The “tsm_tb_cap_v63.macro” should be used for V7.1.1 servers if TSM server to server replication is not being used or if replication is being used and the data is not being managed differently. If V7.1.1 is being used and replication is configured to use “DISSIMILAR POLICIES” (see command QUERY REPLSERVER), than the “tsm_tb_cap_v711_tgt.macro” and “tsm_tb_cap_v711_src.macro” macros should be used. The SUR link referenced in the question above (” What are the IBM Tivoli Storage Manager capacity-based licensing programs?“) provides additional information about how to use these macros.

How do I download the macro from the FTP site?

How you download the macro from the FTP site will vary by your operating system and the browser that you are using. An example of how to do this is:

1. Click on the appropriate link from the table above.
2. For example the tsm_tb_cap_v6.macro, should appear as shown after downloading it. The example is only an excerpt and shows just the first 43 lines of the file. It is shown to illustrate the general layout and content of the macro.


3. From the browser, perform the “Save As” which is typically available from the “File” drop down menu on most browsers. It is recommended that it be saved as the name of the macro file so that the other instructions will reference the appropriate name.

For example, if you selected the macro “tsm_ar_tb_cap_v63.macro”, save this to your local disk as the same name (“tsm_ar_tb_cap_V63.macro”).

Note:
When performing the “Save As”, you want to only save the content of the page and not the HTML formatting or such that was applied when it was opened in the browser to view. On Mac OS, select “page source” to prevent saving it with the HTML tagging from the browser. From Windows, saving it as “Text Document (*.txt)” should be used as this will also prevent the HTML tagging from being embedded in the document.

4. To verify that you have done this correctly, you can open this in an editor and view the contents of the saved file and compare it to what was shown in the browser from step 2 above.

Note: The macro contains a number of lines that are many characters long and depending upon your editor settings, these may wrap (as shown above) or they may extend to the right and only be visible by scrolling to the right. It can be viewed either way, the important item is that the long lines are not broken up into many smaller lines with a “carriage return” or such imposed in the line.

What are the impacts or consequences of running the macro against my TSM server?

The macro is a TSM administrative command macro. It executes a number of SQL statements against the TSM server. The macro will require processing capacity (CPU) and memory from the TSM server. The SQL statements being run will read information from the TSM server’s database and as such it will generate I/O to the TSM server database and use memory for the database buffer pool and in-memory for the handling and processing itself.

For V6.1, V6.2, V6.3, or V7.1 servers, the SQL processing provided by DB2 is typically able to handle the resource needs of these SQL statements without issue. Notably, the statements usually run quickly on the order of minutes or tens of minutes.

For V5.5 servers, the SQL processing is highly dependent upon the CPU, memory, and I/O to the server database. In most cases, the macro is able to run in minutes, tens of minutes, or hours. In a few cases, we have seen that the macro takes many hours to run. The reason it can take a long time to run is that the SQL processing on V5.5 servers is not as efficient as what is available to the V6 and V7 TSM servers. It is also highly dependent upon the available system resources, so if the server is already near or exceeding its operational limits, than running the macro may take a long time.

For V5.5 servers, if the “tsm_tb_cap_v5.macro” macro is not able to complete or taking a long time to run, there is an alternate version of the macro available for use. See the topic in this document that discusses “What is the tsm_tb_cap_V5_lite.macro?” for more details on the purpose and use of this.

What is the “tsm_tb_cap_v5_lite.macro”?

This “lite” version of the macro reduces the complexity of the capacity measurement macro but it can only be used if the TSM server does not have any of the following types of data stored on it:

  • TSM server to server virtual volumes. This server cannot be a target for a TSM server to server virtual volume configuration.
  • TSM for Sharepoint or HSM for Windows. This server cannot store data from a TSM for Sharepoint or HSM for Windows clients or agents.
  • Data replicated from FastBack. This server cannot store data from a FastBack server replicating to this TSM server as a target.

If any of these types of data are being stored to this V5.5 server, then the “lite” version of the macro may not be used. If this V5.5 server is not storing any of these types of data, then the “lite” version of the macro can be used. Often times, it is able to run in less time and using less resources so it can complete in a shorter, more manageable timeframe.

The “tsm_tb_cap_v5_lite.macro” should be used for the following circumstances:

  • The V5.5 TSM server is already overloaded with regards to workload or available resources. For example: The server is at or near the limits of the resource capacity (CPU, memory, I/O) or the daily workloads (client data ingest, server maintenance) are taking all or most of the time available in a 24 hour window to complete.
  • The “tsm_tb_cap_v5.macro” has been tried but it takes too long to run, ran and never completed, or fails to run in this V5.5 TSM server environment.

How do I get the macro on the machine (system) where my TSM server is running?

If the system the TSM server runs on has access to the internet and the FTP link to the appropriate macro, then the macro can be accessed and saved directly from the FTP site to that system.

If the system the TSM server runs on does not have access to the internet, then the appropriate macro needs to be saved to your local environment and then transferred to the system where the TSM server is running. This can be done using file transfer tools like FTP, scp, WinSCP, or many other techniques or tools.

Note:
The macro file is simply a text file. It should be transferred from machine to machine as just a normal text file. It does not require any special handling such as to transfer it as “Binary” or such.

How do I run the macro?

The macro is run from a command prompt and uses the administrative command line client. The macro should be invoked using the following command syntax:

dsmadmc -id=<yourid> -password=<yourpassword> -dataonly=yes -outfile=<output_file_name> macro <macro_name>


The input parameters that must be specified by the administrator when this is executed are the items enclosed in ‘<‘ and ‘>’ respectively. The specific input parameters are:

  • <yourid> – This is the administrative user id that will be used to connect to the server.
  • <yourpassword> – This is the password for the administrative user id that will be used to connect to the server.
  • <capacity_file_name> – The results from the macro will be stored to this file. Select an appropriate file name use. For example, consider using the server name such as “server1.capacity”.
  • <macro_name> – The name of the macro to be run which is tsm_ar_tb_cap_v63.macro.

An example of how the macro would be invoked against a Unix, Linux, or AIX server using an xterm (or equivalent) type of interface is:

Note: The macro is invoked from the command line administrative client being run in batch mode. The macro should not be run from the command line administrative client in interactive mode.

What is the output of the macro?

The macro writes its output to the file designated by the “-outfile=…” parameter when it is invoked. See the topic “How do I run the macro?” for more explanation about how to invoke (run) the macro. An example output report for a V6 server is:

This is the general format of the report. For V5.5 servers, the “Deduplication Benefits” section simply references that TSM offers deduplication in newer versions of the product and it does not otherwise report a value. In this example, 42 TB is not being counted in the capacity measurement because the data was deduplicated and this is the savings result from the elimination of that duplicate data.

The “Details on Excluded Data” section will vary depending upon what exclusions are found. If there is no data of a specific type identified and excluded, then nothing is shown in the report. In this example, the server is using storage pools of TYPE=COPY or TYPE=ActiveData. In this case, 51 TB is identified and excluded from measurement.

This example is provided as a “guide” to understand what a typical report looks like. If the output of the macro differs significantly from what is shown this usually indicates that the macro was not correctly run. The typical reason for a significant difference in the formatting of this report is that the macro was run from the command line administrative client in interactive mode instead of being run from the system command line and using the administrative client in batch mode.

What do I do if the value reported from the macro seems wrong or incorrect?

Contact IBM service. Please provide the following information:

  • Identify the server where you are seeing the incorrect or unexpected result.
  • Provide the macro that was run to create the capacity report with the value in question:
    • Include information about the command syntax that was used to invoke the macro.
  • Provide the created capacity report that contains the value in question.
    • This is the output file specified from “-outfile=…” parameter when the administrative command line client was invoked to run the macro.
  • Collect and provide the following data from the TSM server:
    • SELECT * FROM OCCUPANCY
    • SELECT * FROM NODES
    • SELECT * FROM STGPOOLS
    • SELECT * FROM FILESPACES

written by Bosse

Oct 22

System State Backups May Fail On Certain Windows Operating Systems

Windows VSS Comments Off on System State Backups May Fail On Certain Windows Operating Systems

Problem(Abstract)

TSM Client system state backups sometimes fail on Windows 2008 R2, Windows 7, Windows 8, or Windows 2012 operating systems. These backups are performed using Volume Shadow Copy Service, which may fail during this operation. During the operating system installation, a 100 MB System Reserved Partition is typically created, however the VSS operation will fail if this volume is not online. This leads to the system state backup failure.

Symptom

When this problem is encountered the following will appear after the system state backup is invoked:

Backup System State using shadow copy…
ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

System State Backup finished with failures.

ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

After the failure, vssadmin reports that the ASR writer has timed out.

********

In addition to the above error, the error log will contain entries similar to the following:

05/13/2011 11:18:39 ANS5250E An unexpected error was encountered.
TSM function name : BackupComplete()
TSM function : ‘BackupComplete() failed with error VSS_E_BAD_STATE. -2147212543’
TSM return code : -2147212543
TSM file : asrutil.cpp (2416)
05/13/2011 11:18:39 ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

05/13/2011 11:18:40 ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

********

In addition to the errors listed above, the Windows Event Viewer will contain:

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}.
Routine details EndPrepareSnapshots({4fe8f016-cc83-4541-acb1-106e36caba72}) [hr = 0x80070015, The device is not ready.].

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

 

Cause

TSM uses VSS to back up system state, but VSS runs into errors if the 100 MB System Reserved Partition is offline.

One cause for the 100 MB System Reserved Partition to be offline is having the Windows automount capability disabled. There are circumstances where the automount capability must be disabled, but it has been observed that this can result in the partition being offline after the reboot.

 

Environment

Windows Server 2008 R2

Windows 7
Windows Server 2012
Windows 8

 

Diagnosing the problem

To determine if this problem has been encountered during a TSM Client system state backup, perform the following:

  1. Confirm that the operating system is Windows 2008 R2, Windows 7, Windows 8, or Windows 2012.
  2. Check for the errors listed in the Symptoms section above.
  3. Run ‘DISKPART LIST VOLUME’ from a Command Prompt to determine if there is a 100 MB volume that is offline.

Resolving the problem

As mentioned in the Abstract section, this problem occurs because the 100 MB System Reserved Partition is offline. This issue can be resolved by enabling automount and rebooting, which will bring this volume online and keep it online through subsequent reboots. Enabling automount can be done by opening a Command Prompt window and invoking DISKPART:

DISKPART -> automount enable -> exit

Before making this change to enable automount, care should be taken to determine that it was not disabled intentionally. For example, systems acting as VMware vStorage backup servers are required to have automount disabled. If automount needs to stay disabled, a work-around would be to go into DISKPART and set the 100 MB volume online:

DISKPART -> list volume -> select volume 1 -> online volume -> exit

The volume selected should be the 100 MB volume. In the above example it was assumed that ‘list volume’ showed the 100 MB volume to be volume 1. It is important to note that with automount disabled, this will only keep the volume online until the next system reboot.

written by Bosse

Sep 15

New Data Protection for Microsoft SQL Server Version 7.1.1

SQL Comments Off on New Data Protection for Microsoft SQL Server Version 7.1.1
Support for Microsoft SQL Server 2014
You can now use Data Protection for SQL Server to manage SQL Server 2014 in stand-alone and failover cluster environments, and to protect your SQL Server 2014 databases.
Backup processing efficiencies and improvements
During backup processing, Data Protection for SQL Server bypasses database snapshots and databases that are in offline, mirroring, and restoring states. With this release, the databases that are bypassed during backup processing are indicated in the console output and in the tdpsql.log.
AES 256-bit encryption added as an available data encryption type
AES 256-bit encryption is available as a data encryption type with this release. AES-256 provides the most secure algorithm to encrypt data that is sent to the Tivoli Storage Manager server. Previously supported AES-128 and DES-56 encryption remain as supported encryption types.
Checksum processing is available for legacy database backups
In the Microsoft Management Console (MMC), you can specify integrity checking for legacy database backups. On the command-line interface, you can set the SQLCHECKSum parameter with the set command to specify integrity checking for all legacy backups. You can override the global setting by issuing the SQLCHECKSum parameter on the backup command.
VERIFYOnly option is available for legacy database restore operations
You can verify whether a legacy database backup is valid without physically restoring the backup. Before you restore the legacy database backup, you can run the restore operation with the Verify Only option in the MMC. Alternatively, you can use the /VERIFYOnly option with the restore command on the command-line interface.

written by Bosse

Sep 15

News in TDM Exchange 7.1.1

Exchange Comments Off on News in TDM Exchange 7.1.1

New for Data Protection for Microsoft Exchange Server Version 7.1.1

Data Protection for Microsoft Exchange Server includes several new features and changes.

The required authority to perform mailbox restore operations is reduced
In previous releases, only members of the Exchange Organization Management role group had the required administrative permissions to complete mailbox restore operations. With this release, it is no longer necessary for Exchange backup and restore operators to be in the Organization Management role group and have full administrative authority. You can use Exchange Role Based Access Control (RBAC) to limit users to specific operations, for example, view-only access to a mailbox list or individual mailbox restore operations. With RBAC management role scope, you can further limit the scope of restore operations, for example, to users in a single Active Directory domain.
Capacity to keep a recovery database for mailbox restore operations
With this release, you can retain a recovery database for reuse in mailbox restore operations. Alternatively, you can ensure that the recovery database is removed after a mailbox restore operation is complete. You can use the /KEEPRDB option with the restoremailbox command on the command-line interface, or specify the option in the Microsoft Management Console (MMC).
Capacity to use or remove an existing recovery database during mailbox restore operations
You can restore mailboxes from an existing recovery database, or you can automatically remove an existing recovery database during mailbox restore operations. You can choose whether to use a recovery database for mailbox restore operations in the MMC, or by using the /USEEXISTINGRDB option with the restoremailbox command on the command-line interface.
Performance enhancements in Mailbox Restore Browser functionality
Performance is significantly improved when the Mailbox Restore Browser feature restores whole mailboxes, mailbox folders, and selected mail messages.
Usability enhancements in the Mailbox Restore Browser interface
When you use the Mailbox Restore Browser interface to restore a mailbox, you can identify which backup version to restore from a list of available backups. Right-click menus are available for mailbox restore tasks.
AES 256-bit encryption added as an available data encryption type
AES 256-bit encryption is available as a data encryption type with this Data Protection for Exchange release. AES-256 provides the most secure algorithm to encrypt data that is sent to the Tivoli Storage Manager server. AES-128 and DES-56 encryption remains as encryption types that you can use.
Options to bypass integrity checking in a Database Availability Group environment
If at least two healthy copies of a database (one active and one passive copy) exist in a Database Availability Group (DAG) environment, it might not be necessary to verify the consistency of the database and log files. To expedite backup processing, you can bypass integrity checking of database and log files. You can use the /SKIPINTEGRITYCHECK options with the backup command on the command-line interface, or in the MMC.

written by Bosse

Jun 24

Backup of VMware Windows MS SQL guest fails

VE Comments Off on Backup of VMware Windows MS SQL guest fails

Problem(Abstract)

Tivoli Storage Manager for Virtual Environments is used to back up a Windows guest that runs Microsoft SQL. The backup of the VM fails with the ANS9365E and ANS5250E errors.

Symptom

The following errors are logged during the backup :


04/30/2014 23:18:46 ANS9365E VMware vStorage API error for virtual machine 'myguest'.
TSM function name : visdkCreateVmSnapshotMoRef
TSM file : vmvisdk.cpp (5416)
API return code : 67
API error message : An error occurred while quiescing the virtual machine. See the virtual machine's event log for details.
04/30/2014 23:18:46 ANS5250E An unexpected error was encountered.
TSM function name : vmVddkFullVMPrePareToOpenVMDKs
TSM function : snapshot targetMoRefP is null
TSM return code : 115
TSM file : ..\..\common\vm\vmbackvddk.cpp (12439)
04/30/2014 23:18:46 ANS1228E Sending of object 'myguest' failed.

 

Diagnosing the problem

Examine the vmware.log of the virtual machine, located in the folder of the virtual machine in the datastore. The following errors are logged :

2014-05-05T02:32:18.259Z| vcpu-1| I120: [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
2014-05-05T02:32:18.259Z| vcpu-1| I120+ The error code was: 5
2014-05-05T02:32:18.259Z| vcpu-1| I120+ The error message was: 'VssSyncStart' operation failed: IDispatch error #8449 (0x80042301)

Examine the Windows event log of the Windows guest. The following errors are logged :

4/30/2014 11:18:30 PM VSS Error None 6008 N/A MYGUEST
Sqllib error: Failed to create VDS object. hr = 0x80040154.
4/30/2014 11:18:30 PM VSS Error None 20 N/A MYGUEST
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during
installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID
{40700425-0080-11d2-851f-00c04fc21759} and Name MSSQL_ClientVirtualDeviceSet is [0x80040154].

 

Resolving the problem

In this case, the backup fails is caused by a VSS problem on the Windows guest. Follow the steps below to resolve the error :

  1. Stop SQL Server.
  2. Click Start/Run and enter the following command in the Open box, and then click OK.

    Regsvr32 Path\SQLVDI.DLL

    The default path of the Sqlvdi.dll file is C:\Program Files\Microsoft SQL Server\80\COM.
  3. Restart SQL Server.
  4. Run the backup of the VM

Refer to the following Microsoft article for more information about the VSS SQL error.
http://support.microsoft.com/kb/830575

written by Bosse

May 07

Considerations when upgrading to Tivoli Storage Manager v7

Upgrade Comments Off on Considerations when upgrading to Tivoli Storage Manager v7

Question

What are the known issues you need to be aware of before upgrading to version 7.1 of the Tivoli Storage Manager?

Cause

There are two potential DB2 APARs that you may encounter during your upgrade from v6 to v7.
APAR Numbers:

Note that the underlying sub-directory structure of DB2’s active, active mirror, archive, and archive overflow locations have been changed. As a result, at upgrade time, DB2 attempts to copy the log files from the old sub-directory structure into a new sub-directory structure.

If DB2 is unable to successfully move the log files, the following errors may be seen:

Tivoli Storage Manager Installation/Upgrade Results:

      When running the upgrade of the server, the following warning message is encountered:

ANRI1017W WARNING:   The upgrade command for database TSMDB1 failed. To complete the upgrade of this instance, correct the error and reissue the following command as user <Instance User>:

db2 upgrade database TSMDB1.

      Next, trying to start DB2 and run the upgrade command results in the following:

$ db2start
04/14/2014 16:17:58     0   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.

$ db2 upgrade database TSMDB1
SQL1762N  Unable to connect to database because there is not enough space to allocate active log files.  SQLSTATE=08004
db2diag.log File Results:2014-04-08-10.04.20.104213-300 I63592A829           LEVEL: Error
PID     : 14811534             TID : 2058           PROC : db2sysc 0
INSTANCE: prd04                NODE : 000           DB   : TSMDB1
APPHDL  : 0-7                  APPID: *LOCAL.tsmprd04.140408150419
AUTHID  : PRD04                HOSTNAME: prd004
EDUID   : 2058                 EDUNAME: db2agent (TSMDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgReallocLogs, probe:970
MESSAGE : ZRC=0x85100084=-2062548860=SQLP_NO_SPACE_FOR_LOG
          "Not enough space to create primary logs"
DATA #1 : String, 59 bytes
Log path / Free space (bytes) / Log space required (bytes):
DATA #2 : String, 52 bytes
/prd04/db2actlog/prd04/NODE0000/LOGSTREAM0000/
DATA #3 : unsigned integer, 8 bytes
16079912960
DATA #4 : unsigned integer, 8 bytes
137441050624

2014-04-08-10.04.20.161956-300 I71011A511           LEVEL: Warning
PID     : 10944702             TID : 1              PROC : db2bp
INSTANCE: prd04                NODE : 000
HOSTNAME: prd004
EDUID   : 1
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:365
MESSAGE : ZRC=0xFFFFF91E=-1762
          SQL1762N  Unable to connect to database because there is not
          enough space to allocate active log files.

 

Answer

For APAR IC99700, there are two possible solutions you can do before attempting your upgrade.

    1. Double the size of the file system where your active log resides. All this space will be needed because the log files are copied from the old location to the new location (refer to APAR IC97073).
    2. Change the size of your active log by updating the ACTIVELOGSIZE in your dsmserv.opt file. Once you update this option, restart your Tivoli Storage Manage server, prior to your upgrade, to allow the new size to take effect. If this is the option you select, ensure you have double the space in your active log file system. After you complete the upgrade, start your server and go through your verification steps. Halt your Tivoli Storage Manager server and reset your ACTIVELOGSIZE option to your desired size and then start your server.

For APAR IC97073, there is no work around. Following a successful v7 upgrade, be aware that there is a chance the old log files will not be removed. These old files may need to be manually removed. Before removal, verification of the configuration from both the Tivoli Storage Manager and DB2 perspectives should be completed. Contact Support for assistance.

Related information

IBM Tivoli Storage Manager Upgrade and Migration Proces

written by Bosse

May 07

Archive and active log directories are full and server will not start

ActiveLog ArchiveLog Comments Off on Archive and active log directories are full and server will not start

Question

If a FULL database backup is not taken in time to prune the archive logs before the directory becomes full. Either the active log becomes full, or the active directory becomes full of the logs that could not be archived. The result is that the Tivoli Storage Manager server shuts down.

Cause

Tivoli Storage Manager server shuts down and archive log directory and active log directory are full. The server cannot be started again.

Answer

When the archive log directory or active log directory fills up, or when the pre-allocated active logs fill up, the Tivoli Storage Manager shuts down. In order to get the Tivoli Storage Manager server up and running, you must update the DB2 configuration to change the location of the active log directory to a new location. This will allow to active logs to free up space and then the Tivoli Storage Manager server can start. You can then clear the archive log directory by issuing database backups. Complete the following procedure:

1. Create a temporary directory large enough to place the active logs.
See dsmserv.opt for value of ACTIVELOGSIZE.

2. Open a DB2 command prompt:
Windows:
Go to Start > All Programs > IBM DB2 > DB2COPY1 > Command Line Tools > Command Window – Administrator.

AIX/Linux/Unix:
1. Open a terminal session.
2. Log in as the Tivoli Storage Manager instance user.

3. Update the DB2 configuration to specify the new location for active log directory that you just created. From the DB2 command prompt, issue the following commands:
set db2instance=SERVER1
db2start
db2 update db cfg for tsmdb1 using newlogpath <path_from_step1>
db2 connect to tsmdb1

4. The active log files will not be removed until the following ‘activate’ command is issued.
First perform a deactivation to ensure that the database is not already activated:
db2 deactivate db tsmdb1
Then run the activate command:
db2 activate db tsmdb1

Note: The active logs will be COPIED and RENAMED (not moved) to the new temporary directory that you specified in step 1.

5. You have 2 options to prune the archive logs to get the Tivoli Storage Manager sever back up and running:

Hide details for Option A: Have Tivoli Storage Manager prune the archive logsOption A: Have Tivoli Storage Manager prune the archive logs
You can have Tivoli Storage Manager prune the archive logs by issuing database backups. You will need to update the DB2 configuration to point the active log direction location back to the original location, and then issue the activate command to copy over the log files to the original location. Since these newly created active log files have space to write transactions, the Tivoli Storage Manager server can start, and you can initiate DB backups to prune the archive logs. Complete the following steps:

A.5.1. Update the DB2 parameter to point the location of the active log back to the original location.
See ACTIVELOGDIRECTORY value in dsmserv.opt.
db2 UPDATE DATABASE CONFIG FOR TSMDB1 USING NEWLOGPATH <path_to_activelogdir>

A.5.2. Issue the activate command to copy the logs to the original location:
db2 activate db tsmdb1

A.5.3. Start the Tivoli Storage Manager server in the foreground.
Open a command terminal and navigate to the server directory and issue the dsmserv command to start the correct instance. Refer to the command here:
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.srv.ref.doc/r_cmd_dsmserv_start.html

A.5.4. Run a database backup to prune some of the archive logs.
dsmserv backup db type=full dev=<your device class>

A.5.5. Review the archive log directory. Is the drive/volume free space still low? You will have to decide if you need to run a second database backup to avoid having the archive logs fill up again before the next scheduled database backup. This depends on the average growth of archive logs per day. Review the timestamps on the archive log.

Hide details for Option B: Have DB2 prune the archive logsOption B: Have DB2 prune the archive logs
You can have DB2 prune the archive logs by running a DB2 database backup.

B.5.1. Create a directory on a drive/volume with enough space to hold a full DB2 database backup.

B.5.2. From the DB2 command prompt, issue the following commands:
db2 deactivate db tsmdb1
db2 backup db tsmdb1 to <path_to_database_directory>

Examples:
Windows: db2 backup db tsmdb1 to C:\dbbackup
AIX/Linux: db2 backup db tsmdb1 to /tmp/dbbackup

The following message will appear once the backup is complete:
Backup successful. The timestamp for this backup image is: 20090721130818
At the end of this backup, archive logs will start pruning.
Note: depending on the size of the database and archive logs, this could take a while to complete the backup.

B.5.3 Review the archive log directory. Is the drive/volume free space still low? You will have to decide if you need to run a second DB2 database backup to avoid having the archive logs fill up again before the next scheduled Tivoli Storage Manager database backup. This depends on the average growth of archive logs per day. Review the timestamps on the archive log.
If need, issue another DB2 database backup.

B.5.4. Delete any DB2 database backups as follows:
db2stop
db2start
db2 connect to tsmdb1
db2 PRUNE HISTORY <timestamp> WITH FORCE OPTION AND DELETE

where <timestamp> is the timestamp that was displayed after the DB2 database backup completed. See step B.5.2, where the timestamp is: 20090721130818.

B.5.5. Update the DB2 parameter to point the location of the active log back to the original location.
Ssee ACTIVELOGDIRECTORY value in dsmserv.opt.
db2 UPDATE DATABASE CONFIG FOR TSMDB1 USING NEWLOGPATH <path_to_activelogdir>

B.5.6. Connect to the database to start automatic moving of active logs from the temporary location to original active log location.
db2 force application all
db2stop
db2start
db2 connect to tsmdb1

The connect command will trigger DB2 to move (not copy) the active logs to the original directory.
Note: depending on the size of the active logs, this process can take a long time.

B.5.7. Start Tivoli Storage Manager server in foreground.
Open a command terminal and navigate to the server directory and issue the dsmserv command to start the correct instance. Refer to the command here:
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.srv.ref.doc/r_cmd_dsmserv_start.html

B.5.8. Take a full database backup by issuing the following commands:
disable sessions
backup db type=full dev=<your device class>
enable sessions

Now that the Tivoli Storage Manager server is up and running, attention should be paid to see how often FULL Tivoli Storage Manager database backups are needed in order to prune the archive log directory.

written by Bosse

May 07

Configuring DB2 log archives to Tivoli Storage Manager

TSM 7.1 Comments Off on Configuring DB2 log archives to Tivoli Storage Manager

Question

Configuration steps required to send DB2 archive log data to the Tivoli Storage Manager Server

Cause

Technotes 1391970 (Configuring DB2 and Tivoli Storage Manager in Windows) and 1635414 (Configuring DB2 and Tivoli Storage Manager in Unix / Linux) describe configuring the DB2 DB backups to Tivoli Storage Manager, but additional steps are required in order to send log archives.

Answer

This document presumes that you have already configured the DB2 backups to Tivoli Storage Manager, so the steps for registering a nodename, configuring dsm.opt/dsm.sys, etc., are not included here. Reference the links to the above technotes for more information on that aspect of the configuration.

To ensure the DB2 archive log data can be successfully stored on the Tivoli Storage Manager Server, perform the following steps:

1) Define an archive copygroup for the default management class within the active policyset of the domain in which the node resides.

    DEFINE COPYGROUP domain_name policyset_name mgmtclass_name TYPE=ARCHIVE DESTINATION=archive_stgpool_name RETVER=NOLIMIT

Note: It is recommended to specify a different storage pool hierarchy for the archive logs than the DB2 database backups, especially if the backups are including the DB2 archive logs (which is the default behavior for a full DB2 backup). If the DB2 archive data is in the same storage pool as the DB2 backup data, you can run into the scenario where a DB2 archive log retrieve (which occurs during a DB2 backup) will preempt access to a volume that a DB2 backup session has mounted. This will cause the backup to fail.

2) If the archive logs will be stored using a different management class other than the default, create the additional Archive copygroup for that management class using the syntax in step 1. It is recommended to define an archive copygroup for the default Mgmt Class even if you plan to use a different management class than the default, since this will be checked during the session initialization.

3) Validate and activate the policyset to enable the changes made in the previous steps.

      VALIDATE POLICYSET domain_name policyset_name

ACTIVATE POLICYSET domain_name policyset_name

On the Tivoli Storage Manager client where DB2 resides:

4) Update the database configuration in DB2 to save the log archive data using the Tivoli Storage Manager API interface. Log in as the instance owner (for Windows, also open a ‘db2cmd’ window) and update the db cfg for the databases in question:

      db2 update db cfg for

db_name

    using logarchmeth1 TSM

If you’re specifying a different management class than the default, include the Mgmt Class specification as follows:

      db2 update db cfg for

db_name

      using logarchmeth1 TSM:

mgmtclass_name
5) Restart DB2 to pick up the changes to the DB CFG.

Related information

Configuring DB2 and Tivoli Storage Manager in Unix / Li
Configuring DB2 and Tivoli Storage Manager in Windows

written by Bosse

May 07

Tivoli Storage Manager server upgrade from V6 to V7 fails with ANRI1043E

TSM 7.1 Comments Off on Tivoli Storage Manager server upgrade from V6 to V7 fails with ANRI1043E

Problem(Abstract)

A Tivoli Storage Manager server is upgraded from V6 to V7. The upgrade fails with the following error :
ANRI1043E: An error occurred while dropping the DB2 instances.

Symptom

The following errors are logged :


=====> IBM Installation Manager> Error

ERROR: Error during “install” phase:

Details:
ANRI1043E: An error occurred while dropping the DB2 instances. To review errors and correct any issues, review the log files in /var/ibm/InstallationManager/logs/native.

 

Cause

Orphaned DB2 instance causing the db2idrop command to fail during upgrade

 

Environment

Tivoli Storage Manager Server on Unix/Linux

Diagnosing the problem

1. Run the db2ilist command to verify the DB2 instances that are configured on the system. For example :

# /opt/tivoli/tsm/db2/instance/db2ilist

tsmi
tsmiold

In this case, it shows two instances, tsmi and tsmiold. The tsmiold instance is an instance that is no longer in use.

2. Run the db2greg command to verify the DB2 registry. For example :

/opt/tivoli/tsm/db2/bin/db2greg -dump show
V,DB2GPRF,DB2SYSTEM,xvotsmsrv01,/opt/tivoli/tsm/db2,
I,DB2,9.7.0.6,tsmi,/home/tsmi/sqllib,,1,0,/opt/tivoli/tsm/db2,,
V,DB2GPRF,DB2INSTDEF,tsmi,/opt/tivoli/tsm/db2,
I,DB2,9.7.0.4,tsmiold,/home/tsmiv/sqllib,,1,0,/opt/tivoli/tsm/db2,,
V,DB2GPRF,DB2FCMCOMM,TCPIP4,/opt/tivoli/tsm/db2,
S,DB2,9.7.0.6,/opt/tivoli/tsm/db2,,,6,0,,1359560348,0

Again, in this case, the registry shows references to the tsmi and tsmiold instances

3. Run the db2idrop command to remove the old instance (tsmiold). The command fails with the following error :

DBI1081E The file or directory /home/tsmiold/sqllib/bin is missing.

 

Resolving the problem

Remove the orphaned DB2 registry reference to the old instance (tsmiold) with the following command :


/opt/tivoli/tsm/db2/bin/db2greg -delinstrec instancename=tsmiold

Retry the upgrade once the orphaned instance is removed

written by Bosse

May 07

Server failed to start after upgrade SQL5035N

TSM 7.1 Comments Off on Server failed to start after upgrade SQL5035N

Problem(Abstract)

After a server upgrade, it fails to start with the follwing error:

SQL5035N The database must be upgraded to the current release.

Symptom

When trying to start the Tivoli Storage Manager server after an upgrade and you receive the following error:

ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1568) Thread (5): Missing sqlState=55001, sqlCode=-5035 from table. Returning rc = 9994. SQL5035N The database must be upgraded to the current release. SQLSTATE=55001

 

Cause

The database instance did not upgrade properly during the upgrade process.

 

Diagnosing the problem

Run the following DB2 commands as the Tivoli Storage Manager instance user (default: tsminst1):

db2start
db2 connect to tsmdb1

You will get:
SQL5035N The database must be upgraded to the current release.
SQLSTATE=55001

 

Resolving the problem

You will need to manually complete the upgrade of the database instance using the commands below:

db2start
db2 upgrade database TSMDB1
Note: The upgrade command will take time, depending on how big the database is. There will be no progress messages given. You can monitor the CPU/Memory usage to verify the process is running.

After the upgrade completes, try the DB2 connect commands again and it should be successful.
db2start
db2 connect to tsmdb1
Now you can start your Tivoli Storage Manager server.

written by Bosse