Files missing after Restore - file validation?

[jshipley]

We just upgraded from Vault Workgroup 2020 to Workgroup 2023 and we are now live on the 2023 server and mostly everything is working fine.  However we are getting some issues where the file is not is not found.  Here is the error:

Here is a screen shot of the log File Store log:

It says something about replication, which we are not using, at least I don't think we are and we dont' need it.

If I browse on the server to that location to find the file it is missing.

But I can get it on the old server from where the backup was taken from.

Any help would be appreciated.  Thanks

[jshipley]

Here is the Vault server console screen that shows the number of files in the store:

It has gone up some since yesterday when it was at 707585 but that's pretty slow.

[ihayesjr]

@jshipley 

It looks like you are missing many files in the file store on the 2023 server.

Go to the old server and navigate to the file store folder.

Copy all files from the old server to the 2023 server, skipping the duplicates.

This should bring back the missing files. The server task will remove any files it doesn't need overnight.

[jshipley]

Ok I will try that - thanks!  I think I'll start with a small folder and see how that works.

Is there any reason these could have been dropped during the backup/restore/migration?

[ihayesjr]

They should not have dropped during the backup or restore unless something prevented them from being copied.

[jshipley]

Ok here is another example.  CK120007.dwg.  It won't 'Get' the file from 2023.

And here is what the log file says:

12/13/2022 10:08:06 AM Replicating: Resource checksum failed for 'CK120007.dwg' version 12. Located in the file store at E:\Vault\FileStore\Vault\000\000\000\000\001\978\1978793\1978793_2352906_12.dwg.
12/13/2022 10:08:06 AM Could not validate or replicate resource 'CK120007.dwg' version 12. Located in the file store at E:\Vault\FileStore\Vault\000\000\000\000\001\978\1978793\1978793_2352906_12.dwg.

Here is the file store folder which shows the file in there:

Why would it say it's not there?

[ihayesjr]

Root problem with this error is the following log entry.

12/13/2022 10:08:06 AM Replicating: Resource checksum failed for 'CK120007.dwg' version 12. 

This error indicates that the file in the file store is most likely corrupt. Try replacing it with the same file from the old server.

[jshipley]

OK did that and same error:

This is bizarre.  It's the same file from 2020 and 2023 is saying it is failing validation.  At this point my only option is to Get these files from the 2020 and save and check them in one at a time.

[ihayesjr]

Before going that route, I recommend that you create a product support ticket so that it can be investigated more.

The support team will recommend the best next steps.

[ihayesjr]

In the mean time, run this command line on your server.

Vault 2023 Help | Validate File Store from the Command Line | Autodesk

[jshipley]

Ok I am running that.  Started it about 3 hrs ago.  There is no screen feedback.  How do I know if it is working or the progress?

thanks

[ihayesjr]

Open the Windows Task Manager to see if the ADMS executable is still running.

If it doesn't appear, the validation is complete, and you can open the ADMS Console and look at the console log file for the results.

[jshipley]

It looks like it completed the validation successfully.  And I don't see any errors.

Here is the console log from when I started the validation:

And here are the last lines from the log from 6:10 PM 

I have opened a case with Autodesk support so I am working with them also but I am trying to keep this thread alive as well.

[jshipley]

One thing that I would like to try is to find out what the database has that is making it fail the checksum validation on check out.  If I could compare the checksum in the old and new servers for a specific file that might be helpful.  Does anyone know of a way to work your way through the database table to get from a file version to the actual file and folder?

[ihayesjr]

@jshipley 

The checksum information in the old and new databases will be the same. An upgrade is not going to change those. Since the file store validation did not return a checksum failure with any of the files, that error is masking the real problem. 

Continue to work with support so they can figure out your real problem.

[jshipley]

Ok thanks.