4 4 3:SEP sesam Quick Install Guide: Difference between revisions

From SEPsesam
m (→‎See also: -> quick fix - link to configuration section in old guide)
(Added link to new article.)
Line 11: Line 11:


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_Sesam_CLI]]
| rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_sesam_Configuration_–_First_Steps]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also:  [[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]] –  [[Release Notes]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also:  [[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]] –  [[Release Notes]]
|}
|}
Line 386: Line 386:
==What is next?==
==What is next?==


[[Special:MyLanguage/SEP_sesam_Configuration_–_First_Steps|SEP sesam Configuration – First Steps]]
== See also==


[[Sesam_Quick_Install_Guide_V4.2.2/4.4#Configuration_-_SEP_sesam_first_steps|Configuration – SEP sesam first steps]]
== See also==
[[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]] – [[Special:MyLanguage/FAQ#installation_and_configuration|FAQ: Installation and configuration]]
[[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]] – [[Special:MyLanguage/FAQ#installation_and_configuration|FAQ: Installation and configuration]]

Revision as of 14:53, 29 November 2017

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

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check Documentation archive. You can also download PDF version of the SEP sesam Quick Install Guide.


Overview

A complete SEP sesam environment consists of different modules, which can be combined according to your needs to implement optimized backup. Modules interact with one another through SEP APIs which are also used for interaction with another software.

Essential modules of each SEP sesam environment are: SEP sesam Server, SEP sesam GUI, SEP sesam Remote Device Server (RDS), and SEP sesam Client(s). Each module is installed separately. The SEP sesam environment is managed centrally by the SEP sesam GUI.

SEP sesam also provides additional modules and functionality that enable consistent backup of databases (Oracle, MS SQL, IBM DB2, Informix SAP R/3, etc.), applications (like SAP), groupware systems, and virtualization environments. Some of these extensions are already a part of a Client package, and some require a separate license in order to function. For details on licenses, see Licensing. Check SEP sesam OS and Database Support Matrix to learn what is supported on which platforms. For list of all supported extensions and their configuration, see Extensions.

Once you have determined how you want to set up your SEP sesam environment, you can install the required components. Note that the installation procedure depends on the platform on which you are installing a SEP sesam package. Also, the procedure for installing different packages might differ.

SEP sesam Server hardware requirements

Hardware requirements/en

Microsoft Windows installation

Prerequisites

  • Before starting the SEP sesam installation, make sure that you are logged in as a local administrator or domain administrator.
  • For remote access via remote desktop connection (RDC), the RDC administrator needs the same access rights as the local administrator.
  • To install any of the SEP sesam components (SEP sesam Server, RDS, Client or GUI), (you will require an installation file which can be downloaded from Windows download. Make sure to download the correct file for your processor type.
  • If you are planning to install a server (including the GUI) or the GUI, Java Runtime Environment (JRE) must be installed on the system. For details on the required Java version, see Java Compatibility Matrix.
  • The .Net Framework 4 is required for server installation and can be deselected for all other SEP sesam components during installation.
  • x86 operating systems with more than 3.25 GB RAM must either reduce the amount of RAM to below to 3.25 GB or migrate to an x64 operating system. This is necessary because SEP sesam requires 64 KB blocks for LTO (Linear Tape Open) whereas an x86 system can only write 32 KB blocks to tape drive because the PAE (Physical Address Extension) is automatically activated. Also, a loader cannot be accessed properly by SEP sesam.
  • SEP sesam uses network resolution for server to client communication. Before installing, you should test DNS name resolution by simply pinging (using both, long and short name) from server to client and back. For details on DNS resolution check, see How to check DNS configuration.
  • Ensure that any used SCSI devices are recognized by the operating system to which you are installing SEP sesam. SEP sesam checks the SCSI bus attached storage devices during the installation and adds its data to the database. SEP sesam can only see devices recognized by the operating system.
  • It is recommended to disable firewall to avoid problems during the SEP sesam installation. Once SEP sesam is installed, you can enable the firewall with exceptions made for the SEP sesam services.
  • For details on SEP sesam default ports, see Which are SEP sesam default TCPIP ports?

Installation

SEP sesam provides four installation packages: SEP sesam Client, SEP sesam GUI, SEP sesam RDS and SEP sesam Server (includes the Client and GUI components). In the installation example below, we will use the SEP sesam Server installation package.

  1. Locate the download folder where you saved the SEP sesam installation package and double-click the sesam-srv-<Version_ID>-windows.x<SysTyp>.exe file to start the installation. Note that on Windows 7, you must explicitly execute the .exe file as administrator even if you are logged in as an administrator. Select your installation language and click Next.
  2. Agree to the license agreement and click Next again.
  3. Choose whether you want the the SEP sesam services to run under the Standard system accountor a Custom user account. It is recommended to give the SEP sesam Server services a Domain user account belonging to the Domain admins and the Local administrators groups. After choosing a user account, click Next.
  4. InstallStartAs en.png


  5. Select an installation directory for the program files (including the folders <SESAM_ROOT>\bin and <SESAM_ROOT>\skel) and the application data (including the folder <SESAM_ROOT>\var. This folder requires significant storage space if installing a server). Click Next.
  6. InstallChangeInstallationFolder en.png


  7. In the next window, select which of the four SEP sesam components you want to install (SEP sesam Server, SEP sesam Remote Device, SEP sesam GUI or SEP sesam Client). There is an additional option of installing a GUI with the SEP sesam Remote Device and a client with the SEP sesam GUI.
  8. InstallSesamFeatures en.png


  9. After selecting a component, click Next.
    Information sign.png Note
    SEP sesam Server package already includes all other components. If you are installing a Remote Device Server (RDS), you can also include a GUI. If you are installing a GUI, you can also include the Client.
  10. Depending on which components you are installing, proceed accordingly:
    • If you are installing the SEP sesam Server, click Install and then Finish to complete the installation.
    • If you are installing the SEP sesam RDS, SEP sesam GUI or SEP sesam Client, type the name of the SEP sesam Server (in the example below, the name of the server is Informatix).
    Information sign.png Note
    You must enter the hostname and not the IP address of the SEP sesam Server. The server name may not contain underscores.
    InstallServerName en.png


  11. Click Next. The firewall information dialog is only intended for purposes of information. Take note of the information and click OK. Click Install to install the selected SEP sesam component and then click Finish to complete the installation.

If you have a problem or questions regarding installation, also check FAQ: Installation and configuration.

Linux

SEP provides RPM packages for the most common Linux distributions (for example, SuSE and RedHat) and DEB files for Debian Linux distributions. The latter run on most Debian-based distributions, such as Ubuntu.

It is recommended to search for a previously installed SEP sesam Server version to verify that no previos installation package or component is already in place. The following commands can be used to search for an installation:

rpm -qa | grep sesam

Finds a previously installed Sesam package in the package database.

cat /etc/sesam2000.ini

If this INI-file exists, this means that a Sesam installation is already on the system.

ps fax | grep sm_

Finds running Sesam processes in the system.

Prerequisites

  • Before starting the SEP sesam installation, make sure that you are logged in as root.
  • To install any of the SEP sesam components (SEP sesam Server, RDS, Client or GUI), you will require an installation file which can be downloaded from Linux download. Make sure to download the correct file for your processor type.
  • If you are planning to install a server (including the GUI) or the GUI, Java Runtime Environment must be installed on the system. For details on the required Java version, see Java Compatibility Matrix.
  • SEP sesam uses network resolution for server to client communication. Before installing, you should test DNS name resolution by simply pinging (using both, long and short name) from server to client and back. For details on DNS resolution check, see How to check DNS configuration.
  • Ensure that any used SCSI devices are recognized by the operating system to which you are installing SEP sesam. SEP sesam checks the SCSI bus attached storage devices during the installation and adds its data to the database. SEP sesam can only see devices recognized by the operating system.
  • It is recommended to disable firewall to avoid problems during the SEP sesam installation. Once SEP sesam is installed, you can enable the firewall with exceptions made for the SEP sesam services.
  • The PostgeSQL server package from the used distribution install medium has to be installed. The SEP sesam database uses PostgreSQL database binaries.
  • For details on SEP sesam default ports, see Which are SEP sesam default TCPIP ports?
Information sign.png Note
On RHEL, the SEP sesam installation changes the permissions of /var/run/postgresqlto grant SEP sesam users PostgreSQL access privileges.

SEP sesam Server installation

Installing PostgreSQL

A PostgreSQL database is needed for 64-bit SEP sesam installations. This guide explains how to install this database software on various Linux distributions.

The database can be installed on a different Linux-based distributions:

  • SLES10/SLES11, OpenSuSE and newer
  • Debian/Ubuntu/UCS
  • RHEL / CentOS

For details on PostgreSQL backup or restore configuration, see PostgreSQL Backup and PostgreSQL Restore.

SLES10/SLES11 and newer, OpenSuSE based distributions

The PostgreSQL database can be installed using Yast or other common command line tools (rug of zypper). The prerequisite is SLES, i.e. OpenSuSE install CD.

Installing with zypper

OpenSuse as well as SLES10 or SLES11 include the tool zypper to (de-)install packages in the command line. The package name for the PostgreSQL database is postgresq1-server. This program's installation includes all dependencies that are needed for SEP sesam.

The installation is performed as follows:

kiwi:~ # zypper install postgresql-server
Loading files of the repository...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are being installed:
  postgresql postgresql-libs postgresql-server 

Total size of the download: 4,1 M. After the operation an additional 7,1 M will be needed.
Continue? [YES/no]: YES
Package postgresql-libs-8.3.7-0.1.1.i586 is being called (1/3), 175,0 K (560,0 K installed)
Calling: postgresql-libs-8.3.7-0.1.1.i586.rpm [done]
Installing: postgresql-libs-8.3.7-0.1.1 [done]
Package postgresql-8.3.7-0.1.1.i586 is being called (2/3), 1023,0 K (4,2 M installed)
Calling: postgresql-8.3.7-0.1.1.i586.rpm [done]
Installing: postgresql-8.3.7-0.1.1 [done]
Package postgresql-server-8.3.7-0.1.1.i586 is being called (3/3), 3,0 M (12,4 M installed)
Calling: postgresql-server-8.3.7-0.1.1.i586.rpm [fertig (1,1 M/s)]
Installing: postgresql-server-8.3.7-0.1.1 [done]

Afterwards the PostgreSQL instance can be started once:

kiwi:~ # /etc/init.d/postgresql start
Initializing the PostgreSQL database at location /var/lib/pgsql/data    done 
Starting PostgreSQL                                                     done
Installing with YAST

You can also installing over the graphical interface. Searching and selecting the package is done via the YAST package search.

Installing on Debian based distributions (Debian/Ubuntu/UCS)

Debian based distributions automatically bring along according PostgreSQL packages over the online repositories and also on the install CDs.

Installing with apt-get

All Debian based distributions (Ubuntu, UCS) include the standard tool apt-get which is common for package management. With this tools packages can be installed and deinstalled in the command line.

The meta package PostgreSQL includes all dependencies that are needed for a SEP sesam installation.

root@hostname#: apt-get install postgresql
Pckagelists are being read... Done
Dependency tree is being created       
Reading status information... Done
The following packages have been installed automatically and aren't needed any longer:
  libnm-util0 libpcsclite1 dhcdbd libpkcs11-helper1 libiw29 wpasupplicant libnl1 openvpn-blacklist
Use »apt-get autoremove« to remove them.
The following additional packages are being installed:
  postgresql-8.3 postgresql-client-8.3 postgresql-client-common postgresql-common
Recommended packages:
  oidentd ident-server postgresql-doc-8.3
The following NEW packages are being installed:
  postgresql postgresql-8.3 postgresql-client-8.3 postgresql-client-common postgresql-common
0 updated, 5 new installed, 0 to be removed and 53 not updated.
7257kB of archives have to be downloaded.
After this operation 19.6 MB of storage space are needed additionally.
Do you want to continue [Y/n]? Y
Getting:1 http://ftp.de.debian.org lenny/main postgresql-client-common 94lenny1 [46,8kB]
Getting:2 http://ftp.de.debian.org lenny/main postgresql-client-8.3 8.3.7-0lenny1 [1651kB]
Getting:3 http://ftp.de.debian.org lenny/main postgresql-common 94lenny1 [116kB]
Getting:4 http://ftp.de.debian.org lenny/main postgresql-8.3 8.3.7-0lenny1 [5208kB]
Getting:5 http://ftp.de.debian.org lenny/main postgresql 8.3.7-0lenny1 [235kB]
7257kB were downloaded in 4s (1686kB/s)
Vorkonfiguration der Pakete ...
Selecting previously deselected package postgresql-client-common.
(Reading database ... 96396 Files and directories are currently installed.)
Unpacking postgresql-client-common (from .../postgresql-client-common_94lenny1_all.deb) ...
Selecting previously deselected package postgresql-client-8.3.
Unpacking postgresql-client-8.3 (from .../postgresql-client-8.3_8.3.7-0lenny1_i386.deb) ...
Selecting previously deselected package postgresql-common.
Unpacking postgresql-common (from .../postgresql-common_94lenny1_all.deb) ...
Selecting previously deselected package postgresql-8.3.
Unpacking postgresql-8.3 (from .../postgresql-8.3_8.3.7-0lenny1_i386.deb) ...
Selecting previously deselected package postgresql.
Unpacking postgresql (from .../postgresql_8.3.7-0lenny1_all.deb) ...
Converting trigger for man-db ...
Setting up postgresql-client-common (94lenny1) ...
Setting up postgresql-client-8.3 (8.3.7-0lenny1) ...
Setting up postgresql-common (94lenny1) ...
supported_versions: WARNING: Unknown Debian release: 5.0.2
Adding user postgres to group ssl-cert
Setting up postgresql-8.3 (8.3.7-0lenny1) ...
Creating new cluster (configuration: /etc/postgresql/8.3/main, data: /var/lib/postgresql/8.3/main)...
Moving configuration file /var/lib/postgresql/8.3/main/postgresql.conf to /etc/postgresql/8.3/main...
Moving configuration file /var/lib/postgresql/8.3/main/pg_hba.conf to /etc/postgresql/8.3/main...
Moving configuration file /var/lib/postgresql/8.3/main/pg_ident.conf to /etc/postgresql/8.3/main...
Configuring postgresql.conf to use port 5432...
Starting PostgreSQL 8.3 database server: main.
Setting up postgresql 8.3.7-0lenny1) ...
root@hostname#:
Installing on RHEL / CentOS based distributions
Installing via yum package manager

Installing in RHEL or CentOS based distributions is similar as in SLES or Debian. For this distributions is used the command line tool yum:

[root@rhel5fix ~]# yum install postgresql-server
Loading "downloadonly" plugin
Loading "rhnplugin" plugin
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
rhel-i386-server-5        100% |=========================| 1.3 kB    00:00     
Reading repository metadata in from local files
primary.xml.gz            100% |=========================| 2.3 MB    00:02     
################################################## 6101/6101
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for postgresql-server to pack into transaction set.
postgresql-server-8.1.11- 100% |=========================|  29 kB    00:00     
---> Package postgresql-server.i386 0:8.1.11-1.el5_1.1 set to be updated
--> Running transaction check
--> Processing Dependency: postgresql = 8.1.11-1.el5_1.1 for package: postgresql-server
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for postgresql to pack into transaction set.
postgresql-8.1.11-1.el5_1 100% |=========================| 121 kB    00:00     
---> Package postgresql.i386 0:8.1.11-1.el5_1.1 set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 postgresql-server       i386       8.1.11-1.el5_1.1  rhel-i386-server-5  3.9 M
Installing for dependencies:
 postgresql              i386       8.1.11-1.el5_1.1  rhel-i386-server-5  2.9 M

Transaction Summary
=============================================================================
Install      2 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 6.7 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): postgresql-server- 100% |=========================| 3.9 MB    00:04     
(2/2): postgresql-8.1.11- 100% |=========================| 2.9 MB    00:03     
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: postgresql                   ######################### [1/2] 
  Installing: postgresql-server            ######################### [2/2] 
Installed: postgresql-server.i386 0:8.1.11-1.el5_1.1
Dependency Installed: postgresql.i386 0:8.1.11-1.el5_1.1
Complete!

Installing SEP sesam Server package

To install the SEP sesam Server, select the download folder where you saved the SEP sesam Server installation package.

  • Use the following command to install *.rpm files:
rpm -Uvh sesam_srv<Version.OS.SystemTyp>.rpm
  • Use the following command to install *.deb files:
dpkg -i sesam-srv<Version.SystemTyp>.deb

The SEP sesam Server installation includes a GUI which is automatically installed. If the display variable has been set, the GUI starts immediately after the installation is completed. To start the GUI manually, use the following command:

/opt/sesam/bin/gui/sesam_gui

SEP sesam Client installation

To install the SEP sesam Client, select the download folder where you saved the SEP sesam Client installation package.

  • Use the following command to install *.rpm files:
rpm -Uvh sesam_cli<Version.OS.SystemTyp>.rpm
  • Use the following command to install *.deb files:
dpkg -i sesam-cli<Version.SystemTyp>.deb

Run the following command on the client to grant the SEP sesam Server access rights and to allow it to contact and backup the client:

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

If you have a problem or questions regarding installation, also check FAQ: Installation and configuration.

SEP sesam GUI installation

The SEP sesam GUI package have to be installed separately. The SEP sesam Server installation package already includes a GUI, which is installed automatically.

To install the SEP sesam GUI, select the download folder where you saved the SEP sesam GUI installation package.

  • Use the following command to install *.rpm files:
rpm -Uvh sesam_gui<Version.OS.SystemTyp>.rpm
  • Use the following command to install *.deb files:
dpkg -i sesam-gui<Version.SystemTyp>.deb

On KDE and Gnome, the installation generates a link on the root user desktop to start the GUI. This link must target the correct SEP sesam Server. Open the link properties and add the following parameter to the command line:

-S <SEP sesam Server Name>

If you have a problem or questions regarding installation, also check FAQ: Installation and configuration.

Mac OS X

Two SEP sesam installation packages are available for Mac OS X: the SEP sesam Client installation package and the SEP sesam GUI installation package, which also includes the SEP sesam Client.

SEP sesam Client for Mac OS X 10.8 supports standard file backups with ACL's. Disaster recovery is not supported!

Prerequisites

  • Before starting the SEP sesam installation, make sure that you are logged in as a local administrator or domain administrator.
  • To install any of the SEP sesam components (SEP sesam Client or GUI), you will require an installation file which can be downloaded from download center.
  • If you are planning to install a GUI, Java Runtime Environment must be installed on the system. For details on the required Java version, see Java Compatibility Matrix.

Client installation

  1. Select the macos directory on the CD/DVD or the download folder where you saved the SEP sesam Client installation package.
  2. To install the SEP sesam Client, double-click the sesam-cli_<VersionsID>-macosx.pkgfile.
  3. The SEP sesam Server requires access rights to the Mac OS X client so that it can contact and backup the client. Open the Mac OS X System Preferences, select the Sesam Server tab and enter the server hostname. Click Apply.
  4. InstallSystemPreferencesMacOS en.png

You can verify that the service is running under the Sesam Client tab.

GUI installation

  1. Select the macos directory on the CD/DVD or the download folder where you saved the SEP sesam GUI installation package.
  2. To install the SEP sesam Client, double-click the sesam-cli_<VersionsID>-macosx.pkgfile.
  3. The SEP sesam Server requires access rights to the Mac OS X client (included in the GUI package) so that it can contact and backup the client. Open the Mac OS X System Preferences, select the Sesam Server tab and enter the server hostname. Click Apply.
  4. You can verify that the service is running under the Sesam Client tab.
  5. You can connect to a SEP sesam GUI server under the Sesam GUI tab. To start the GUI, enter the name of the GUI server, select the language and click Start Sesam GUI.
  6. InstallSystemPreferencesMacOSGUI en.png

If you have a problem or questions regarding installation, also check FAQ: Installation and configuration.

What is next?

SEP sesam Configuration – First Steps

See also

Automatic Installation on WindowsUpdating SEP sesamApplying Service Packs on LinuxSEP sesam CLIFAQ: Installation and configuration