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

Question

Question

volume consistency utility shows 0 documents but images exist in win folder

asked on November 13, 2015

After migrating all documents from Old_Volume to New_Volume, we can still see a very large number of images still exit under the volume folders in windows folder structure.

We ran the Volume Consistency Utility and it comes back with "Total Images = 0".

Also the Statistics tab of the volume shows Documents = 0.

1. Statistics --> Statistics tab of Volume

2. Volume Path details

3. Volume Consistency Utility

4. Physical Files: Images still exist on Windows Drive under Old_Volume folder

 

Do you think it's safe to delete this Old volume from the windows system?

1. statistics.jpg
2. Volume Path details.jpg
3. Volume Consistency Utility.png
4. Physical Files.png
0 0

Replies

replied on November 13, 2015

The volume path in lfadmin ends in $, but the path in explorer does not.

1 0
replied on November 16, 2015

Robert,

Sorry can you please explain a bit. Thanks

0 0
replied on November 16, 2015

It looks like your volume path is incorrect in the admin console, explorer shows that the volume path does not end with $, but the path in admin console does. This is why the admin console reports zero files, it has a path that doesn't exist.

0 0
replied on November 17, 2015

Robert,

Yes, that is fine and expected.

The actual config in LF points at a hidden share (hence the $), and this also shows through in the volcon report.

 

The Windows Explorer screenshots show it without the $ because we have mapped to the root of the drive (l$) rather than the share itself, but the issue remains that the physical TIF files still exist in the share.

 

I am currently checking with our customer as; What user account is running the LF Server service? Does the user running LF Server service has appropriate access rights to delete documents from the windows folder (where the images are left over)?

Answer to above questions would rule out the possibility of documents getting migrated to new volume successfully  but haven't been removed from the windows folder because of not having the appropriate access rights.

0 0
replied on November 17, 2015

Robert,

I have checked and all the permissions seems fine. The service account running the LF Server service has got appropriate access rights to delete from all folders and sub-folders in the windows drive. Also, we have made service account as local admin but still no luck. On the other hand, a lot of old volumes are empty after the migration and they have similar access rights etc. as well.

Any suggestions please?

0 0
replied on November 17, 2015

Check the event viewer on the LFS machine for an event with more information.  But if all of the files migrated to the new volume, you should be able to delete the files from the old path without a problem.

0 0
replied on November 17, 2015 Show version history

We did look into the event logs and didn't find any issues.

This is a live systems and that's why we are hesitating to delete the images from old volume without 100% confidence.

I have now raised a support ticket for this.

Thanks

0 0
replied on November 16, 2015

Robert,

Yes, that is fine and expected.

The actual config in LF points at a hidden share (hence the $), and this also shows through in the volcon report.

 

The Windows Explorer screenshots show it without the $ because we have mapped to the root of the drive (l$) rather than the share itself, but the issue remains that the physical TIF files still exist in the share.

 

I am currently checking with our customer as; What user account is running the LF Server service? Does the user running LF Server service has appropriate access rights to delete documents from the windows folder (where the images are left over)?

Answer to above questions would rule out the possibility of documents getting migrated to new volume successfully  but haven't been removed from the windows folder because of not having the appropriate access rights.

 

 

You are not allowed to follow up in this post.

Sign in to reply to this post.