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



Repository at 6 TB Need help figuring out where to go from here

asked on February 15, 2018


I don't see where I can submit a ticket for help so I guess this the next best thing :)

I'm no to this organization and they have been running Laserfiche for many years (trying to find out now) and we ran out of space today. :(  So, that said, does anyone have some best practices for setting up storage?  Is there a way to generate a report to see how much space we are using over a timeline?  To kinda gauge our future usage.

Thank you for your time,


0 0


replied on February 15, 2018 Show version history

Hi Sue,

I'm sure other people can provide more complete answers as far as reporting and such, but our organization has a repository containing over 26TB of images/files and is growing at somewhere around 750GB per month.

Our configuration involves a collection of 4-6TB drives on servers specifically dedicated to hosting the LF Volumes (i.e., separate from the app server) and a single logical volume configured in the LF Admin Console set to roll over at 20GB.

As each physical volume is filled, Laserfiche automatically rolls over to a new 20GB physical volume within that logical volume.

Outside of Laserfiche, we have monitoring tools that check the available space of each drive on the server, and we are alerted when a drive reaches 80%, 90%, and 95% of capacity.

When a drive gets close to capacity, we use the LF Admin console to change the UNC path of the default volume to point to a drive with more available space.

When the current physical volume reaches the 20GB limit, the next rollover volume will be created in the new location meaning we can continue using the same default volume but still have the files distributed across multiple drives and/or servers.

All of our primary documents go through a very specific set of processes and we track a variety of data including image/file sizes in an external database that we use for reporting.

You can find some helpful information about volumes and best practices in this document.

2 0
replied on February 16, 2018

Thank you so much Jason for taking the time to respond.  This looks like a very balanced and well thought out solution.  I will bring it to the group as a starting point.  Thank you again!  Have a great weekend. Sue

0 0


replied on February 15, 2018

In general, there isn't a way to say how your repository has grown over time.  There are a few tricks that might apply, depending on your configuration.

  1. Audit Trail could be recording document creation events, and while it doesn't record how large they are, maybe the rate of creation is close enough for your purposes.
  2. Your backup software may have logs recording how much data is backed up at each run.
  3. If your volumes are set to roll over by size you can get an idea of how long it takes to reach the limit.
1 0
replied on February 16, 2018

Thank you Brian for your response :)  I will include your response in my email to my work group also.  Have a great weekend and thanks again!  Sue

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

Sign in to reply to this post.