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

Question

Question

Volume Storage on Isilon (On-Prem )

asked on December 13, 2022

Our organization is would like to move-away from extremely large volumes/data files on our local servers. Our desire would be to migrate all existing Laserfiche volumes onto our Isilon. As a pilot for this action we are wanting to spin up a test repository and have the volume for that repository exists in the Isilon. 

From what I could see in the repository creation wizard we are only able to use local paths for the volumes. (I tried manually inputting the previously mapped file path on the Isilon, with no success unfortunately.)

 

I have two questions:

 

1. Is our goal even possible with out current Laserfiche system? (We are using on-prem not Cloud)

 

2. If so, what are the steps I need to follow after creating the repository? (I created it and currently have the volume saved locally on the LF server we use for that environment.)

0 0

Answer

SELECTED ANSWER
replied on December 13, 2022 Show version history

I don't have any experience with Isilon, but:

From what I could see in the repository creation wizard we are only able to use local paths for the volumes. (I tried manually inputting the previously mapped file path on the Isilon, with no success unfortunately.)

This is a common mistake. You can only use a drive letter for local physical drives - typically c:, d:, e:. Mapped paths are defined at the session level - they are controlled by user settings and are set up as part of the login process. A process running as a Windows service won't have the same mappings as the interactive user. Any network folder location needs to be specified using UNC paths (\\machine\share\folder).

3 0
replied on December 13, 2022

I tried that first but I was using the web admin tool and then switched over to the local machine and never tried that way again. I went straight into trying to map it. 

It did not balk upon the first change of volume path so far so good. Thanks for the insight. 

2 0

Replies

replied on December 13, 2022

Your Laserfiche server doesn't care where the physical volume image and document files are so long as there's a UNC path or drive share it can see and access like any other.

The best way to migrate volumes is to do it by individual physical volumes in the Windows Admin console and manually copying the data from your server to the new location. Disable the physical volume when users don't need to see the files in it, manually copy the physical volume over to your new drive/UNC location, update the path in the properties of the physical volume, enable again, and log into your repository and see if you can access the files. 

If you can, you're good. If you can't switch the path back and troubleshoot. Cause is almost always account running Laserfiche Server service doesn't have access rights to the remote drive.

In theory, you can change the path in physical volume properties and Laserfiche will do it for you, but it takes forever for the process to complete. 

 

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

Sign in to reply to this post.