Question

Move Volume to different folder on the same server

Laserfiche Version 9 Administration Backup and Recovery

Updated August 21, 2015

asked on August 14, 2015

I am trying to move a volume with a fixed path from:

\\servername\images\volumeName

\\servername\testimages\volumeName

When I do, I get an error: "Fixed path for a volume must either be empty or contain a valid VOLUME.ID file and may not be a subdirectory of the current fixed path. [9264]

Is this move not allowed since the it looks like it is a sub directory (under the server) of the existing path? How else can I move the volume?

Thanks in advance.

0 0

Answer

SELECTED ANSWER

replied on August 17, 2015

I figured out the issue. I am moving this volume to a location where our test system has a volume of the same name. So, it saw the exiting volume ID file.

I've resolved the location problem.

Now when I change the path, I get an error that says "There is insufficient space on the target device. [9053]"

It is a 40GB volume with 303 GB of free space on the disk. What's going on?

0 0

Replies

replied on August 14, 2015

Did you move the volume first in Windows Explorer and then try to update the volume path in the Laserfiche Administration Console? That may be why you're getting that error message.

If the volume files are already in \\servername\testimages\volumeName but the path in the Laserfiche Administration Console is \\servername\images\volumeName, then you can do the following:

In Windows, rename the \\servername\testimages\volumeName folder to \\servername\testimages\volumeName-DONOTDELETE
Create a new blank folder, \\servername\testimages\volumeName
In the Laserfiche Administration Console, change the volume path to \\servername\testimages\volumeName
Now in Windows, look in \\servername\testimages\volumeName and see if there is a volume.id file. If there is, copy it into \\servername\testimages\volumeName-DONOTDELETE. If there is no new volume.id file, then that's fine
Rename \\servername\testimages\volumeName to \\servername\testimages\volumeName-DELETE
Rename \\servername\testimages\volumeName-DONOTDELETE back to \\servername\testimages\volumeName

Now confirm that the documents can be viewed normally in the Client.

2 0

replied on August 14, 2015

It seems like your volume may be missing the VOLUME.ID file then. So to confirm, the volume files are still in \\servername\images\volumeName and the fixed path of the volume is set to the same?

In the Laserfiche Administration Console, create a new volume.
Go to the location where you created the new volume and copy it's VOLUME.ID file
Paste the copy of the VOLUME.ID file into \\servername\images\volumeName
Open the VOLUME.ID file that's in \\servername\images\volumeName using a text editor like Notepad
Under the [Required] line, you should see a line that reads [NewVolumeName]=[SomeHexValue]
You will need to change that line so [NewVolumeName] is the name of the actual volume you're working with. As for [SomeHexValue], you'll need to use the correct value for that volume. You can find this by querying the vol table in the database and getting the value stored in the localid column for that particular volume.
Once the VOLUME.ID file has been modified to use the correct volume name and hex id value, go back into the Laserfiche Administration Console and try changing the fixed path again. Make sure that when specifying the new path, that it is empty first.

2 0

View 2 previous replies

replied on August 14, 2015

I will try this.

What should I have done?

If I did it right, what would cause this to process to fail? We have tried this kind of thing before and never been able to move a volume without a bunch of extra work. I want to understand what should be done so I can avoid this.

Thanks for the detailed help.

0 0

replied on August 14, 2015

The main cause of this type of issue is if the VOLUME.ID file is missing. If the volume did have the VOLUME.ID file and you were changing the fixed path to a new location that is empty, then there shouldn't have been any issues (with the presumption that the Laserfiche Server service account has read/write permissions to the new location).

If you find that there are other volumes in the repository that do not have a VOLUME.ID file as well, you can use the steps above to make one for them.

To get more information about this process, perhaps you can also test this on a smaller scale. Create a new volume and import a document or two into it. Then change the fixed path to a new empty folder. The Laserfiche Server should disable the volume while it moves the files automatically. After the move is completed, re-enable the volume.

0 0

SELECTED ANSWER

replied on August 17, 2015

I figured out the issue. I am moving this volume to a location where our test system has a volume of the same name. So, it saw the exiting volume ID file.

I've resolved the location problem.

Now when I change the path, I get an error that says "There is insufficient space on the target device. [9053]"

It is a 40GB volume with 303 GB of free space on the disk. What's going on?

0 0

replied on August 18, 2015

Please contact your Laserfiche reseller to open a support case so the matter can be further investigated.

0 0

replied on August 21, 2015

Just to wrap around, the answer we came up with is to move the volume manually and the update the fixed path. This is what I've had to do in the past.

Has the built in function of moving volumes via the admin console worked for anyone?

Not sure if it matters, but I'm doing this from the admin console on a client workstation, not the server.

1 0

replied on August 14, 2015

The only thing I did was go into the admin console and change the fixed path. I did not create a folder in explorer.

There is a folder now, but the images never moved. I can open them find in LF client. The fixed path in the admin console did not change to the new path.

Is this the right way to do it?

0 0

You are not allowed to follow up in this post.

Question

Question

Move Volume to different folder on the same server

Answer

Replies

Sign in to reply to this post.