Dear CW, I'm happy to announce that, after considerable deliberation, the Royal Conservatory of Music Library in Toronto is implementing Koha ILS, with a projected go-live date of 1 September 2016. In partnership with our IT department, the library is beginning the first stages of the implementation. Our IT director had a question at a recent meeting regarding common server architecture set-up. We are a small library (+/-170000 lines of data across 6 SQL tables) with a user base of about 600. The library has about 70000 items. He was curious about how Koha libraries who are hosting their own instance have set-up their server in terms of LAMP distribution and redundancy. For example, have you installed everything on one hardened server with some sort of RAID configuration and backup system, or do you have an application server, SQL server, and assets server, each with their own hardening, redundancy, and backup regiment? For vendors on the list who host Koha for client libraries, what is your common architecture set-up at your company? Any information or documentation referrals would be helpful, and off-list replies are welcome, too. Thanks all. Very much looking forward to the RCM being part of the Koha community. C Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER the royal conservatory TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca<http://www.rcmusic.ca/> Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.