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

Question

Question

Laserfiche in Azure Questions

asked on August 5, 2019

We are preparing to move our Laserfiche infrastructure to Azure and we are trying to determine if Standard or Premium SSD's are the best route to take.  Couple of questions for Laserfiche or anyone that has already gone through this:

  1. Would you recommend using Standard SSD's or Premium SSD's?
  2. Has LF or anyone ever done I/O bench mark testing?  One of our Laserfiche Application servers is a very heavy read/write system, so not sure if we should run premium SSD's makes sense based on LF specifications for writing to disks.
  3. Are there any recommendations or risks to physical drive size?  Does LF recommend multiple drives 4tb's each or just a single 8tb drive?

 

I am looking for answers from anyone that has possibly already gone through this kind of migration or even done an install like this for a large client.

Thanks

0 0

Replies

replied on August 5, 2019

I've never done an install of Laserfiche in Azure. The following is just my observations based on how Azure storage offerings work.

Initially, you should try to match your IOPs to what you currently have, and then scale from there. You should be able to use the tools on your SAN, or the Windows profiling tools to figure out what you need.

Also, you don't have to keep everything in the premium tier, since it can get expensive. You can have different volumes on different types of storage, depending on how often it gets accessed. There can be a 3x price difference between HDDs and premium SSDs. You can always start with standard SSDs and the move some volumes to something faster later on.

Storage on Azure is a lot different than local storage. By default, all storage is locally redundant. So, if you ask for 1 TB of storage, Azure will transparently manage two additional replicas of your data. There will always be two copies of the data in one rack, and another in a second rack. I only mention that, because it means we need a slightly different look at how storage is provisioned in the cloud environment. It's all done in software, and you're not actually connecting directly to physical disk. So, size and performance considerations get a little fuzzy.

For the slightly different option, you can look at something like Azure Files, which operates like a file share served from a SAN. The pricing is different, and you don't need to provision a set size ahead of time.

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

Sign in to reply to this post.