Vault Folder Export failing

[BigBrett]

Vault Pro 10.0.2.30936

I am attempting to export Vault folders prior to deleting them (trying to clean out old code) but the export attempts fail with a message that the tree structure could not be built.

Here are log entries for two failed exports:

2018/10/24 7:01:18 AM <generic>: [<No Name>:11] [System.Web.Services.Protocols.SoapException: 1108 : FailDBInvalidTreeRecords
2018/10/24 7:01:49 AM <generic>: [<No Name>:1] Folder Export: Error in ProcessResults_ProcessTransaction() An exception was encountered retrieving the Tx Information for $/AllyCAD34_Help. Tx: 91720 Previous Tx: 83014 [1108 : FailDBInvalidTreeRecords] [System.Web.Services.Protocols.SoapException: 1108 : FailDBInvalidTreeRecords

2018/10/24 7:04:38 AM <generic>: [<No Name>:11] [System.Web.Services.Protocols.SoapException: 1108 : FailDBInvalidTreeRecords
2018/10/24 7:04:52 AM <generic>: [<No Name>:1] Folder Export: Error in ProcessResults_ProcessTransaction() An exception was encountered retrieving the Tx Information for $/CivDes63. Tx: 91720 Previous Tx: 83014 [1108 : FailDBInvalidTreeRecords] [System.Web.Services.Protocols.SoapException: 1108 : FailDBInvalidTreeRecords

[Tonya]

Have you performed any obliterates in this repository? If so, the Vault Export/Import tool will most likely not be successful.

You have the most recent version of Vault installed so my next suggestion would be to try to export without deleted items.

Thanks,

Tonya

[BigBrett]

There have been plenty of obliterates to try and reduce the overall database size. I am selecting not to export deleted items.

So, if the export tool cannot handle obliterates I must do my own thing to create a code backup before I delete and then hopefully obliterate these very old code entries ?

I have been caught before when deleting and then an obliterate fails due to the presence of some other shared item. It would be helpful if you guys looked at a set of tools that will export without failing due to deletes/obliterates, and will obliterate irrespective of previous shared code that is already deleted. Our database is 20GB in size and we need to reduce it as it is mostly old, redundant code that will never be touched again.

[Tonya]

Agreed, there is room for improvement with the Folder Export/Import Tool in regards to obliterates.

In Vault 10.0.2, we made some minor advancements with Folder Export/Import. If you don't already have this installed, I would suggest downloading it as well. Please keep in mind that your Vault Server has to be 10.x in order to use the Vault 10.0.2 client.

Thanks,

Tonya

[BigBrett]

Unfortunately, as shown in the first post, we are already on 10.0.2.

I can get around the export by creating a zip file after a Get of the relevant folder, which I know will lose history but these are very old applications no longer supported so history is of no interest.

Then however, I want to delete and then obliterate those specific folders. I can predict now that old deleted/obliterated shares and branches are going to be a problem, so I would like to reiterate my request for a utility that will obliterate with no regard for such links.

[Tonya]

Thank you for your feedback in regards to the obliterate feature. We have had others suggest the same request and I will make sure to express your concerns in the work item ticket.

Tonya