did anybody listen to the Readme?
1. Client installation
2. Server Update2 Installation
3. Database Update
4. Rebuild Search Indexes
ok, we have done, and then?
Summary of Issues Addressed
Enable Purge: ...Before enabling Purge on existing vaults, it is strongly recommended to run Autodesk Reference Repair Utility on those vaults and repair any references that are identified by the utility as missing from specific parent file versions.
How should this work?
1. The Reference Repair Utility needs approx 2 month to analyse our Vault (700.000 files, 430 GB)
2. We should repair references that will be purged subsequently?
3. Has anybody seen any result of Reference Repair Utility?
Parent Version 42
Latest Version 56
Parent Version 18
Latest Version 57
This makes definitely no sense?
We want to have the exactly workaround for performing Update 2.
In time we have updated our Vault backup on a test server and we have purged it.
After that we have made a overnight job with Reference Repair Utility on one of hundreds assembly groups with the shown results above.
Please help, Norbert
Please see mroe detailed help on the utlity on the WIKI
Please note too there is a high level video walkthrough, explaining the repair process under the main Wiki topic here: http://wikihelp.autodesk.com/Vault/enu/Help/Help/0
I think there you have misunderstood me
It's not about how I run the Repair Reference, but when.
The readme for Update 2, is that it should be executed strictly before the first purging.
Yes, before you start using Purge, we strongly reommend that you run the Reference Repair Utility and repair any missing references the utility may find.
Anil Chintamaneni (Autodesk)
Has anyone of you an idea what time it will be handled Repair Reference?
1st The run in our case would be extrapolated 2 months.
2nd The repair would have to be added manually in the list (time?)
3rd When everything is repaired, then I purge the vault and all that I have repaired for weeks is cleared by the purging?
What is the real reason that Autodesk says it all references necessarily be repaired before the purging?
Can someone explain to me? We have no logical explanation for it.
As described in the thread the issue we are resolving relates to missing references which could eventually become incorrectly eligible for purge.
If you continue to purge without identifying and repairing these missing references you risk purging required files. This is why we advise completing the repair process first.
In terms of the time taken to repair, if you have multiple vaults you can repair files that have missing references in one vault first, turn on Purge on that vault and move on to next vault. You can also speed up the scanning process by running the Reference Repair Utility on multiple Client workstations and scanning different folders at the same time. Please note that with this approach, you will essentially be tying up each machine for the time taken to run that scan and consume a license in the case of “paid for” versions.
Thank you, we looked at the video.
We hope that no one has such a vault which you have presented. Our Vault is configured on Unique Filenames.
The recent scans run on all errors. We obtain any XML file.
Incidentally, this is unreasonable workaround anyone.
That has shown us that we will do that in no case, too.
We will synchronize the local file store (with Get Latest) then we will consider purging after Update 2 on the server.
We are on Vault 2012 Collaboration. The help wiki says that Vault workgroup and above will automatically repair dangling references under certain conditions and that a manual repair process will be required for files that do not meet those requirements.
How do I know if the automatic repair was successful?
How do I know if I need to run the manual repair utility?
How do I know when I can enable purge?
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.