Export/Import does not retain complete history

[muppal]

I am trying to copy the contents on FolderA from Repostority A to a new folderB into new repository B. I successfully used the export/import utility, and while there were no errors during that process, I find that the complete history is not present in the imported folder.
The version numbers have all changed as well. I was under the impression that the imported folder would be an exact copy of the original folder, history, version numbers and all. Thanks in advance for the help. -Madhavi

[muppal]

i am attaching the export/import log for your review.

[Beth]

Which version of Vault are you on?

It looks like some errors were logged during the export.

Can you tell me which areas look like they have the wrong version numbers?

[muppal]

We are running version 4.1.4 right now. I have attached a screen shot of a folder from both repositories. I exported and imported to the TestCM repository. I was hoping the history would be retained as in the original folder/repository.

[Beth]

What has happened to the PAM7.00 folder? Was it deleted, renamed, or possibly obliterated? The log says it may have been obliterated.

Were the items that were inside of that folder moved out into another folder?

Were you exporting at root or some lower folder? If lower, which folder are you exporting and importing?

There's some obliteration warnings in other spots as well.

[muppal]

Not sure what happened with the PAM7.00 folder, it may have been deleted, because when I get history at the root I don't see that folder being obliterated. However, there have been some folders/files under the PAMXG5 folder that have been obliterated. Would this be the reason the history is not being copied over correctly?
I am exporting $/PAMXG5 and all its subfolders from the GlobalPAM repository, and importing it to the TestCM repository.

[Beth]

Can you right-click $ and select properties? Then go to the deleted items tab. Is PAM7.0 listed there?

Can you run a history query on $ for only the action of obliterate?

[muppal]

Actually, it looks like PAM7.00 was renamed to PAMXG1.

[Beth]

Can you still check for any obliterates with the history query?

[muppal]

There are no obliterates for the PAM7.00 folder, but there are other obliterates in other folders, like the PAMXG5 folder.

[Beth]

Was PAMXG5/PAM/util/samplescommon ever moved or renamed? Or was one of it's parent folders ever moved, renamed, or obliterated?

[muppal]

Nothing in that folder. But i have attached the query results for anything deleted, moved, and obliterated in the PAMXG5 folder.

[Beth]

Normally, importing won't work at all when there are obliterates. In very few cases, a user is successful.

What you are seeing with your versions being different is that the earlier versions of those files came from someplace else, and it's likely to be from a folder that was obliterated after the file was moved to the location it's being exported from. Let's say your file has 50 versions, but from versions 1-30 it was in file $/Folder1 and from versions 31-50 it was in $/Folder2. Even though it was a move, when it's trying to find versions 1-30, it's going to look in the history of $/Folder1. If Folder1 was obliterated, then it will just import versions 31-50, but will restart the numbering back at 1 again.

Obliterates and Export/Import just don't go well together, because one needs history, and the other destroys history. There are warnings during the obliterate process about this.

[muppal]

ok, this explains a lot. Thanks for the help.

[Beth]

Feel free to let us know if you have any further questions.