SEP sesam | Univention Corporate Server (UCS) Backup (Lang_DE)
Articles,  Blog

SEP sesam | Univention Corporate Server (UCS) Backup (Lang_DE)

Hello and welcome to this
Introduction video. I’ll show you how to protect a UCS Univention environment with SEP sesam. Here we are on the UCS Web
Frontend. I have already installed the SEP sesam backup server using the App Center. It is is already running.
The UCS environment consists of serveral components.
In my case Kopano. Additionally I have VMs running on KVM, PostgreSQL databases,
and MySQL databases, OpenLDAP and I am hosting ownCloud.
Last but not least I have numerous files, that I share via Samba. We want to protect all of these applications with SEP sesam and
I will show you how to set up all the backup tasks. Therefore we switch to the SEP sesam GUI. There’s nothing really set up yet. I’ve only created groups under the menu item tasks. It always makes sense to work with groups –
this makes it easier to start the backups. I have four groups here:
Applications, Bare Metal, Files, VMs. DI’ll show you what I put into this applications group. Everything else is self-explanatory. I have a Data Store (Backup to Disk). Then we go to tasks by clients.
Here we first create the tasks of the applications. To do this I select “New backup task” and I click directly on this browse button
and then we see that we get all the applications displayed. I just start from the top with MySQL and
I always check the box at the top. If you mark the checkbox
at the top, the source “all” is used. That means, if another new
database is added this new database is automatically
included in this task and is automatically backed up.
I am assigning this new task to this task group. So all databases are assigned to the applications group. Continuing with
PostgreSQL databases: here I do exactly the same. Then Kopano: here again I
start from the top. For a Single-Item-Restore
or Single-Mail-Restore I also assign it to the Application-Group. I don’t really
like the task name yet – let’s name it Kopano. Then, of course, I want to include
the files from ownCloud in the Application Group as well. You can find them here: just enter ownCloud. The corresponding ownCloud
database can be found here under MySQL and is already included
here with the MySQL task. I’ll just check in and see
if that’s really the case. Exactly: there’s the ownCloud database. And then we’ll see if we forgot anything else.
Yes, something is missing: OpenLDAP. OpenLDAP – we create the task
by using a little trick. We fill in “all” under Source. We call the task OpenLDAP and save it. There it is.
Now we switch the task types from path backup to OpenLDAP. Of course, we still have to assign OpenLDAP
to the application group as well. Now we have assigned all applications
from the UCS environment to the application group. We can see that here,
too: Tasks by Groups. Here they are. Next, we create the
job for the VMs. A separate task for every VM. We again assign the whole task
to the VM group and also call it VM – that’s nicer. We do the same with the 2nd VM and also assign it to the VMs group. Then
we’ll continue right away and create a Linux BSR for the Bare Metal Recovery called “BSR”. We also have a task group for this.
Finally we have to setup the normal path file backup. For this
we simply go to “All Local File Systems” at the top, so that we have the
source “all” again and assign it to the Files Group. Now we have
really created all tasks for the UCS environment. We have already assigned
all of them to the corresponding groups – as you can see. The groups are assigned to a schedule – in the Schedule.
I’ve done that before, as you can see here. Here is the checkmark.
The application schedule is backed up to the data store with backup level “full”
on Saturday at 10 a.m. – and this also applies to the other groups.
This is also a schedule and the nice thing now is that
I have four different groups and I have the possibility to start
the backups of the groups at different times. As you can see here, you can also filter.
Here we also have the schedules with all the tasks. Now the whole UCS system is protected.
Finally, it makes sense to simply start an instant
backup in order to test whether the backups are working properly.
We are already at the end of our presentation. Thank you very much for watching!
Hope to see you next time.

Leave a Reply

Your email address will not be published. Required fields are marked *