Sesam Quick Install Guide V4.0/4.2.1

From SEPsesam
Jump to: navigation, search
Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.

Sesam Quick Install Guide V4.0/4.2.1 download PDF

Copyright © SEP AG 1999-2017. 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.

Installation of SEP sesam V4.0/4.2.1 on Windows

Prerequisites

Before starting the SEP sesam installation please make sure that you are logged in as local administrator or domain administrator. In case of remote access via remote desktop connection (RDC) the RDC administrator needs equivalent access rights as the local administrator. In order to install one or several SEP sesam components (SEP sesam server, Remote Device Server, Client, or GUI) an installation file is required which can be downloaded at http://download.sep.de/windows/. Please make sure to download a suitable file for your processor type.

If you are planning to install a server (including a GUI) or a GUI, Java Runtime Environment (JRE) 1.6 or higher has to be installed. For server installation .Net Framework 3.0, 3.5, or 4.0 is mandatory, for all other SEP sesam components it can be deselected during installation.

x86 operating systems having more then 3.25 GB RAM, have to either be reduced to 3.25 GB RAM or migrated to x64 operating system. This is necessary because SEP sesam requires 64 KB blocks for LTO (Linear Tape Open), but those systems can only write 32 KB blocks on tape drive due to the automatically activated PAE (Physical Address Extension). Also a loader cannot be accessed properly SEP sesam.

There are three different installation packages available providing either all or only single SEP sesam components. In the following we will explain the installation using solely the server installation package, which contains all SEP sesam components.

Installation

In order to install a SEP sesam component please choose the winXX directory on the CD/DVD, or choose the download folder where you saved the SEP sesam installation package. Start the installation by double-clicking on the sesam-srv-<VersionsID>-windows.x<SysTyp>.exe file. Please note that on Windows 7 even if you are logged in a administrator you still have to explicitly execute the exe file as administrator. After choosing your installation language, choose Next. Agree the license agreement and choose Next again.

InstallChangeInstallationFolder en.png

As depicted in the adjacent figure choose the installation directory for the program files (includes folders <SESAM_ROOT>\bin and <SESAM_ROOT>\skel) and the application data (includes folder <SESAM_ROOT>\var, in case of a server installation this folder might require a lot of storage) and click Next.

Now you have to decide which of the four SEP sesam components (SEP sesam server, RDS, Client, or GUI) you want to install. For an RDS installation you have the possibility to optionally include a GUI and for a GUI installation you have the possibility to optionally include a Client by checking the check box. The adjacent figure shows the four features that can be selected.

InstallSesamFeatures en.png

After choosing a suitable SEP sesam component choose Next.

SEP sesam Server

In case of a SEP sesam server installation you only have to click on Install to install the server on your operating system. Finally, click on Finish to complete the installation.

InstallServerName en.png

SEP sesam RDS, GUI, Client

For all remaining SEP sesam component you have to insert the host name of the SEP sesam server in the next dialog. Thereby the host name may not contain underscores.

Please note, that you have to enter the hostname and NOT the IP address of the SEP sesam server. In the given example we used the server name informatix. After enter SEP sesam server name please press Next.

The firewall information dialog is only intended for information purposes. Take notice of the information and click OK. Now you only have to click on Install and the chosen SEP sesam component will be installed.

Finally, click on Finish to complete the installation.

Installation of SEP sesam V4.0/4.2.1 on Linux

Prerequisites

You have to be logged in as user root (not user with root rights!). In order to install one or several SEP sesam components an installation file is required which can be downloaded at http://download.sep.de/. Please make sure to download a suitable file for your processor type. If you are planning to install a server (including a GUI) or a GUI, Java Runtime Environment (JRE) 1.6 or higher has to be installed. 64 bit operating systems need a PostgreSQL database to be installed.

For most common Linux distributions (e.g. SuSE and RedHat) SEP provides RPM packages. For Debian Linux distributions SEP provides DEB files. They will run on most Debian based distribution, like Ubuntu.

Server installation package

In order to install a SEP sesam server please choose the linux directory on the CD/DVD, or choose the download folder where you saved the SEP sesam server installation package.

To install RPM files the following command should be used:

rpm -Uvh sesam_srv<Version.OS.SystemTyp>.rpm

To install *.deb fils the following command should be used:

dpkg -i sesam-srv<Version.SystemTyp>.deb

Because the SEP sesam server includes a GUI, a GUI is automatically installed on your system. If the display variable is set GUI starts right after installation is complete. To manually start the GUI please use the following command:

/opt/sesam/bin/gui/sesam_gui

Client installation package

In order to install a SEP sesam client please choose the linux directory on the CD/DVD, or choose the download folder where you saved the SEP sesam client installation package. To install RPM files the following command should be used:

rpm -Uvh sesam_cli<Version.OS.SystemTyp>.rpm

To install *.deb fils the following command should be used:

dpkg -i sesam-cli<Version.SystemTyp>.deb

Since the SEP sesam server needs access rights to the client to be able to contact and backup the client, you need to execute the following command on the client

/opt/sesam/bin/sesam/sm_setup set_client <SEP sesam Server Name>

GUI installation package

You can either install solely the GUI package or in addition to a client. Since an SEP sesam server installation package includes a GUI it will automatically be installed on a server. In order to install a SEP sesam GUI please choose the linux directory on the CD/DVD, or choose the download folder where you saved the SEP sesam GUI installation package. To install RPM files the following command should be used:

rpm -Uvh sesam_gui<Version.OS.SystemTyp>.rpm

To install *.deb fils the following command should be used:

dpkg -i sesam-gui<Version.SystemTyp>.deb

For KDE and Gnome the installation routine generates a link on the root user Desktop to start the GUI. This link has to be adjusted to the correct SEP sesam server. Please open the properties of the link and add the following parameter to the command line -S <SEP sesam Server Name>

Installation of SEP sesam V4.2.1 on MacOS

Description

With the client for MacOS X 10.8 standard Filebackups with ACL's are supported. Disaster Recovery is not supported!

Prerequisites

Before starting the SEP sesam installation please make sure that you are logged in as local administrator or domain administrator. In order to install a SEP sesam component an installation file is required which can be downloaded at http://download.sep.de/. If you are planning to install a GUI, Java Runtime Environment (JRE) 1.6 or higher has to be installed.

There are two different installation packages available for MacOS providing SEP sesam components. The SEP sesam client installation package and the SEP sesam GUI installation package, including the SEP sesam client.

Client installation package

In order to install a SEP sesam client please choose the macos directory on the CD/DVD, or choose the download folder where you saved the SEP sesam installation package to. Start the installation by double-clicking on the sesam-cli_<VersionsID>-macosx.pkg file. Since the SEP sesam server needs access rights to the MacOS client to be able to contact and backup the client, you need to insert the server hostname. This can be done in the System Preferences Pane under Sesam Client which is opened directly after installation has been finished. Goto the Sesam Server tab, insert the SEP sesam server hostname, and hit Apply.

InstallSystemPreferencesMacOS en.png

In the Sesam Client tab you can see if the service is running.

GUI installation package

In order to install a SEP sesam gui please choose the macos directory on the CD/DVD, or choose the download folder where you saved the SEP sesam installation package to. Start the installation by double-clicking on the sesam-gui_<VersionsID>-macosx.pkg file. Since the SEP sesam server needs access rights to the MacOS client (included in the gui package) to be able to contact and backup the client, you need to insert the server hostname. This can be done in the System Preferences Pane under Sesam Client which is opened directly after installation has been finished. Goto the Sesam Server tab, insert the SEP sesam server hostname, and hit Apply.

In the Sesam Client tab you can see if the service is running.

In the Sesam GUI tab you can connect to a SEP Sesam GUI server. To start the GUI insert the name of the GUI server to connect to, select the GUI language, and hit Start Sesam GUI.

InstallSystemPreferencesMacOSGUI en.png

Configuration - SEP sesam first steps

In the following you will find a quick description of a typical SEP sesam configuration. For more detail information concerning all existing SEP sesam functions and configurations can be found in the User Manual and as well in the FAQs of the SEP sesam Wiki.

Step 1 Location

At the beginning you have to decide which operating systems should be backed up with SEP sesam. For this purpose you need the name and configuration of all target computer. In your GUI at Components -> Topology you can choose arbitrary location names and descriptions, since each client has to be assigned to a distinct location. By default the location LOCAL is created on a server (in our example informatix). Go to Components -> Topology and press New Location on the taskbar. Please insert the Name HOME and hit OK . By now your Topology should look as follows.

GUITopologie en.png

Step 2 Clients

To add clients to the just created location go to Components -> Topology -> HOME -> new Client. Depending on the operating system running on the client you have to choose one of the following platforms: Windows, UNIX, VMS oder NETWARE. The name of the client has to be the network host name of the computer. The name has to be resolvable either by DNS or hosts-file. Please insert the platform specific operating system of the client in the corresponding box.. The dialog Task for new client appears right after confirming the client by pressing OK, please select no. In our example we added a Windows (qsbox1) and a Linux (talentix) client to our location HOME. After configuring each of the clients we selected no in the Task for new client dialog.

GUITopologieClients en.png

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 inserts their data in the SEP sesam database. You can see available data stores i.e. DiskHard and DiskChange by selecting Components -> Data Stores. By default a data store (Test-Store) is created on the SEP sesam partition. In the following we will use the existing Test-Store for our sample back up.

Step 4 Tasks - What should be backed up?

Choose the location of interest in Tasks -> by Client, in our example we choose HOME, and select the client to be backed up. Then select New backup task from the taskbar. Please insert the description for a backup task in the appearing window. The task name can be chosen arbitrarily (max. 32 characters). We recommend to use descriptive names. The input box Source comprises the drives, folders, and files that will be backed up.

For our sample system we create a total of 13 backup tasks

  • one backup task for your SEP sesam (SESAM_BACKUP, created automatically)
  • one System Recovery backup task for each Windows system (qsbox1_system_recovery, informatix_system_recovery)
  • one all backup task per Client for all data (qsbox1_data_all, talentix_data_all, informatix_data_all). Please make sure to check the Option VSS for each Winodws client.
  • one backup task for each database (qsbox1_mssql_all, talentix_ORACLE, talentix_postgresall)
  • one backup task for each virtual machine (qsbox1_SEP_Cloud_notus, qsbox1_SEP_Cloud_VMware_vCenter, qsbox1_SEP_Cloud_Windows7)

GUIAuftraegenachClients en.png

Those backup tasks can be grouped in our Tasks -> by Groups menu. Please choose New Task Group and insert a name, then select the tab Assign Tasks and choose the backup tasks you want to assign to the task group on the left and move them to the right by pressing the right arrow to the right. In our sample system we create a group for each backup typ, i.e. we end up having 5 backup task groups.

GUIAuftraegenachGruppen en.png

Step 5 Schedules - When should the data be backed up?

Please switch to Scheduling -> Schedules. This window gives an overview of the configured schedules and their appointed date. All SEP sesam schedules can be controlled from here. We recommend the following schedules

  • 1 schedule (Diff, Mo.-Fr.) for all your data (regardless of the operating system), begin 8:00 pm
  • 1 schedule (Full, weekly) for all your data (regardless of the operating system), begin 10:00 am
  • 1 schedule (Full, daily) for your system, begin 9:00 pm
  • 1 schedule (Full, daily) for the SEP sesam self backup, begin 07:00 am
  • 1 schedule (Full, daily) for all your databases, begin 10:00 pm
  • 1 schedule (Full, daily) for all your virtual machines, begin 11:00 pm

GUIZeitplaene en.png

Please choose New -> New Schedule from the taskbar. Start by inserting a descriptive name for the schedule, like e.g. Data-Diff-Mo-Fr-2000, in case of a differential backup each working day at 8:00 pm. Then select the tag weekly and check Monday through Friday. Finally you have to insert the start time, in our case 20:00 o'clock and hit OK. For a one-time execution of the schedule right-click on the schedule and select Immediate Start. In the appearing dialog choose default priority and click on OK to start the backup.

Step 6 Backup event - How should the backup start?

To configure a cyclic backup we use the schedules that we just created. To realize a cyclic execution we have to create a New Backup Event for each schedule. The backup event is inserted in the SEP sesam calender which will then be executed by the SEPuler to the given timepoint. To generate a backup event please active on of the created schedules and choose New -> New Backup Event on the taskbar. In the given example in case of the Data-Diff-Mo-Fr-2000 schedule choose the Backup typ DIFF, the Media pool TEST-POOL and the Task Group Data, which we created earlier. We repeat this procedure using adequate settings all our schedules. In the next figure you see our thoroughly configured system.

GUIZeitplaenemitSicherungsauftraegen en.png

At this time point we have a completely configured system which will execute the newly created backup jobs at the given timepoints. Finally, after the execution of your backup event you can control the correct execution of your backups either in the menu Scheduling -> Calendar Sheet or in the menu Job State -> Backups.