{"id":33414,"date":"2024-06-10T16:35:45","date_gmt":"2024-06-10T14:35:45","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=33414"},"modified":"2024-06-13T13:32:39","modified_gmt":"2024-06-13T11:32:39","slug":"m-files-migrate-vaults-to-a-high-available-environment","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/m-files-migrate-vaults-to-a-high-available-environment\/","title":{"rendered":"M-Files, Migrate Vaults to a High Available environment"},"content":{"rendered":"\n

If you read my previous blog<\/a>, you know why I’m doing a migration \ud83d\ude42<\/p>\n\n\n\n

If not let’s explain it a bit, since 1 year I play with M-Files using an VM in the cloud, but I reached the limits and running a lot of Vaults start to become costly for a simple playground.
Additionally as the VM is stopped during the night I can’t simulate a real prod environment.<\/p>\n\n\n\n

So I decided to move my Vaults to a nice On Premise and highly available environment (Multi Server Mode).<\/p>\n\n\n

\n
\"Be<\/figure>\n<\/div>\n\n\n

There are two main scenario: <\/p>\n\n\n\n

1. Firebird Vault<\/h2>\n\n\n\n

In case of a simple Vault is created using the embedded Firebird DB nothing really challenging.<\/p>\n\n\n\n

You perform a Full backup on the source<\/p>\n\n\n

\n
\"Vault<\/figure>\n<\/div>\n\n\n

You move the backup file to the target and restore it:<\/p>\n\n\n

\n
\"Restore<\/figure>\n<\/div>\n\n\n

Restoring a Firebird Vault can only be done on a local drive and cannot use the high availability features of my environment.<\/p>\n\n\n\n

If it is only for a small demo then it can be fine, otherwise we can do the following steps:<\/p>\n\n\n\n

Migrate to a Microsoft SQL Server<\/p>\n\n\n

\n
\"Migrate<\/figure>\n<\/div>\n\n\n

Enter the required information to connect to the MSSQL instance, be careful the “Basic user credentials” must be<\/strong> an existing login in the SQL Server instance, M-Files cannot generate it as you may need to configure it on another node. <\/p>\n\n\n

\n
\"SQL<\/figure>\n<\/div>\n\n\n

Click on “Test connection” to be sure everything is ok and ten proceed.<\/p>\n\n\n\n

After some minutes (depends the Vault size) the migration is done.<\/p>\n\n\n\n

But it’s not over yet, maybe you haven’t noticed, but it was not possible to change the Data Location.<\/p>\n\n\n\n

You must move it to a shared space in order to mount it to a second node, so for that.<\/p>\n\n\n\n