On Wed, Aug 17, 2011 at 8:01 AM, Jeff Blaine <[email protected]> wrote: > Replying to my thread starter from a few months ago. > > On 6/23/2011 11:32 AM, Jeff Blaine wrote: >> >> If anyone has any clever advice as to how to about this, >> I'd love to hear it. >> >> RT 3.8.7 + security patches, PostgreSQL 8.1.23, RHEL5 >> >> We need to replicate our production RT instance's data >> to a development instance (yes, backward), but we don't >> want to carry the ~6GB of *ticket and attachment* >> data (what else?) over to development. >> >> Essentially, we want the same environment in development >> as production, but with empty queues. > > Warning: Do not try this. It seemed to work fine, then > weird things started popping up. Instead, dump everything > from production, restore everything on the dev server, > then shred the tickets on the dev server.
I had a use case similar to this (backporting production DB to a dev environment, wanting to drop all tickets and related data but preserve everything else). In my case I had tried to shred the tickets but ran into an error to the effect of too many tickets specified by the shredder resulting in too long of a GET request URI length for the server. I concluded that shredding that many tickets from the UI wasn't going to work and there must be a better way. Is this right, or is there some way of massaging a deployment to delete a largish number of tickets? (In our case it was something like ~3500 tickets in the four RTIR queues). Happy to post back with details if needed. -- Darren Spruell [email protected] -------- RT Training Sessions (http://bestpractical.com/services/training.html) * Chicago, IL, USA September 26 & 27, 2011 * San Francisco, CA, USA October 18 & 19, 2011 * Washington DC, USA October 31 & November 1, 2011 * Melbourne VIC, Australia November 28 & 29, 2011 * Barcelona, Spain November 28 & 29, 2011
