Question

Detached Volume failed. No files are there when i re-attach the volume.

Laserfiche

Updated December 23, 2015

asked on December 21, 2015

We are moving our Laserfiche to a new server. On the old server we detached the volume. During the detach we received an error on the server saying "Laserfiche Admin Console: Operation timed out."

The volume showed as detached so I reattached the old volume to the old server that we were detaching and the files do not show up in the repository. They are still there in the physical locations ("c:\repositories\volumes\repo_name\00\00\00") but they are not in repository when I look in the client.

I'm trying to figure out how to get them back and I think I'm missing something. Any help would be great. thanks

0 0

Replies

replied on December 21, 2015

In the c:\repositories\volumes\repo_name folder, was there a volume.id file?

0 0

replied on December 21, 2015

yes there is.

0 0

replied on December 22, 2015

Hello all,

We are working with the VAR through a Support Case, but for public note one thing to look for is the toc.xml file in the volume folder (same place as the VOLUME.ID file); this file contains the information on repository documents in the volume. If it is corrupted (as may be the case here, given the Operation Timed Out warning) then behavior like this can manifest.

Unfortunately there isn't much to be done except detaching/exporting again. The volume may need to be restored from backup. Typically we recommend exporting before detaching, as through that method one can verify that the detached/exported volume is valid before committing to a detach.

Again, for this particular instance we are still troubleshooting through a support case but the above notes may apply for a general case when behavior such as this arises.

Hope this helps!

0 0

replied on December 23, 2015

James,

That is exactly what is going on. toc.xml did not export as it should. Is a restore from the DB my only option in this case?

Thanks

Nate

0 0

replied on December 23, 2015 • Show version history

Hi Nate,

If the volume files are inaccessible because the currently-attached volume reads as empty, then unfortunately yes. This is why we recommend exporting first: exporting creates a copy of the volume in the repository, leaving the original intact. This way if the process is interrupted and something like this happens, another attempt can be made because the original volume is still attached.

For further details specific to this case, please contact your VAR to have them update the currently-open Support Case with us.

Best,
James

0 0

You are not allowed to follow up in this post.

Question

Question

Detached Volume failed. No files are there when i re-attach the volume.

Replies

Sign in to reply to this post.