Delete EDITIONS

I've got 800 EDITIONS in a branch and need to start periodically deleting EDITIONS.

The EDITIONS now contain 600,000 assets and 20,000 dcr's so I'm slightly nervous - I've already damaged the backing store on my staging TS server testing 'EDITION deletion' with only 10% of the content I have in production.

There does not appear to be much on the subject in Interwoven docs or the support web site.

I need to delete the older 33% of my EDITION list (the bottom 300 EDITIONS) and require some advice regarding best practices.
e.g.
Should I delete older EDITIONS first or the more recent?
Can I delete more than one EDITION at a time?
Assuming I can only delete one EDITION at a time how long should I wait before deleting the next?
Are there any indicator (processes) I should be looking for to indicate the EDITION is deleted? [Ideally I'd like to script and cron it...]

Any other advice ???

Many Thanks,
Steve.

Find more posts tagged with

Comments

Migrateduser

You have to be really careful when deleting many editions at once. We tried blasting away dozens of editions at one time once, and just about destroyed the TS server. When you delete editions, it creates these batch jobs that run in the background (run iwstat to see what's going on with batch jobs) and if you have too many edition deletions going on at the same time, these batch jobs just multiply like rabbits and it brings your TS Server to its knees. We've needed to get rid of editions for space reasons, so I set up cron jobs to run on off hours, deleting editions one at a time through the night. It takes a lot of time, but the alternative is not good. Be careful and good luck.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

fish

Thanks v much.
The support guys are also telling me to start with the oldest EDITION first (obviously not INITIAL!).
Well I'll cross my fingers and delete my oldest EDITION...

Migrateduser

Another thing you can do is monitor the first couple of edition deletions to see how long each one takes, and use that time as a guide for how to space out your deletions if you decide to create your own batch process to delete the editions automatically. I also set up an edition maintenance script that will delete the oldest edition whenever someone creates a new edition - that at least keeps your edition count static. You can do this using the command trigger that kicks off whenever a publish event occurs. You can customize this script to only delete an edition in the branch (or branches) you need to do this for. If you want more details on that, email me.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

I am sorry I am just seeing this now. I would actually advise against deleting editions like this prior to TS 5.5.x. The reasons for this are detailed in the following kb article:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=2204

Migrateduser

We are well aware of that article, however we have run into a severe space issue on our TS server and have no choice but to delete editions periodically to reduce the used space on our server. We essentially have no choice but to streamline how many editions exist. And contrary to what the article says, we can reclaim a significant amount of space by deleting certain editions.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

mikelowndes

On solaris TS (421) also eats RAM when doing this and then does not let it all go... Caused us horrid problems when we did this: we also ran out of disk! We were deleting editions to create space, but the process actually increased disk usage. A bigger disk and a VAST number of inodes helped, but we still had to restart TS periodically during our edition clearout. Now, we just do it little but often...
Mike, NHM

http://www.jisc.ac.uk/techwatch/reports/