IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace Storage Protect Family
Categories Spectrum Protect (Server)
Created by Guest
Created on Sep 19, 2011

RELATED IDEAS

TSM Server is backing up transaction logs twice

The TSM Server is backing up the transaction logs twice.

1. The DB2 is automatically backing up the transaction logs to ARCHIVELOGDIR; at each log switch.
2. The TSM Server will backup the db2 database using: DB2 BACKUP DB TSMDB1 ONLINE USE TSM
Due to that "INCLUDE LOGS" is default parameter, the command will actually be: DB2 BACKUP DB TSMDB1 ONLINE USE TSM INCLUDE LOGS

At end of DB2 backup, all transaction logs used by this "image/backup" will be sent as part of the backup.

The problem is that the transaction logs is not on the primary disk anymore, due to that DB2 has allready automatically backed up the files to ARCHIVELOGDIR
DB2 has to restore the transaction logs to original place, just so that DB2 can backup them again.

3. After a complete "image/full" DB2 backup, the TSM Server will backup the ARCHVIELOGDIR to TSM
This is the second time the same transaction logs would be protected.

Idea priority Low
  • Guest
    Reply
    |     Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |     Jan 18, 2013

    Thank you for submitting this enhancement request, we do understand the requirement and the rationale behind it but unfortunately we do not plan to implement this function.

    The log files in the archive log directory are not a "backup" per se.  When a log file is full and no longer referenced by an active unit of work, they are transitioned to the archive log.  However, once in the archive log directory, these archived log files may be needed for direct read by DB2, such as during server restart and performing crash recovery against the database to establish transaction consistency.  
    the underlying database system (DB2) automatically manages the log file locations for optimal performance, this means that sometimes while performing under heavy load, DB2 may use all the active log space to support in-flight transactions in which case the files in the archive log will be the only instance of that log file etc. 
    With regards to make a switch to "EXCLUDE LOGS" for the way TSM performs it's DB backup. Yes, this may speed up the database backup and yes it may reduce the size needed for the database backup.  However, this may result in a database that is not transactionally consistent in the event of a restore and in particular of a restore where the existing archive log files are not present/available (consider a full DR case where recovery at a DR site is needed and the archive log files from the production site are not available).  So going this route could position a customer with data loss or an unusable TSM server depending upon the transaction state of the database in the backup (since it's 'missing' some of its logs). As a data protection product, TSM is not planning to make a change that can put the data we are chartered with protecting at risk.

  • Guest
    Reply
    |     Sep 29, 2011

    I do not agree. First, only a few transaction logs are included with the backup and therefore only thos logs are backed up twice. Only the logs required to make the DB consistent are included. I remember the time when the include logs option was not available in DB2 and the problem is that when you restore from a online backup, you need to get the logs from a different media. If the media for the logs is unavailable, you can't restore the DB. Also, if you just want to restore without rolling forward, including the logs make a restore from an online backup faster and more simple. The parameter include logs by default have resolved this and I think this is preferable in "pure" DB2 and TSM/DB2 environments.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.