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

Question

Question

Harddrive free space starting to be a little concerning

Laserfiche Version 10 Administration
Updated February 3, 2021
asked on January 25, 2021

We have a data volume on our server that is starting to get a little low on space.  This is on a virtual server and the way it was initially set up it can't be expanded "hot" unfortunately.  

So my question is:

Is there a way to migrate an repository off that drive onto another one, or a way to "extend" an existing repository to another drive?  

Thank you in advance!

0 0

Replies

replied on January 25, 2021

I'm not sure which type of volume your using, (physical/logical), but our repository is configured to use logical volumes, and when a drive starts getting full we just go into the settings and change the drive for the logical volume.

What that means is that when the current volume hits the size limit, when it rolls over to create a new volume it will do so on the new drive, and the old stuff can stay on the original drive. We have close to 30TB of data, so it is spread out across multiple virtual servers with multiple 4TB drives.

 

There's really a lot of options, but it all depends on what type of volume you're currently using, how much data you're dealing with, and what is best for your long term goals. For example, migrating existing data is possible, but it's also a very time consuming process if you have a lot to move.

1 0
replied on January 25, 2021

Volumes is your answer. This is a layer that the users do not see (unless you teach them how to manually alter the volume). You can move, and create new volumes on any physical storage without impacting the structure of the repository.

You can even use workflow to move files based on conditions to different storage types for speed, size, cost, etc. All in real time without any impact on users.

1 0
replied on February 3, 2021

Ok thanks for the guidance.  So in doing research I found conflicting ways to move the volume to a new drive.  (To me it sounds like the best scenario to copy the data to a whole new disk drive and then change the volume path to the new location and then delete the data in the old location).

But.  In looking I am finding conflicting documents on how to do this:

This is the one that looks the best and easiest (all data moved off old disk drive, thus freeing up space for the other repositories)

https://answers.laserfiche.com/questions/119488/best-practise-in-moving-volume-from-one-storage-to-another-storage#119495

But then I find this that says you have to move mdf files etc:  Help! 

https://www.laserfiche.com/support/webhelp/Laserfiche/9.0/en-us/AdminGuide/LFAdmin.htm#Moving_Transferring_a_Network_Repository.htm%3FTocPath%3DLaserfiche%20Administration%20Guide|Repository%20Administration|Moving%20Repository%20Data|_____1

 

0 0
View 3 previous replies
replied on February 3, 2021

The second article is regarding moving SQL databases.

To move a volume's storage location it is just a matter of updating the path, you will get a message that the files will be moved automatically for you when doing this.

If using a logical rollover volume, changing the path of the root will mean new rollovers will go to the new drive. If you want to move all the existing data update the path for each individual rollover and they will be moved.

Migrating volumes is different, this is creating a new volume and moving all entries to the new volume. If you do this you also need to migrate all the folders to use this new volume if you want new files to be placed in this volume.

0 0
replied on February 3, 2021

Ok so (you know I have follow-up questions :)

So I have a repository and it is currently located on D: drive.  (Screenshot attached)

So with your first comment : "To move a volume's storage location it is just a matter of updating the path, you will get a message that the files will be moved automatically for you when doing this."

So all I need to do is change the :/Defvol to say G:\HRJobs\Defvol?  And then it will move all the data for me?  Or do I need to copy all the data using robocopy to the new location first and then change the path?  Sorry... just trying to make sure.

volumemove.jpg
volumemove.jpg (120.87 KB)
Download
0 0
replied on February 3, 2021

You can actually do either. You can move the data first using robocopy, then update the path. This will cause downtime for the users though, and should only be done if you prefer robocopy for it's reliability.

After moving the files yourself, just update the path and the system will see that you already moved them and be done. (the message actually mentions this)

Or you can just change the path and the files will be moved, as the system will see that they still exist in the old path.

0 0
replied on February 3, 2021

Good deal!  I will try it with a much smaller one first.  Thank you for your help!  

0 0
replied on February 3, 2021

One quick question after reading it several times.

 

So you said the files will be moved.   So I assume that is a process that runs or does it start to happen immediately.  And therefore should be done after hours because it would affect server processing etc?

0 0
replied on February 3, 2021

It starts moving them immediately. I can not see how it would effect production, since if the file has not been moved it could open it from it's current location if smart enough. Although it does not specify if there is any downtime or not. Might be berried in some documentation somewhere.

If it doesn't make it clear, you could wait until after hours to start the process just to make sure.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...