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

POC on deleting older versions

kukunoor1

Hi Team,

how can we do a POC on deleting older versions of the file by keeping only 5 latest versions of the file. and my TS is 6.7.2 and SP 2

i am able to list out version and im not able to find the solution for how to delete the five and more than versions.

Any pointers or suggestions

really appriciate your time

Thanks.

Find more posts tagged with

Comments

nipper

You need a script/program to query the number of versions of all assets and then start deleting them

There are CLTs to help, like iwrlog

Adam Stoller

You need a script/program to query the number of versions of all assets and then start deleting them

There are CLTs to help, like iwrlog

To be a bit more detailed - you use the information in iwrlog to identify the name of the edition associated with the specific version of the file - and then you delete that edition - however, deleting that edition then deletes all the version references for all the files in that edition (not just a single file) - and this will only delete the actual version of a given file if it is the very last edition that contains a reference to that version of the file.

The POC for deleting editions is pretty trivial.
The POC for maintaining a specified number of versions of all files is a bit more complex.
The arbitrary specification of 5 versions is, IMO, silly (at best).

kukunoor1

To be a bit more detailed - you use the information in iwrlog to identify the name of the edition associated with the specific version of the file - and then you delete that edition - however, deleting that edition then deletes all the version references for all the files in that edition (not just a single file) - and this will only delete the actual version of a given file if it is the very last edition that contains a reference to that version of the file.

The POC for deleting editions is pretty trivial.
The POC for maintaining a specified number of versions of all files is a bit more complex.
The arbitrary specification of 5 versions is, IMO, silly (at best).

Many Thanks all for your information.

Using iwrlog i can get the version numbers that i am getting currently from iwattrib.

But i am not getting any clue on how to delete required versions???

Regards,
Priyanka

Adam Stoller

Many Thanks all for your information.

Using iwrlog i can get the version numbers that i am getting currently from iwattrib.

But i am not getting any clue on how to delete required versions???

Regards,
Priyanka

Here's the deal - try to pay attention ...

Understand?If you do decide to run the test described above - please post the results.

nipper

That was my bad, I thought there was a way to remove a version. I was thinking of ClearCase......

desmart

Hi All,

Is there a way to identify the older edition which is huge in size.I understand the more number of submits , the more huge is an edition.

we are planning to remove older editions and there are thousands of editions on various branches.So how can I identify the edition which upon deletion will save some significant amount of space on the store.
Version:Teamsite 7.2.1

Thanks!!

Rick Poulin

I understand the more number of submits , the more huge is an edition.

Not quite. A new hidden edition is created each and every time a submit is performed (the UI abstracts this a little bit by combining a bunch of editions under a single given name). Thus, an edition is "larger" if the submit event that created it had a lot of changes. An edition is no more than a 'diff' between two submit events, and all files that haven't changed will simply be recorded as pointers to a past edition where the HAD changed. Whenever you delete an edition, the content store essentially merges the diff from the deleted edition with the one that came before it.

In terms of effectively shrinking your content store, it's typically a bad idea to pick and choose certain editions for deletion. Your space savings will not really be obvious or calculable ahead of time. Instead, decide *how far back* you want to keep your history, and then start deleting editions starting with the oldest one, going forward until you hit that target date or the store is small enough to suit your purposes.

Adam Stoller

Hi All,

Is there a way to identify the older edition which is huge in size.I understand the more number of submits , the more huge is an edition.

we are planning to remove older editions and there are thousands of editions on various branches.So how can I identify the edition which upon deletion will save some significant amount of space on the store.
Version:Teamsite 7.2.1

Thanks!!

I think you're barking up the wrong tree, or at least the wrong limb of the tree.

You would have to identify what edition contains the most unique versions of files - i.e. versions of files that do not exist in any other edition, staging, or workarea - if you delete that edition, then those versions of those files become subject for garbage collection.

More correctly, you need to decide how many old editions you want to preserve and then delete all previous editions - this will then make it likely that you will be "deleting" old versions of certain files, over time.

desmart

Thanks for your reply Rick & fish!!

I wanted to copy my prod default store to dev and have a test on the deletion of edition to see if there will be some significant space save.

We have to replace it on top of the dev default as there is no enough space to mount another store.

Is there something that I need to take care off as I am directly pasting it on top of dev default store.

Adam Stoller

I hate to make too many assumptions, but it sounds like you don't really know what you're doing and thus my advice would be to bring in someone who does, or open a Support Case and work closely with them to go through all the steps.

That being said, you are also being naive if you think deletion of a single edition will save you any significant amount of disk space. If you are really running into disk space problems perhaps the issue is that the server wasn't configured with sufficient disk space to begin with - and the best way to fix that is to get more disk space.

desmart

fish,

I didnot say that I am expecting a significant space diff with deletion of single edition.

its just that we are not supposed to do it directly on Prod.

Thanks!!