This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Hi Jeffrey,
Thanks for the idea.
We are aware that syncing the configuration between two Instana backends would be very useful for the scenarios you are describing.
At present this capability is outside the scope of what we can deliver. We are actively exploring technical approaches that could make such synchronization possible in the future, but the work is still early and we do not have a solution to offer today. We plan to revisit this idea in Q1 2026 to assess whether we can address it then.
We tried the Migration option. But it failed
[root@host tmp]# stanctl migrate --air-gapped -f dump-20250731102105.tar.gz --install-type production --download-key *********** --cluster-data-dir /mnt/instana/var/data
⠹ Checking node: [0s] ✓
⠋ Extracting migration data [0s] ✓
⠋ Migrating config [0s] ✓
⠋ Adding Instana Helm repo [0s] ✓
⠧ Setting up the cluster [22s] ✓
⠦ Applying pre-requisites [1m2s] ✓
⠼ Starting cluster components [0s] ✓
Error: no Postgres images found to import
migrate also corrupted the backend as we were not able to stop or start cluster after the above error. So we had to uninstall and redeploy the backend to make it running again.
Later it was confirmed by support (TS019947888) that migration from Standard Edition to another installed Standard Edition is not supported. We mist do a fresh installation on the destination side. This is not acceptable RTO for the customer as a fresh installation and bringing the DR side instance online has to be within couple of mins (<5min). And considering a scenario of a upgrade or patching requirement on the primary Instana server they need the secondary instance running. In this case both would be off line.