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

Question

Question

Repository on two different physical drives

asked on June 30, 2016 Show version history

Ive seen this post: http://answers.laserfiche.com/questions/91753/Moving-files-to-the-second-volume--Is-it-done-automatically-or-manually

I have read the administration guide on roll over repository locations.

In that post Justin states "

'm still unclear if they are the SAME logical volume or two different ones. If they are logical children of the same parent volume, the rollover will happen automatically when the first volume reaches the provided size limit (or at the specified time period, if it's set up that way). The user wouldn't need to do anything and both would appear as the same volume to them - new files would simply go into the second one. If they are different volumes, there is no inherent rollover between them.

Regardless, changing the path (or any of the properties) of the parent logical volume will impact the defaults when the next rollover child is created. So if you wanted to ensure that the next volume will be on a different location, you can change the path now and it will be created there. Of course, if it's the physical volume, it will actually try to move the existing documents there right now, so make sure you're setting it on the logical parent. "

and 

"If your volumes are set up as logical volumes then it will happen automatically. However if they are two completely separate volumes with no connection between the two, it will happen manually. Please see https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/LFAdmin/Content/Volume_Rollover.htm and its child pages for more information. "

"If your volumes are setup as logical volumes" My screenshot suggests that both devices are logical volumes. "then it will happen automatically" but Its not. Fill the Default repository drive and the system errors out with no available space.

 

The link he provided talks more theory of what should happen but not what steps you need to take to ensure the system is setup as needed.

 

Based on my interpretation of the support provided by this site, this setup should work, but it is not working and im running out of space.

 

Can anyone help clarify how to fix this issue?

 

Edit: If this wont work because its on two different physical drives but are both setup as logical volumes than why would you just say that they all need to be on the same drive? I really hope this is not the case.

Rollover Screenshot.png
0 0

Replies

replied on June 30, 2016

No, this setup will not work. Rollover happens within the same logical volume. So Default is one logical volume with physical child volumes under the hood (Default000000, Default000001, etc). When the first child volume fills up, rollover occurs and new documents are redirected to the next child volume and so on. Creating documents in Default will never attempt to put documents in Default_2 because that's a completely separate volume.

Moving documents between volumes (from Default to Default_2) is called migration and is a user-initiated manual process.

That said, you can change the path to a logical volume to move it to a different drive. New child volumes will be created in the new location. Existing child volumes will stay where they are.

0 0
replied on July 1, 2016

So how does one tell the system to use two different drives (E: and F:) and roll over between the two? Because as of right now it seems that the only option is to take the partition from F: and add it to E: which is what the customer does not want to do.

0 0
replied on July 1, 2016

When you want the volume to stop writing to drive 1 and start creating new child volumes on drive 2, you update the logical volume's path in the Laserfiche Administration Console to point to the new location on drive 2.

0 0
replied on July 1, 2016

So any files already created in the repository are still accessable even though they are on the E: drive and ive told it to work on the F: drive? Also it wont migrate files already in the system automatically to the drive will it?

0 0
replied on July 1, 2016

Yes. As long as the Laserfiche Server service still has access to the E: drive, the files will still be accessible. Volumes on the E: drive will not automatically move to the new location.

0 0
replied on July 5, 2016

One major note that I feel has been overlooked in Laserfiche documentation. You want too make sure you adjust the repository location with enough space for the system to roll over on its own and select the new location. I spent two hours with support trying to "trick" the system into working in the new space. 

If you find yourself in the same situation as I did this past week, your best option is to have someone from support walk you though the process of tricking the system to rollover manually. 

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

Sign in to reply to this post.