Here's an idea (I have not tested this!): If you have an EE, there is backup module coming with it. You can try to make a backup and then restore the content in new installation. This way all your live nodes are kept as well as their versions. The backup is traversing whole repository, retrieving all the nodes and all of their version history. When there is no node pointing to the version history, it should not be backed up and therefore it should not be restored either. This way you should be able to get rid of the orphaned versions. The fact that it is traversing whole tree for each workspace and validating nodes instead of blindly copying DB tables is what makes backup module slower then backup directly at DB layer, but it has this kind of advantages (another one is that it can aid migration from one DB to another). As I said at the beginning, I have not tried to perform backup/restore with the goal of removing stale versions specifically, but from insight I have into this operation I think the stale versions should be dropped during the process. Easy test is to run backup on your instance and then restore it in clean DB and compare sizes of the DB before and after. Since part of the backup is DB connection info, make sure you update this before restoring to new instance in case your connection string is not transient (like localhost or 127.0.0.1). The info is stored in repoConfig.gz/zip file.
HTH, Jan On Thu, 2009-04-23 at 07:10 -0700, George.Francis wrote: > > There is an OS Eclipse plugin called JCR Browser, but it didn't work very > well for me so I just wrote a basic swing GUI to build a JTree representing > the JCR heirarcy - it doesnt take long. > Cheers, > > > rainer wrote: > > > > As far as i know you cannot simply delete them.. but i'd be glad if so. > > corrects me ;) > > > > Can you plz tell me: What tool do you use to watch/edit those > > repositories? > > > > thx > > rainer > > > > > > > > > > > > George.Francis wrote: > >> > >> Our JCR repo is bloated to a size of 3GB. Looking into it, I found that > >> there seem to be thousands of entries in /jcr:system/jcr:versionStorage > >> that are orphaned, ie: they refer to items that were removed from the > >> repository. I was told that these history items couldnt be deleted from > >> the repo (when I try I get a JCR exception). How can these orphaned > >> history nodes be removed? > >> Regards, > >> George > >> > > > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
