wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114wp-extended-search domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Last week, we announced that 9 German education and research organizations moved from ownCloud to Nextcloud together with the TU Berlin. Today we’ve published a case study on our website which details the migration of the TU Berlin and the results achieved, including 50% lower base and 38% lower peak database loads. The end result was faster service to users at lower cost.
The Tu Berlin was one of the first universities to provide its own file sync and share solution, already evaluating ownCloud back in 2011. They provided cloud storage within the DFN cloud research program, servicing 16 member research and higher education institutions today. Their service has over 22.000 active users at the TU Berlin, with more at the other organizations and storage for the TU Berlin itself is well over 70 TB, with students allowed a maximum of 20 GB data and staff members up to 100 GB.
The TU Berlin uses load balancers spreading user requests between 4 application servers which run a NGINX/MySQL/PHP 5.6 stack on CentOS 7.3. Data can be found on a GPFS-based storage and a Galera MySQL cluster while LDAP and Kerberos handle authentication and all of it runs in LXD containers managed with OpenStack.
After Nextcloud won a tender for providing a new file sync and share solution, TU Berlin decided to migrate to Nextcloud 11 which promised significant scalability, security and feature improvements. The team is also interested in exploring Nextcloud Global Scale in the future, for scaling up their DFN cloud service and decreasing the total cost of ownership.
The migration was planned during the course of three weeks and executed in one week, fitting the update window set between the result of the tender and end of the old contract. A test environment built from a copy of production was used to prepare. As part of the migration to Nextcloud 11, the TU Berlin decided to move to NGINX from Apache, which was made possible thanks to the native SAML support in Nextcloud.
The migration process itself was ready in time and worked exactly as planned. The TU Berlin did not need any stand-by support from Nextcloud.
Overall, the migration was like a typical upgrade.
Before Nextcloud 11 was deployed, the TU Berlin faced scaling issues with heavy peak load on the database cluster during working hours. The migration resulted in peak load decreasing by over 38% while off-peak times even show a 49% lower stress on the servers. Thanks to this improvement users experience a snappier experience and faster syncing while the TU Berlin can now grow further without significant investment.
Server load before and after migration from ownCloud to Nextcloud
You can find more details in the case study on our website and Dr.-Ing. Thomas Hildmann from the TU Berlin will talk about the migration and its results at the Focus Friday on the Nextcloud Conference later in August.
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
Per saperne di più
The Nextcloud Conference is not your average event - it's a community meetup that brings together Nextcloud enthusiasts, contributors, developers, users and industry experts from all over the world.
Per saperne di più
Per aiutare le organizzazioni governative e aziendali a migrare da Microsoft 365, il team di Nextcloud Office sta cercando partecipanti per studi UX. In particolare, gli utenti abituali di Microsoft Office sono incoraggiati a partecipare e a fornire il loro contributo, in modo che il team possa identificare e risolvere i principali ostacoli alla migrazione. […]
Per saperne di più
Over the last years Nextcloud Talk has developed in a fantastic productivity tool, enabling teams across the globe to communicate and collaborate in chat rooms, video meetings and webinars.
Per saperne di più
