Content Replication and Archiving Across Azure VMs

We're in the process of migrating our MFiles on-prem instance between azure virtual machines. I went through the process of backing up and restoring the Vault databases with an azure blob storage as well as migrating the vault files themselves with an Azure storage account linked between the two virtual machines. Compressing, moving, and unzipping, the files themselves was a real pain but it's done. However, we're not ready for the migration yet, so my thought was we could use the scheduled content replication and archiving feature to essentially 'sync' the vaults across virtual machines. The issue that I'm running into is that my azure storage account doesn't seem to be a valid drive when selecting a location for my content package. Does anyone know of anyway to export/import MFiles content packages to a Azure storage account? I'd rather not have to write a folder watcher for the virtual machines to shuttle the content packages to the storage account for export/impot. Any help or suggestions would be greatly appreciated and if I'm going about this the wrong way or if there is a better way to go about this I'm open to suggestion. 

Parents
  • I've seen these instructions for using Azure File Share for replication, hopefully they work for you:

    1. "Path from the server:" must be the UNC path of your File Share, for example \\mytestaccount.file.core.windows.net\externalsource
    2. Use "Set Account" to add the details of your Storage account.
    3. "This account": must be the name of your Storage account, for example mytestaccount
    4. "Password:" must be the Primary Key of your Storage account

    The other option would be to use the cloud storage offered by M-Files to move the content packages, but for this you need to request a connection string from our support since your vaults are not hosted on M-Files Cloud. Refer to Use replication via cloud storage in the user guide for more information.

Reply
  • I've seen these instructions for using Azure File Share for replication, hopefully they work for you:

    1. "Path from the server:" must be the UNC path of your File Share, for example \\mytestaccount.file.core.windows.net\externalsource
    2. Use "Set Account" to add the details of your Storage account.
    3. "This account": must be the name of your Storage account, for example mytestaccount
    4. "Password:" must be the Primary Key of your Storage account

    The other option would be to use the cloud storage offered by M-Files to move the content packages, but for this you need to request a connection string from our support since your vaults are not hosted on M-Files Cloud. Refer to Use replication via cloud storage in the user guide for more information.

Children
No Data