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

Keep transaction logs online as long as possible

The DB2 database has to allways retrieve all transaction logs from backup, even though the information might still be online.
------------------------------------------------
Here is an description how the backup is working today in DB2

The current DB2 procedure is:
1. Write to an active log file until that log file becomes full
2a. Start writing to next log file
2b. backup the full log file
3. If backup is ok, rename the log file to a new sequence number
---------
And here is an example of how this could be improved:

Suggested workflow:

1. Write to an active log file until that log file becomes full
2a. Pick the oldest "log file" that are marked as "backed up";
and rename that file to a new sequence number.
Start writing to this file
Remove the "backed up" informenation about the old log file
2. backup the full log file (last switched log file)
3. if the backup is ok. Mark that log file as "backed up"

Idea priority High
  • 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
    |     Feb 8, 2014

    Thanks for your request and sorry for the great delay in response. The issue here lies with DB2 and is not something that we can improve. There may be some incremental improvements from DB2 in this area, but it does not appear to be a broad issue with our customers so we do not expect significant changes. As an alternative, FlashCopy Manager  could address this issue since it would allow the backups and restores to occur much more quickly. The roll-forwarding of the logs would take more time, but that might not be as much of an issue with the faster restore operation.

  • Guest
    Reply
    |     Sep 28, 2011

    An example of the flow:
    DB2 has 3 active logs.
    LOG1 : is active
    LOG2 : empty
    LOG3 : empty

    when LOG1 is full, the LOG will be backed up.
    The LOG will be renamed after successful backup.

    LOG1 : renamed to LOG4

    LOG2 : is active
    LOG3 : is empty
    LOG4 : is (now) empty, but actually contains information about LOG1
    ----------
    If this would have been changed to a similar flow as for Informix.

    LOG1 : is active
    LOG2 : is empty
    LOG3 : is empty

    when LOG1 will be full, the LOG will be backed up.
    If the LOG backup is successfully backed up, the LOG will be marked as backed up.

    LOG1 : backed up
    LOG2 : is active
    LOG3 : is empty

    next switch; same procedure...

    LOG1 : backed up
    LOG2 : backed up
    LOG3 : is active

    next switch:
    - rename the oldest LOG file only if the LOG has been marked as backed up.

    LOG1: will be renamed to LOG4

    LOG2 : backed up
    LOG3 : backed up
    LOG4 : is active (the old LOG1 information will be overwritten)

  • Guest
    Reply
    |     Sep 19, 2011

    Talk to INFORMIX to see how they have improved this.

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.