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; } } }

Control Versioning

System

Hi,

Is there any way to clear the previous versions?.

We are using Interwoven Teamsite 6.5 for about 1 year, we have a lot of versions for each and every file submitted.Because of this our disk space grows very rapidly.

We want to clear some of the versions.Let say if there are 10 versions , we need to keep only last 5 versions.Is there any command or utility to do this.

Kindly expecting your reply

Thanks

Find more posts tagged with

Comments

Pawan

Hi,

If your main concern is the disk space, then you can better run the iwfsshrink CLT which will make your system run faster and save you preserve the versions.

Thanks,
Pawan

Adam Stoller

Hi,

Is there any way to clear the previous versions?.

We are using Interwoven Teamsite 6.5 for about 1 year, we have a lot of versions for each and every file submitted.Because of this our disk space grows very rapidly.

We want to clear some of the versions.Let say if there are 10 versions , we need to keep only last 5 versions.Is there any command or utility to do this.

Kindly expecting your reply

Thanks

This has been discussed before in the forums (did you try searching before posting your question?)

The iwfsshrink suggestion is always a good first pass - it removes duplicate data from the backing store which can occur over time (and especially occurs after an iwconvert / iwmigrate run)

Beyond that - you need to delete entire editions - you cannot delete specific versions of files, only editions. If a specific version of a file only exists within the edition you are deleting, then that version of the file will also get removed - but if it exists in any other edition, staging, or workarea on that branch it will not get removed.

msrinivas

Deleting editions doesnt help much wrt disk space. Editions contain only pointers to versions of files. iwfsshrink is the best option. Please remember that there might be performance issues when running iwfsshrink. So ideally you should run it as an off hour task.

HTH

Adam Stoller

Deleting editions doesnt help much wrt disk space. Editions contain only pointers to versions of files. iwfsshrink is the best option. Please remember that there might be performance issues when running iwfsshrink. So ideally you should run it as an off hour task.

HTH

Where do you get your information from?

While editions are comprised of pointers to versions of files and not the actual files themselves - it is only when all pointers to a specific version (and perhaps all earlier versions) of a file are removed that the version(s) will get removed from the backing store and thus reduce the size of the backing store. (see this thread for a testimonial, and this thread for additional information)

iwfsshrink is responsible for removing data-duplication - which was a significant problem in older versions (pre-5.5x) of TeamSite when changes to metadata on a file caused a complete copy of the asset to be created despite the asset not having been changed, and also occurs when TeamSite replays events during an iwconvert (from 5.x) or iwmigrate. There may still be cases where data duplication occurs with today's versions, but it tends to be relatively little and running iwfsshrink once a quarter is generally sufficient to keep it in check. It does not delete versions of assets.

This all being said - 1 year's worth of data should not be stressing your backing store partition unless you significantly undersized it

Migrateduser

Where do you get your information from?

While editions are comprised of pointers to versions of files and not the actual files themselves - it is only when all pointers to a specific version (and perhaps all earlier versions) of a file are removed that the version(s) will get removed from the backing store and thus reduce the size of the backing store. (see this thread for a testimonial, and this thread for additional information)

iwfsshrink is responsible for removing data-duplication - which was a significant problem in older versions (pre-5.5x) of TeamSite when changes to metadata on a file caused a complete copy of the asset to be created despite the asset not having been changed, and also occurs when TeamSite replays events during an iwconvert (from 5.x) or iwmigrate. There may still be cases where data duplication occurs with today's versions, but it tends to be relatively little and running iwfsshrink once a quarter is generally sufficient to keep it in check. It does not delete versions of assets.

This all being said - 1 year's worth of data should not be stressing your backing store partition unless you significantly undersized it

Hi Ghoti,
I have tried like iwfsshrink run c:\iw-store\default
it gives a error message "No archive found"

I used iwgetstore to get my store it retruns as c:\iw\iw-store

so i again tried like iwfsshrink run c:\iw\iw-store

it gives me the same error message "No archive found"

any idea about this ?Kindly advise

Adam Stoller

Hi Ghoti,
I have tried like iwfsshrink run c:\iw-store\default
it gives a error message "No archive found"

I used iwgetstore to get my store it retruns as c:\iw\iw-store

so i again tried like iwfsshrink run c:\iw\iw-store

it gives me the same error message "No archive found"

any idea about this ?Kindly advise

If you just want to run it on the default store - just do: iwfsshrink run and then periodically run iwfsshrink status until you see something that looks like:

Not currently running. 
Last started Mon Jun 26 15:47:53 2000 
Last completed Tue Jun 27 00:40:04 2000 
Files examined: 317974 
Bytes examined: 75936814830 
Files found to be duplicates: 233430 
Files converted: 198352 
Bytes removed: 23455046531

If you are using a secondary store - just use the store's name - not it's path at the end of both of the above commands.

This is reasonably well covered in the CLT manual (which is the source of the sample output shown above)

Migrateduser

If you just want to run it on the default store - just do: iwfsshrink run and then periodically run iwfsshrink status until you see something that looks like:
Not currently running. 
Last started Mon Jun 26 15:47:53 2000 
Last completed Tue Jun 27 00:40:04 2000 
Files examined: 317974 
Bytes examined: 75936814830 
Files found to be duplicates: 233430 
Files converted: 198352 
Bytes removed: 23455046531 
If you are using a secondary store - just use the store's name - not it's path at the end of both of the above commands.

This is reasonably well covered in the CLT manual (which is the source of the sample output shown above)

Thanks a lot for the Help