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

Question

Question

Laserfiche Volume Size Realistic Limitations

asked on November 23, 2016

All research and communication I can find now suggests their is not real performance limitation on Volume Size.

I looked at the limitations of 2^31 Pages (2 Trillion +)

It is really just a matter of convenience regarding managing the Volume for back up etc..

Reason I ask is I want to Encrypt my Volume without worrying about Encrypting new or adding a password to numerous Roll Over Volumes.

So I was thinking just one Physical Volume.

Any concerns, gotchas?

 

0 0

Answer

SELECTED ANSWER
replied on December 5, 2016

It's mostly the operational inconvenience of having to unlock them every time the server restarts.  Disk-level encryption is likely going to be more performant, but the difference might be small enough that you wouldn't notice.

0 0

Replies

replied on November 23, 2016

For what its worth, we generally only do new setups with a single volume unless their backup strategy prefers some degree of separation. I find it just makes it easier overall to run with a single volume.

We also run it this way in our internal Laserfiche server(20TB data) and it only has 2 physical and 0 logical volumes. We use one for our fast storage and one for a slower archive storage location that gets automatically moved after a certain time period.

0 0
replied on November 24, 2016

Thanks for the practical example

0 0
replied on November 23, 2016

Volume encryption is not well-suited to active volumes, you should be using disk-level encryption tools for that.  So that's not a reason to avoid multiple volumes.

The main reason to limit volume sizes is for compatibility with backup procedures and media.  Rolling over volumes based on dates can make it easier to implement retention policies.

0 0
replied on November 24, 2016

In what sense is it not well suited I did see that it's primary intention is exporting or archiving but no real detail on cons on a live volume. Is it more just regarding the requirement to add the Encryption Password when Server is restarted.

Inability to support the Logical Volume?

Is it a performance issue? Risk of forgetting password?

0 0
SELECTED ANSWER
replied on December 5, 2016

It's mostly the operational inconvenience of having to unlock them every time the server restarts.  Disk-level encryption is likely going to be more performant, but the difference might be small enough that you wouldn't notice.

0 0
replied on December 6, 2016

Thanks

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

Sign in to reply to this post.