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

Question

Question

Rollover volume size - Pro's and Con's for changing the size? (Disaster Recovery vs performance considerations)

asked on December 12, 2013

During a recent Disaster Recovery test procedure  it was discovered that a client had to change each and every rollover volume to point to a new slightly different mapped location on an identical but differently named NAS. 

 

What is the reasoning for having the default rollover size at 20 gigs? Is there any reasons not to have it at say, 100 gigs?

 

What ways have you taken to minimize this solution. The first thing that comes to mind for me is to map the hard drive - but I've ran into issues before with VM level HD changes triggering a license invalidation. 

 

If Laserfiche is running under a windows service account, is there a reliable way to map those drives to a letter so that you only change that aspect on disaster fail over?

 

0 0

Answer

APPROVED ANSWER
replied on December 12, 2013

20GB is around 500,000 pages (blank and white image and text), so it was a reasonable size for your typical Avante installation where it was expected that volumes would be segmented off either by department or by year.

 

Depending on your repository expected growth, you could set higher sizes.

 

I don't think there's a reliable way of mapping drives for services because Windows doesn't support them well.

1 0

Replies

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

Sign in to reply to this post.