IBM Data and AI Ideas Portal for Customers


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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2
Created by Guest
Created on Feb 9, 2015

Ability to backup/clone a database across the network (redirected restore)(RIMS)

Verizon needs the capability to issue a set write suspend IO command on database. Get the data to another instance at another location and bring it up. Informix has this ability and Verizon likes it. This is called a redirected restore. Verizon's databases are too large to be able to backed up and restored in a tradional manner in a timely manner. Note from customer: Jill and/or Colin, This has become very hot lately! Is there any way, either via DB2 native commands, or using Netbackup to do a backup of a source system and restore it to a target system without actually storing the output on disk or tape (Informix redirected restore)? I know we can do a backup of a remote DB to a filesystem on that remote system, or backup to an NFS mounted filesystem, but in both those cases, there's a backup file that is created, and in the case of the remote DB backup, you still need to ftp the image to the destination server. Also, I know you can backup/restore to/from a named pipe, but the reader/writer operations have to be on the same local server, and the restore process has to be kicked off before the backup process (how useful is that?). The business problem, is that it takes too long to recreate an HADR environment and there's a need for additional disk to support large DB backup images, after actually declaring a DR. We had a situation last week where we were within minutes of declaring DR on IVAPP North production, due to a System Administrator opps. The only thing that prevented us from declaring DR was the amount of time and effort it would have taken to 'rebuild' the old primary once it was available (at least 1 week). Being without DR for that long is not acceptable. We had put a formal request in for DB2 providing the equivalent functionality as Informix's redirected restore, what is the status of that request? Another note: During conversations with one of our Informix DBA managers this morning, Tommie Stroup, he indicated that Informix supports an operation called Redirected Restore that provides capabilities that we find very useful in that environment. Essentially, this operation allows the restoration, or even an initial materialization, of a Cold Backup taken at a primary site to be delivered over the network to a secondary, geographically diverse site, for purposes of restoration. He has found this feature extremely useful for a number of purposes, which does not require sending tapes or other media to the secondary location.
  • Guest
    Apr 11, 2019

    You can do the backup/restore via named pipes even via network borders.

    1. source system create 1-n named pipes (mkfifo /tmp/my_backup_pipe_1 ...)
    2. target system  create 1-n named pipes (mkfifo /tmp/my_restore_pipe_1 ...)
    3. from target system "connect" two pipes (ssh <source host> -c "cat /tmp/my_backup_pipe_1" > /tmp/my_restore_pipe_1)
    4. Start restore on target from local restore pipe
    5. start backup into source system pipes
     
    amount of pipes parallelizes the process and performance depends on I/O subsystem and amount/size of tablespaces