nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Preserve version history when copying content

Kavitha_Sundaram

We are looking to implement a content archival solution in TS 6.7.2(Windows 2003). The requirement is as follows.
When the content has expired, the content will need to be moved into a branch (either sub-branch or a parallel branch, whichever works) along with its version history.
Which command-line tools should i use for copying the content?
Could i use OpenDeploy? Does it maintain version history?

TIA.

Find more posts tagged with

Comments

nipper

Try using the "Copy to" menu item. It retains EAs and *may* include history.

You can use iwmigrate but that is a pain.

Adam Stoller

We are looking to implement a content archival solution in TS 6.7.2(Windows 2003). The requirement is as follows.
When the content has expired, the content will need to be moved into a branch (either sub-branch or a parallel branch, whichever works) along with its version history.
Which command-line tools should i use for copying the content?
Could i use OpenDeploy? Does it maintain version history?

TIA.

If you're looking for CLTs - I'd suggest iwcp and/or iwupdate. The history of the file should be tracked back to the original in the source branch even though there is a "hole" there from whence the original file was copied (assuming you're deleting the original after copying it for archival purposes).

Set yourself up a little test scenario:

smwangi

I don't think there is way to do what you want easily.. Your file in the new branch will always have "Copied from **** " as the first version and the rest of the history will remain in source branch.

The only way to do this I is I beleive
1) duplicate the strore,
2) do a reverse delete in new store copy. ie. delete everything but the unwanted files
3) use iwmigrate to copy the new branch in new store into orginal store but to a _deleted_files_branch (now with just unwanted files) . Your deleted files will be here with all their history

4) delete duplicate store

This might be overkill. Consider your requirements.

Vips

iwcp may not be able to maintain all the versions while copying takes place, instead iwupdate has to be used to maintain all the versions. I just the ran the scenario mentioned by GHOTI and could see all the versions being maintained in Branch B even after deleting the content from Branch A

pann0204

We are looking to implement a content archival solution in TS 6.7.2(Windows 2003). The requirement is as follows.
When the content has expired, the content will need to be moved into a branch (either sub-branch or a parallel branch, whichever works) along with its version history.
Which command-line tools should i use for copying the content?
Could i use OpenDeploy? Does it maintain version history?

TIA.

As per the suggestions in this thread mentioned, u can use iwcp/iwupdate or easily can use 'Copy to' from the edit menu, but none of these will preserve your older versions if you delete the source directory. There is a related topic in TS admin guide.

Regards,
Pawan

Adam Stoller

As per the suggestions in this thread mentioned, u can use iwcp/iwupdate or easily can use 'Copy to' from the edit menu, but none of these will preserve your older versions if you delete the source directory. There is a related topic in TS admin guide.

Regards,
Pawan

Are you sure about that?
If you delete the source branch - yes, you will delete all the old version history, but if you just delete the files in the source branch, their versions should remain intact.
Is there a specific section in the Admin Guide that you believe corresponds to this?

Kavitha_Sundaram

Hi,

Thanks a lot for all your response on this query.

My findings..

1. Tried the steps suggested by Ghoti. I realised that version history in branch B is always referenced back to branch A.
2. So if i delete the edition in Branch A, i don't see the version info for that specific version in Branch B.

My requirement is to totally diassociate both the contents once i copy over the content to branch_b while still retaining the version history.

Can iwmigrate could be used to copy content from one branch to another branch within the same store??? I don't want to use an intermediate store.

Adam Stoller

Hi,

Thanks a lot for all your response on this query.

My findings..

1. Tried the steps suggested by Ghoti. I realised that version history in branch B is always referenced back to branch A.
2. So if i delete the edition in Branch A, i don't see the version info for that specific version in Branch B.

My requirement is to totally diassociate both the contents once i copy over the content to branch_b while still retaining the version history.

Can iwmigrate could be used to copy content from one branch to another branch within the same store??? I don't want to use an intermediate store.

If you want to do the iwmigrate route, you will need a temporary second store.

This should create a complete clone of branch_A with all versions of all files in it, so that you can then remove files from either branch and their histories will remain intact in the other branch.

pann0204

Are you sure about that?
If you delete the source branch - yes, you will delete all the old version history, but if you just delete the files in the source branch, their versions should remain intact.
Is there a specific section in the Admin Guide that you believe corresponds to this?

Pls refer page-74 from TS_admin guide 671 UNIX.

Regards,
Pawan

Adam Stoller

Pls refer page-74 from TS_admin guide 671 UNIX.

Right - and you said:

As per the suggestions in this thread mentioned, u can use iwcp/iwupdate or easily can use 'Copy to' from the edit menu, but none of these will preserve your older versions if you delete the source directory. There is a related topic in TS admin guide.

You were wrong in your statement. The page you reference indicates exactly what I said:

If you do not need any of your old version history, you can create a new (empty) branch, create a workarea, copy all the old content into the workarea, then delete the old branch. Exercise extreme caution when doing this, as all version and metadata information will be irrevocably lost.

Prior to about three posts-ago - the only thing that was being mentioned for deletion was files and folders. Once you throw editions and/or branches into the mix, the answer is definitely going to be different.

MultiCascade.zip

pann0204

Exactly Ghoti !!!, perhaps I have pre-assumed few things too early seeing this thread at prima-facie and I tried to clarify the feasibility like what is possible and what is not.

Cheers Smiley Happy

Pawan