It's all about the answers!

Ask a question

Archiving Jazz Product's DB partiallly

Canberk Akduygu (99237371) | asked Aug 16 '12, 6:16 a.m.
edited Aug 16 '12, 11:10 a.m. by Jared Burns (4.5k29)


I have a customer who uses RTC and RRC and DB's are getting bigger and bigger. In one and half year RTC DB has reached to 108GB. It's a huge number according to my previous experience and the main reason of this growth is that we always check-in the packages(war,ear,jar files) created by a build to the component. And we are going to keep using like that and DB's will keep growing.

I dont think there's a way to archive some data by giving a timestamp right now. Maybe after two year(2014), we wont need the data of today(2012) Will there ever be such functionalities? I was wondering if it is feasible to expect such a methodology?

Accepted answer

permanent link
Stephane Leroy (1.4k149) | answered Aug 22 '12, 9:35 a.m.
Hi Canberk,
wrt. to to the possible strategies for binaries handling, you might want to have a read at these 2 articles
Ralph, again, is the author of this useful material.
Canberk Akduygu selected this answer as the correct answer

Canberk Akduygu commented Aug 22 '12, 10:41 a.m.

It's an acceptable solution that's I used for another customer. But as far as I understand,right now we don't have any chances to delete that published and checked-in files. May be when we migrate to RTC 4.x, we might consider deleting those binaries manually.

2 other answers

permanent link
Stephane Leroy (1.4k149) | answered Aug 16 '12, 11:27 a.m.
Hi Canberk,

maybe part of the solution would be to change the strategy binaries are stored (and possibly stop uploading all build results systematically). My colleague Ralph has provided an answer you might be interested in here :

If this is not an option, you might be interested by the new feature in 4.0 for deleting file content from the repository (requires administrator credentials)

St├ęphane Leroy
Jazz Jumpstart

permanent link
Canberk Akduygu (99237371) | answered Aug 22 '12, 4:49 a.m.
I also believe that they should stop checking-in all the binaries to the repository but the ant script are build to support automatic attachment of the binaries. May be we should create different build definition for continuous builds and other definition for releases.

And creating a release also could be option, we might create release packages by using that option and delete the other build results. I see that deleting build results delete the content from the repository. I believe it will also delete the binaries attached to that build result, am I right?

Your answer

Register or to post your answer.