<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Hi Laura,</div><div dir="auto"><br></div><div dir="auto">Can Typhoon re-feed its news spool to another news server? If that's the case, you could just send them to your new instance of INN. Otherwise, as Geraint suggested, you can use pullnews as a reader to grap your articles. It works very well.</div><div dir="auto">https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html</div><div dir="auto"><br></div><div dir="auto">Another usual tool to do that is suck (a package outside INN).</div><div dir="auto"><br></div><div dir="auto">Note that you can run INN in slave mode (xrefslave set to true in inn.conf) so as to re-use the same article numbers as in your Typhoon news spool during the time of the transition.</div><div dir="auto"><br></div><div dir="auto">As you do not expire text articles, I believe CNFS buffers are most suited.</div><div dir="auto">tradspool and timehash store 1 article per file, which would exhaust your inodes.</div><div dir="auto">timecaf would probably work but is less used than cnfs.</div><div dir="auto">Do not forget to add new CNFS buffers when the ones you have are almost full, otherwise you would lost old articles (the buffer will wrap). Daily INN reports and also the cnfsstat command give you information about that.</div><div dir="auto"><br></div><div dir="auto">You can dedicate CNFS buffers to particular newsgroups (for instance binaries) so that they do not fill your other buffers too quickly. And expire them after 28 days, or let the CNFS buffers wrap at xx GB.</div><div dir="auto"><br></div><div dir="auto">Examples are here:</div><div dir="auto">https://www.eyrie.org/~eagle/software/inn/docs/</div><div dir="auto">expire.ctl</div><div dir="auto">cycbuff.conf</div><div dir="auto">storage.conf</div><div dir="auto"><br></div><div dir="auto">In case you have any other question, feel free to tell. Good migration to INN!</div><div dir="auto"><br></div><div dir="auto" id="composer_signature">-- <div dir="auto">Julien</div></div><div><br></div><div dir="auto" style="font-size:100%;color:#000000"></div><div style="font-size:100%;color:#000000" dir="auto"></div><div dir="auto" style="font-size:100%;color:#000000"></div><div style="font-size:100%;color:#000000" dir="auto" align="left"><div>-------- Message d'origine --------</div><div>De : Laura Steynes <laura.steynes72@gmail.com> </div><div>Date : 22/07/2021 08:20 (GMT+01:00) </div><div>À : inn-workers@lists.isc.org </div><div>Objet : Typhoon to Inn </div><div><br></div></div><div dir="ltr"><div>Hi folks,</div><div><br></div><div>We are using typhoon 2.6, its some 12 years old and amazingly, on the same hardware, with the exception of a few drives in raid changed out for failures over the years.</div><div><br></div><div>We have decided to format a plan of action and present it to our board for a replacement of all its aging hardware, so in preparation for rebuilding, moving data over, we have some questions.</div><div><br></div><div>We can some 92K newsgroups, dating back with articles from 90's, all up, about 4TB of groups, kept low because binaries groups are expired after 28 days, so my questions are</div><div><br></div><div>Does INN have a method or compatibility program to move this data into INN?</div><div>If not, does anyone have a suggestion of how, for instance INN in reader more to suck all a groups content - even if takes many days, we have no urgency to commission.<br></div><div><br></div><div>I note INN seems to have several storage types, given above - most are text based groups, with some brief binaries groups content, which would be the better storage format? Remembering we have an abundance of disk space, and we do not expire text groups articles.</div><div><br></div><div>Does anyone have a sensible working config file for such cases they care to share?</div><div><br></div><div>Thank you.</div><div>Loz<br></div></div>
</body></html>