IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Add a new idea Subscribe
Status Not under consideration
Workspace Data Lineage by Manta
Created by Guest
Created on Jul 3, 2025

RELATED IDEAS

Support Disaster Recover plans for Manta standalone

Add features or documentation on how IBM Manta standalone can be deployed with disaster recovery so that Manta can be recovered.

Manta standalone is deployed by users on their infrastructure so Manta software may not support DR. However the PLAN or reccommendations of how DR could be implemented would be helpful.

For example, when Manta is set up on a different server, what needs to be done to migrate workflows, connections, lineage to this system. What other data (eg: keycloak configuration?) needs to be migrated to bring up the DR system. How much time would this migration take. Can the source manta system be kept running while this migration occurs, or does it need to be shut down to ensure the backup is valid?

Needed By Quarter
  • Admin
    Jakub Moravec
    Oct 2, 2025

    Hi Dev,

    I can confirm that these topics are being addressed in the the new re-architectured product - both on SaaS (IBM watsonx.data intelligence) and on-prem IBM Knowledge Catalog on Cloud Pak for Data.

    As for the current/classic standalone Manta, what we can do is improve the documentation linked above to add backup/restore instructions for specific components. But at the moment we don't have plans on providing instructions on how to configure Manta to use cluster-deployed ActiveMQ, Neo4j, etc ... as we wouldn't be able to contain the QA for such wide variaty of deployments.

    Best Regards,
    Jakub

    Reply
  • Guest
    Jul 10, 2025

    Thanks Jakub. This was helpful. We looked into this link in the past, and there were certain limitations we faced.

    1. The restore doesnt work reliably when the exported data is large.

    2. The restore takes a long time to complete/fail

    3. Not all artifacts are backed up such as Manta config files, keycloak configuration, etc. so the coverage isnt sufficient.

    We ultimately decided to go with the following approach:

    1. Use thirdparty tools to take a full VM backup of the system, preferably when Manta has been shut down.

    2. Store the backup with structer permissions so that a backup once created cannot be modified.

    3. Restore the entire VM when a disaster occurs.

    This approach works for our current needs, but could be better:

    1. The whole VM backup can reasonably be taken only once a day, so when we recover, we lose about a day's worth of changes. Hence our recovery point objective (RPO) will be about 24 hours.

    2. Since Manta does not have a replication (online) mechanims, there isnt a way to reduce the RPO to minutes.

    The underlying storage technologies (neo4j, activeMQ) do support some multi-node, so theoretically if IBM were to publish some instructions on how to connect Manta to an activeMQ cluster, use MySQL in Keycloak instead of h2DB, store h2DB on NFS, use neo4j cluster instead of embedded nodes, then we could get the RPO down to a few mins, because a restore would need manta to start on another server but connect to these same MySQL, NFS and Neo4j clusters.

    I spoke to Caroline about this and she said that these are things being done on the SaaS solution. Could you confirm if that is true? If so, an appropriate DR plan may be to switch to the IBM Manta SaaS solution.

    Reply
  • Admin
    Jakub Moravec
    Jul 3, 2025

    Hi Dev,

    we have a document listing some of the APIs that can be used for backup/restore at the moment, apart from installing Manta on a VM and have a backup/restore solution for the whole VM, these are the best options at the moment. The doc does not cover all Manta funcinalities at the moment, but it can be exampanded if needed. Can you review the part that is coverd currently and provide feedback if this solution is feasible for you? https://www.ibm.com/docs/en/software-hub/5.1.x?topic=administering-backing-up-restoring-features-manta-automated-data-lineage

    Thank you,
    Jakub Moravec
    IBM Manta Data Lineage product team

    Reply
  • Guest
    Jul 3, 2025

    Filed as response to TS019717125

    Reply

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.