How to move a metastore to a new Storage Account in unity catalog?

[Arnold_Souza]

Hello, 

I would like to change the Metastore location in Databricks Account Console. I have one metastore created that is in an undesired container/storage account. I could see that it's not possible to edit a metastore that is already created. I could also see that it's not possible to create a second metastore in the same Azure region. Well, does anyone know how to move this metastore to another storage account? I was wondering, if I simply move the container to a new Account via Az Copy and then delete and recreate the metatore in the new location, will it work? 

[Arnold_Souza]

Hello @Retired_mod ,

Thank you for the reply. 

As you can see in the image below, there is no step 6. I mean, there is no button to edit the storage path and include a new one. 

Because of that, I was wondering: what if I copy the current container to the new Storage account I have, then I delete the current Metastore and recreated it with the new Storage Account address already populated with the contents of the old metastore. Will it work? I would bet the data will be there (tables) but I do not know about the governance side (Table access controls)

[mohnishbhagde]

Did you get a solution for this? 

[Joaquim]

I would like to bump this thread as I am in a similar predicament. New to Databricks here and I have a dev and prod environment in one Databricks account. I created the dev metastore (with "dev" in its name) in the same region where my production metastore would also reside. Dev & prod live in the same region. So my understanding here (because I can't have the metastores in the same region) is that I would have to have dev and prod in separate regions. So I'm assuming that I'm in the same boat where I would need to move my current dev metastore bucket to a different region and am wondering if this would be possible.

[ac0]

Bumping this thread as well.

[Bakkie]

Facing the same challenge. Any update on this?

The ADLS Gen 2 path seems rather definitive when setting up a metastore:

[tushar55555]

any luck on this?

[Bakkie]

We ended up 1) deleting the metastore (which only contained catalogs/schemas/tables), 2) creating a new one in the desired storage account and 3) re-populating it by running all Delta Live Tables pipeline. All our underlying raw data is stored in another storage account in delta format. Our Tableau connection to the SQL warehouse remained intact due to the same naming.