<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On 6-Aug-06, at 3:52 PM, Brad Templeton wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">It's pretty simple.<SPAN class="Apple-converted-space"> </SPAN></FONT></P> </BLOCKQUOTE></DIV><BR><DIV>It isn't. He's crossing versions and there are schema changes. One I remember for sure is .18 generates the recording's filename from the channel + start/end times while .19 has a column for filename. Changing the recording host won't do it.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I suggest upgrading the .18 database to .19 and using nuvexport to create sql exports of all the recordings which can then be imported to the target system. The sequence of events would be:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>1 - shutdown the .19 system</DIV><DIV>2 - move its db to a safe place</DIV><DIV>3 - copy in the .18 db</DIV><DIV>4 - bring up the .19 backend which will upgrade the .18 db to .19</DIV><DIV>5 - nuvexport all the recordings</DIV><DIV>6 - shutdown the backend and restore the original .19 db</DIV><DIV>7 - import the exported recordings (mysql < *.sql where the nuvexports are)</DIV><DIV>8 - enjoy a much larger recording library</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I'm not sure if the .18 recording files have to be in the recordings directory when you do the nuvexport. Of course, they have to be there after you do the import. If I've glossed over any details just ask.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>- George</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>