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

Question

Question

Laserfiche Large Volume Move

asked on April 24

I have a large volume, over 8 TB that has been copied to a new location.  I need to change the volume path since it is slightly different then the current.  I know I can change the path within LF Admin for the volume I am working with, however this could take a very long time due to the size and I don't have much down time for the change.   

Could the path be changed within MS SQL first, then change the path within LF Admin to match it?  If so any estimate on time for this for the size of the volume?   If so what table(s) need to be updated and what would that look like?

 

Current:   E:\Volume\

New: F:\Folder1\Volume\

 

Thanks!

 

 

0 0

Replies

replied on April 24

You can give this a try:

Update Volume Path
Declare @ReplacementString nvarchar(236)
Declare @FindString nvarchar(236)
Set @FindString = 'Current Path'
Set @ReplacementString = 'Replacement Path'

Update vol

set fixpath = REPLACE(fixpath ,@FindString,@ReplacementString)

 

1 0
replied on April 24

Thanks Blake!  I tried without the variables using the same SQL commands. Which worked great on a very small batch.  

1 0
replied on April 24 Show version history

Using the Admin console takes forever if your using a logical volume, it takes like 30 seconds each between hundreds of windows that need to be opened. For a static volume you can update it in one step. For logical volumes I always shut down the service and update directly in the database, never had a problem doing this.

There is a table called vol that contains the path for all and you can run a simple find and replace script like discussed in this post.

https://stackoverflow.com/questions/1629201/sql-replace-old-values-with-new-ones

We could really use an option to update logical volume paths just like static volumes can be updated in a single step.

0 0
replied on April 24

For nearly any large file migration, my recommendation is to copy the files outside of Laserfiche using robocopy or similiar. Then, stop Laserfiche server service, run your robocopy copy script again to true up incase any files were in flight.

Finally, change it in SQL in the vol table. If you have sub volumes you will need to update all of them, but the table is fairly friendly. Restart Laserfiche. Only the smallest of installs we use the built in tools.

Obviously backup SQL before doing this.

0 0
replied on April 24

Thank you both for responding so quick.  I did a small test within dev and it worked perfectly.  

 

 

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

Sign in to reply to this post.