SEP sesam Configuration – First Steps
Copyright © SEP AG 1999-2019. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.
Below is a brief description of a typical SEP sesam configuration. For detailed information on SEP sesam functionality and configuration, follow the text links under each step, search for relevant articles, and check FAQs.
Step 1 – Location
You must first determine which operating systems SEP sesam will back up. To do this, you will require the names and configuration of all target computers. Because each client must be assigned to a distinct location, you can choose arbitrary location names and descriptions. By default, the location LOCAL is created on the server. For details, see Configuring Location.
- Select Components -> Topology to display the Topology content pane.
- In the Topology window, click New Location.
- Enter the name HOME and click OK.
Your GUI window should now look like this:
Step 2 – Clients
Add clients to your newly created location. For details, see Configuring Clients.
- Go to Components -> Topology -> HOME -> right click and select New Client. Depending on the client's operating system, select one of the following platforms: Windows, UNIX, NDMP, VMS or NETWARE. The client name must be identical to the computer's network host name and must be resolvable either by DNS or hosts-file. For details, see How to check DNS configuration.
- Enter the client's platform-specific operating system in the corresponding box. Click OK to confirm the client.
- In the Task for new client dialog, select the No option.
In the example below, a Windows (qsbox1) and a Linux (talentix) client were added to the HOME location. After configuring each of the clients, the No option was selected in the Task for new client dialog.
For client connection issues, see How to verify that the SEP sesam server has full access to a specific client.
Step 3 – Backup Hardware: Where should the data be stored?
During the installation process, SEP sesam checks the SCSI-bus for connected backup hardware and enters its data in the SEP sesam database.
To view available data stores, select Components -> Data Stores. By default, a data store (Test-Store) is created on the SEP sesam partition. The Test-Store is used as a sample back up in the examples below. For details, see Data Store.
Step 4 – Tasks: What should be backed up?
To create a task, go to Tasks -> By Client in the Main Selection pane to display the Tasks by Clients in the content pane. Select a location (the location in our example is HOME) and select the client you want to back up.
From the task bar, select New backup task and provide a description for the backup task. The task name can be selected arbitrarily (max. 32 characters), however, it is recommended that you use a descriptive name. The Source input box lists the drives, folders and files that will be backed up. For more information, see Creating a Backup Task.
In the example below, we created a total of 13 backup tasks:
- One backup task for SEP sesam (SESAM_BACKUP, created automatically)
- One backup task for testing purposes (TEST_BACKUP, created automatically)
- One system recovery backup task for each Windows system (qsbox1_system_recovery, informatix_system_recovery)
- One backup task per client for all data (qsbox1_data_all, talentix_data_all, informatix_data_all)
Make sure that the option VSS is enabled for each Windows client.
- One backup task for each database (qsbox1_mssql_all, talentix_ORACLE, talentix_postgres_all)
- One backup task for each virtual machine (qsbox1_SEP_Cloud_notus, qsbox1_SEP_Cloud_VMware_vCenter, qsbox1_SEP_Cloud_Windows7)
To group the backup tasks, go to the Tasks -> By Groups, select New Task Group in the content pane and provide a name. In the New task group window, select the backup tasks you want to assign to the task group. Move the tasks from the left side to the right side by selecting the task and pressing the right arrow. In our example, we created a group for each task type, giving a total of 5 backup task groups. For details, see Adding a Task to the Task Group.
Step 5 – Schedules: When should the data be backed up?
Go to Scheduling -> Schedules for an overview of the configured schedules. All SEP sesam schedules can be controlled from here. We recommend the following schedules:
- One schedule (Diff, Mo.-Fr.) for all data (regardless of the operating system), starting at 8:00 pm
- One schedule (Full, weekly) for all data (regardless of the operating system), starting at 10:00 am
- One schedule (Full, daily) for the system, starting at 9:00 pm
- One schedule (Full, daily) for the SEP sesam self backup, starting at 07:00 am
- One schedule (Full, daily) for all databases, starting at 10:00 pm
- One schedule (Full, daily) for all virtual machines, starting at 11:00 pm
From the Schedules content pane, Select New -> New Schedule, and enter a descriptive name for the schedule, for example, Data-Diff-Mo-Fr-2000. If it is a differential backup, set the schedule for each working day at 8:00 pm.
Select the tag weekly and check Monday through Friday. Finally, enter the start time (in the example, at 20.00 hrs) and click OK.
For a one-time execution of the schedule, right-click on the schedule and select Immediate Start. In the dialog that appears, select default priority and click OK to start the backup. For details, see Creating a Schedule.
Step 6 – Backup event: How should the backup start?
Use the schedules created above to configure a cyclic backup. Create a new backup event for each schedule and insert it into the SEP sesam calendar, which will then be executed by the SEPuler at the appointed time. For details on how to create a backup event, see Creating a Backup Event.
To generate a backup event, right-click on a schedule and select New Backup Event in the taskbar. In our example, for the Data-Diff-Mo-Fr-2000 schedule, select DIFF as the backup level, TEST_POOL as the media pool and Data as the task group, which was created earlier. Repeat the procedure with the relevant settings for all the schedules. The figure below shows a thoroughly configured system.
The system is now completely configured and will execute the new backup jobs at the appointed time. After the backup event has been executed, the backup jobs can be checked in the Scheduling -> Calendar Sheet or Job State -> Backups menus.