Skip to Main Content
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.

Status Not under consideration
Created by Guest
Created on Apr 16, 2015

unable to take backups of a database using tdp 6.4.1 for SQL 2012 with always on node

Tsm server 6.4 qnd we are trying to take one backup in two different management classes using tdp sql 2012 with always on feature enabled.
For tye second backup which should go to the new mgmt, it fails with the merge test. Because backup happens using the always on node name instead of the nodename provided in the opt file. Tdp sql version is 6.4.1.
the only workaround we have found is by changing the filesystem name at the tsm server which is not the best practice.
So please provide the solution in which the backup can happen using the nodename specified in OPT files instead of the always on nodename.
tried changing the parameters of tdpsql.cfg but did not work.
changed
Usealwaysonnode no

Please provide a solution for this issue.
thanks in advance

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
    |
    Apr 20, 2015

    It has been a long time that we are waiting for your inputs.

  • Guest
    Reply
    |
    Apr 17, 2015

    Hi,
    Any suggestion on this??