Question

Network Drive got full - needed to switch to new one - not sure if set this up correctly

Laserfiche

Updated October 15, 2024

asked on May 11, 2023

The network drive that our volumes exist in became full, so we created a new drive to save to.

Then I went into the Admin Console and attempted to create a new volume so it would switch from the old drive to the new one. I tried to set up the new volume the same way as the existing volume, but I don't think I did it correctly.

It looks like the old volume is a group of volumes and my new volume is just a singular volume. I don't know how to create a group of volumes in here. It does have a maximum size limit on it, and it does not have a rollover schedule.

Any help would be greatly appreciated

0 0

Replies

replied on May 11, 2023

If the old volume is a group of volumes, then it may have been created as a Logical volume, which is generally the better option and would make things a lot easier for you. With a Logical volume, you don't actually need to create a new volume at all.

Logical volumes will automatically create sub-volumes and roll over to a new one when the configured size limit is reached and that is likely what you're seeing.

The additional benefit of the logical volume is that all you need to do is point it at a new drive and it will start creating the new volumes there instead without breaking the previously created ones.

For example, our largest repository uses a single logical volume spread out across multiple drives. The logical volume rolls over to a new sub-volume (folder) at 20GB, and when a drive is close to being full we just change the path for the logical volume and it'll start using that new drive for the new sub-volumes without impacting the existing ones.

1 0

replied on May 11, 2023 • Show version history

Thanks for the response, Jason! I actually noticed that after submitting this, that it should have been a logical volume.

So now, I have my new logical volume set up, but I have this physical volume that I was using for a few hours. There's a bunch of stuff in it now. Would you know how I move the stuff out of that physical volume into the new logical volume I just created?

0 0

View 1 previous reply

replied on May 11, 2023

Before you do that, it is worth asking why you want a separate logical volume at all. You can change the path on your original volume to use the new drive without having to manage a separate logical volume.

Basically, I wouldn't think you need a new/old logical volume at all, just change the path of the original and it will work the same way just spread across multiple drives the same way it spreads across multiple folders.

Generally speaking, there's more downsides than benefits to having multiple logical volumes unless there's a good reason to do it that way, such as separating files that use different volume security or something.

Either way, the best bet for moving things is probably workflow. You can use advanced search syntax in a Search Activity. For example ({LF:VolId="7"})

Then, use a for each entry loop with the Migrate Entries task to move things from the desired volume.

You can use the LF Client to do a Within Volume search with the Search Syntax box visible as a quick way to get the query. Basically, you're just running a search for all entries stored in your "oops" volume.

Then, plug that search syntax into the Search Repository activity in workflow, and loop through the results.

You'd then set the Migrate Entry activity to move each entry. The ellipsis menu will let you select the destination volume; it also shows the volume id values if you want to get them that way rather than using the LF Client get the query.

0 0

replied on October 15, 2024

Hi @████████

Just to confirm, changing an LV's path to a new drive will leave all the old data from the previous drive accessible, correct?

Once the LV rolls over from drive 1 to drive 2 (because path was changed before the latest physical volume got full), users will now be able to view entries from both drives, even though now the LV is only pointing to drive 2.

Thanks

0 0

replied on October 15, 2024 • Show version history

@████████ That is correct. When the current volume rolls over, it will start using the new drive path.

Existing entries will still stay on their current volumes and will remain accessible; it should be effectively seamless to the end users.

As a result, new entries go to the new volume, but changes to existing entries can still affect the older volumes unless you migrate them first.

For example, if you add new pages or electronic files to an existing document, those files are stored on the same drive/volume as the rest of the document, so it is still possible to see growth on a drive even if the logical has rolled over.

1 0

replied on October 15, 2024

Thank you!

0 0

replied on May 11, 2023

On a secondary note, you should check with whoever manages your servers about setting up some kind of alerts for when drive space gets too low.

In our environment, we always keep Laserfiche repository volumes on their own drives so they will never be impacted by other systems/processes, and we set up alerts based on available drive space; the threshold is based on the amount of space needed to create a new "chunk" for the logical volume.

For example, if your logical volume is set to rollover at 20GB, then set up an alert for when the available drive space dips below 30 or 25. Then, switch the logical volume's drive so that the next time it rolls over it will use the new drive with more space.

0 0

replied on May 12, 2023

Hi Jason, this is all very helpful. I super appreciate this education. I have the OOPS volume cleared out and deleted, and all I have now is my original volume, but updated to the new drive path.

I will say, I was expecting new documents to start saving to the new drive, but it looks like they're continuing to save to the old drive. Is that maybe just because LF hasn't deemed the old drive full enough yet, you think? (see attached screenshots)

LFAnswers-VolumePath.png (166.79 KB)

| Download

LFAnswers-Drives.png (33.53 KB)

| Download

0 0

replied on May 12, 2023

Yes that is correct. Logical volumes "roll over" when they reach the set size limit but they'll continue using the active folder until that point.

Most likely the "current" volume folder is still within the configured limit, but once it rolls over the new folder should use the new path.

0 0

You are not allowed to follow up in this post.

Question

Question

Network Drive got full - needed to switch to new one - not sure if set this up correctly

Replies

Sign in to reply to this post.