Azure Cassandra Managed Instance - Request/Restore Backup

Question

Azure Cassandra Managed Instance - Request/Restore Backup

Felipe K 0

Hello we are evaluating a restore backup from Azure Managed Instance for CassandraDB in one specific RG to another (same region), we are checking for this possibility, but currently portal is not allowing us to open the request (MS docs reference only they can perform the action), even with support plan.

Is this possible? If so we have support plan and pay for Cassandra, any reason we cannot open the request to perform the restore?

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-14T14:13:55.09+00:00

Hello Felipe K

Thank you for posting your query on Microsoft Q&A platform.

Could you please share us any screenshot of the error message you are experiencing?

Thanks,

Suchitra.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-06-10T10:40:38.1033333+00:00

Hi @Felipe K ,

Thank you for your patience while we worked with our backend engineering team regarding your restore request.

We would like to share an important update before proceeding further.

To successfully perform a restore operation between clusters, the target cluster configuration must align with the source cluster, including the datacenter name. This is a required condition for the restore process.

In the current setup, the datacenter name in the staging cluster differs from that of the production cluster. Due to this mismatch, the restore operation cannot be initiated at this time. Required next step

To proceed, kindly create a new target (staging) cluster with the following configuration:

The datacenter name should match exactly with the source (production) cluster

The overall cluster configuration (such as number of datacenters and nodes) should remain consistent

Once the new cluster is ready, please let us know, and we will promptly proceed with initiating the restore request with our backend team.

Thank you for your understanding and cooperation.

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-06-15T22:02:44.01+00:00

Hi @Felipe K ,
As confirmed by the PG team, this scenario is not possible for Azure Managed Instance for Apache Cassandra.

Currently, Microsoft does not support migration via backup download/restore or reusing the same cluster name for staging/production replacement in MI Cassandra. Additionally, as mentioned in the previous communication, for restore operations to work, the target cluster must exactly match the source cluster configuration, including the datacenter name. Since the current staging cluster has a different datacenter name, the restore cannot be initiated.

Please create a new staging cluster with:

Same datacenter name as production

Matching cluster configuration (datacenter count and nodes)

Once completed, please confirm so we can proceed with the restore request from the backend.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-06-17T23:21:26.6666667+00:00

Hi @Felipe K ,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

1 answer

Your answer

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-14T14:13:55.09+00:00

Hello Felipe K

Thank you for posting your query on Microsoft Q&A platform.

Could you please share us any screenshot of the error message you are experiencing?

Thanks,

Suchitra.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-06-10T10:40:38.1033333+00:00

Hi @Felipe K ,

Thank you for your patience while we worked with our backend engineering team regarding your restore request.

We would like to share an important update before proceeding further.

To successfully perform a restore operation between clusters, the target cluster configuration must align with the source cluster, including the datacenter name. This is a required condition for the restore process.

In the current setup, the datacenter name in the staging cluster differs from that of the production cluster. Due to this mismatch, the restore operation cannot be initiated at this time. Required next step

To proceed, kindly create a new target (staging) cluster with the following configuration:

The datacenter name should match exactly with the source (production) cluster

The overall cluster configuration (such as number of datacenters and nodes) should remain consistent

Once the new cluster is ready, please let us know, and we will promptly proceed with initiating the restore request with our backend team.

Thank you for your understanding and cooperation.

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-06-15T22:02:44.01+00:00

Hi @Felipe K ,
As confirmed by the PG team, this scenario is not possible for Azure Managed Instance for Apache Cassandra.

Currently, Microsoft does not support migration via backup download/restore or reusing the same cluster name for staging/production replacement in MI Cassandra. Additionally, as mentioned in the previous communication, for restore operations to work, the target cluster must exactly match the source cluster configuration, including the datacenter name. Since the current staging cluster has a different datacenter name, the restore cannot be initiated.

Please create a new staging cluster with:

Same datacenter name as production

Matching cluster configuration (datacenter count and nodes)

Once completed, please confirm so we can proceed with the restore request from the backend.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-06-17T23:21:26.6666667+00:00

Hi @Felipe K ,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Answer 1

Yes, but Cassandra MI restore is service-managed; it is not a portal restore or downloadable backup. Microsoft’s responsibility model states that backups are automatic and restoration is performed through an Azure support request.

Create the destination cluster in the same region and align its Cassandra version, datacenter name, datacenter count, node count/SKU, and networking with the source. Use az managed-cassandra cluster backup list to identify the backup, then include its ID, both cluster resource IDs, target datacenter, requested restore point, and business impact in the case.

If the portal will not create the request, open Help + support from the subscription that owns the Cassandra resource and select a technical issue for Azure Managed Instance for Apache Cassandra. The paid plan does not add a self-service restore button. If the service is absent from the picker, file through the subscription and ask for routing to the Cassandra MI backup/restore team.