I don't know anything about binlogs, but you could also migrate your jobs data by running a script that reserves jobs on the old server and creates corresponding jobs on the new server. I did that once at my work. That's only an option, of course, if you're not tracking jobs elsewhere, you don't have strict FIFO requirements (assuming the new server accepts new jobs during the migration process), and it's OK that the job ids will change.
On 20 September 2014 12:16, G.D. Arends <[email protected]> wrote: > Hi, > > I am in the process of moving beanstalkd to a new server. We use the "-b" > persistence setting. So I thought I would just copy over the binlog files. > But it seems like there is a lot of old left over junk in the files. Some > old tubes that are no longer used and empty, when I transfer the binlog > files, these tubes are once again there and have a few jobs in the tubes. > > Is this normal? > Is there a way to clean up the binlog files before moving the files to the > new server? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "beanstalk-talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/beanstalk-talk. > For more options, visit https://groups.google.com/d/optout. -- Nigel http://www.forgreatjustice.ca/ -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/d/optout.
