You are viewing limited content. For full access, please sign in.

Question

Question

Azure Files Setup

Laserfiche Version 10
Updated December 3, 2024
asked on August 20, 2021

I am trying to set up Azure files with laserfiche. We have set up everything in the azure side and connected the storage to a drive within the server. I am able to create and modify files within the drive, however when i use the laserfiche admin tool to create a new repository i get a 9044 invalid path error, and when i attempt to unregister/move/register an existing repository i get a 9004 i/o error. 

 

Does anyone have experience in setting this up?

0 0

Replies

replied on August 20, 2021
  1. How are you accessing the Azure Files share?  do you have it mounted as a network drive, or are you trying to access it via a UNC path?
  2. Where is the repository server, on a VM within Azure or hosted elsewhere?
  3. Side note... I recall a slide from one of the Empower sessions indicating Azure Files was not recommended from a performance perspective. 
0 0
View 2 previous replies
replied on August 20, 2021

1. Its mounted as a drive

2. The VM is hosted within azure.

3. Yeah, we have had that discussion and are looking into testing the difference first. It may end up being a solution for archive files. 

0 0
replied on August 20, 2021

I'd try the underlying UNC path instead of the drive letter.

\\<storageAccountName>.file.core.windows.net\<fileShareName>

I'm also curious as to what benefit you see in Azure Files for repository volumes that you don't get with Managed Disks? Standard SSDs are something of a sweet spot because repository volume access patterns tend to be heavy on random read with lots of I/O on tiny files.

0 0
replied on August 23, 2021

We are working on transferring about 40-50 years worth of hard copies into the repository and our main guy for building the server is concerned that we wont be able to attach enough disk space to the server without hitting a limitation. The good news is alot of this data is could eventually be put in cold storage too.

 

I will give the UNC path a try too, thank you!

0 0
replied on August 23, 2021

You can attach quite a lot of disk space to Azure servers.

Azure Standard HDD, Standard SSD, and Premium SSD Managed Disks all go up to 32 TB. 

A D4as_v4 (4 vCPU, 16 GB RAM) instance supports up to 8 data disks. Total: 281 TB.

A D8as_v4 (8 vCPU, 32 GB RAM) instance supports up to 16 data disks. Total: 562 TB.

A D16as_v4 (16 vCPU, 64 GB RAM) instance supports up to 32 data disks (and it caps here; all larger sizes support 32 as well). Total: 1.12 PB.

Do you actually have petabyte-scale data? If not, you don't need to be concerned about being able to attach enough disk space. If yes, the real answer is to figure out how to get as much of it into the Cool/Archival tiers of Azure Blob storage as possible or the storage costs are going to be horrific. At 1 PB with all Standard HDD 32 TiB S80 disks, you're looking at $366,163/year before backups (West US 2 region pricing).

Standard Azure Files shares cap at 5 TiB each (100 TiB with "large file share" feature enabled). Not terribly different in the grand scheme.

0 0
replied on December 3, 2024

Hi Samuel,

 

We have a client that want to user this Azure Files as the new volume to Laserfiche.

How they can configure it on the Laserfiche side (Admin Console) using the UNC of their volume folder. I try to create a new volume. In "Path to Volume," I don't know where to input the UNC of their Azure File Storage. If it's in field "Fixed" or "Removable"? I tried the "Fixed" and "Removable", "I get this error Error Code: 9044
Error Message: Invalid volume path. [9044]"

 

Regards,

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...