Bacula Enterprise Edition new in Univention App Center

Integrate the network enterprise backup solution Bacula Enterprise Edition in heterogeneous IT environments with just a few clicks

With the launch of Bacula Enterprise Edition there is now a further professional enterprise solution for the backup and restoration of data in heterogeneous environments available in the Univention App Center. Users of the enterprise IT management solution Univention Corporate Server (UCS) can test the software with unlimited functions for 30 days and 5 jobs.

Technical overview of the first UCS 4.0 preview

Univention Corporate Server Source codeThe first preview of our upcoming UCS 4.0 release is available. On this occasion I would like to give you an overview of the major technical changes in this preview release.

16.500 new source packages

With UCS 4.0 the underlying Debian distribution is updated to Debian 7 Wheezy. That means all of the 16.500 source packages have been updated and adapted to UCS needs. A major part of the UCS packages is written in Python. We switched from Python 2.6 to Python 2.7 for these packages. To allow an easy migration from UCS 3 to UCS 4, we decided to build the modules still for both Python versions.

One major new feature in Debian 7 is multiarch. Multiarch lets you install packages from multiple architectures on the same machine. This is useful in various ways. The most common is installing both 64 and 32-bit software on the same machine and having dependencies correctly resolved automatically. The Debian wiki has an extensive manual on how to make use of this functionality if you need it.

UCS installation

The UCS 4 installer is based on the Debian Installer and replaced the previous own implementation. The installer asks only for the important basic settings such as language, network and partitioning. Thereby a graphical RAID configuration is possible during the installation. The UCS-specific installation steps are done in a web-based setup assistant. Thus, a UCS system can be configured either by a locally installed web browser or via remote which makes cloud setups really easy. The setup assistant is already used in the UCS 3 appliance.

Hardware support

We decided to update the Linux kernel to 3.16. This will also be the default kernel for the next upcoming Debian stable release aka Jessie. The kernel development has an amazing speed and we are very happy that we rarely find unsupported server hardware.

Active Directory

One major part of UCS is the possibility to act as Active Directory domain controller which, for example allows the Microsoft Windows client management via group policies. This function is based on Samba. The Samba team is currently working on Samba 4.2. We integrated a previous snapshot of Samba 4.2. That allows our partners and customers to get a feeling for this new version.

OpenLDAP performance

At the beginning OpenLDAP is a main component of UCS. Currently, we are using Oracle BerkleyDB (BDB) as database backend. We’ve made a lot of performance and comparative tests with different OpenLDAP backends. The results for the memory-mappend database (MDB) were incredible. So, we decided to switch the database backend to the mdb backend.

We are very grateful for any kind of feedback, either here or in our forum.

Univention releases UCS 3.2-3 with a whole host of innovations

Improved integration in Active Directory domains

Bremen, 13th August 2014. Univention GmbH, a leading European provider of Open Source products for the cost-effective operation and efficient administration of IT infrastructures, has released a new update for Univention Corporate Server (UCS). In version 3.2-3 the new module “Active Directory Connection” replaces the previous AD connector for mounting a UCS installation in an AD domain.

What app developers tell us: “Show me how to start!”

Univention App-CenterSince May 2014, four new apps (Kaspersky Mail Server Security, Mandriva Pulse, Dokuwiki and WordPress) have been released and 12 apps have received updates from their vendors. I’m delighted about those numbers. But it definitely was some work on either side: phone calls, e-mails, technical discussions in the Univention forum and feedback during the approval process.

Something had to be done to optimize the whole process and reduce the communication efforts. But what measures would be suitable and would they really help? For this reason, I contacted some of the app developers directly, some with App Center experience and those who have just made their first app available. Where did they have difficulties during the whole app creation process and what would help them? At this point, I’d like to thank the app developers for their open feedback.