View source for Source:FAQ - Installation and Configuration

<noinclude><languages /></noinclude>
=== {{anchor|RDS_installation}}<translate><!--T:1-->
How do I install a Remote Device Server (RDS)?=== 

<!--T:2-->
You can simply install and configure RDS as follows:</translate>
#<translate><!--T:3--> Depending on your operating system (Linux or Windows), download the relevant installation file from the {{Download}}. For details on Linux/Windows installation, see [[Special:MyLanguage/SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]].</translate>
#<translate><!--T:4--> Add RDS as a SEP sesam Client to the SEP sesam environment. Make sure that the DNS names (between SEP sesam Server and RDS) are correctly resolved (forward and reverse DNS lookup). For details, see [[Special:MyLanguage/Source:How_to_create_a_Remote_Device_Server_(RDS)#RDS_configuration|Configuring RDS]].</translate>  
#<translate><!--T:5-->
Add storage hardware (disk storage, tape libraries or single tape drives) to RDS.

<!--T:6-->
For step-by-step procedure, see [[Special:MyLanguage/Source:How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]].</translate>

=== {{anchor|GUI_Linux}}<translate><!--T:7-->
How do I install the SEP sesam GUI on a Linux system? === 

<!--T:8-->
To install a SEP sesam GUI on a Linux system, proceed as follows:</translate>
<ol><li><translate><!--T:9--> Download a package for your Linux distribution from {{Download}}.</translate></li>
<li><translate><!--T:10--> Depending on your distribution, install the SEP sesam GUI, as described in [[Special:MyLanguage/SEP_sesam_Quick_Install_Guide#GUI|SEP sesam Quick Install Guide]].</translate></li>
<li><translate><!--T:11--> After installing, check that the SEP sesam Server is available by using the following command:</translate></li>

<pre>nslookup <SEP sesam Server name></pre>

<translate><!--T:12--> For details, see [[Special:MyLanguage/How_to_check_DNS_configuration#nslookup|<tt>nslookup</tt>]].</translate>

<li><translate><!--T:13--> Make a shortcut with the following path:</translate></li>

<pre>/opt/sesam/bin/gui/sesam_gui -S <SEP sesam Server name></pre>

<li><translate><!--T:116--> When starting the GUI, you have to log in with an appropriate user, refer to [[Special:MyLanguage/About_Authentication_and_Authorization|About Authentication and Authorization]].</translate></li></ol>

=== {{anchor|RPM problems}}<translate><!--T:14-->
What problems may occur after installing the SEP sesam RPM package? === 
The following message appears when starting the SEP sesam GUI:

<!--T:15-->
 The connection to the server <SEP sesam Server> was denied.

<!--T:16-->
The last message was:</translate>
   
  java.rmi.RemoteException: Connection refused to host: [SEP sesam Server]; nested
  exeption is:
  java.net.Connect.Exception: Connection refused

<ul><li><translate>
<!--T:17-->
Make sure that the SEP sesam RMI Server component is active and the correct port is being used.</translate></li>

<pre><translate><!--T:99--> The program is terminated.</translate></pre>

<li><translate><!--T:18--> If you get this error message, check the Java version with the following command:</translate></li>

<pre>/opt/sesam/bin/sesam/java -version</pre>

<translate>
<!--T:19-->
In the Java v. < 1.7, you will need to update the Java files. For the list of supported Java versions, see [[Special:MyLanguage/Java_Compatibility_Matrix|Java Compatibility Matrix]].</translate><!--Still relevant?-->
</ul>

=== {{anchor|new_server_name}}<translate><!--T:20-->
How do I change the IP address and the name of the SEP sesam Server? === 

<!--T:21-->
Your license must first be [[Special:MyLanguage/FAQ#license_order|modified]] to match the new server name and/or IP address. Send the original license, the new server name, and the IP address to [mailto:info@sep.de info@sep.de].

<!--T:22-->
When you receive the new license information, you can change the SEP sesam Server name using <tt>sm_setup</tt>.</translate> 
<ol><li><translate><!--T:23--> Set the [[Special:MyLanguage/FAQ#profile_setting|SEP sesam profile]] and enter the following command:</translate></li>
<pre>sm_setup change_servername <mynewserver></pre>
<li><translate><!--T:24--> After executing the command, check the interfaces of the renamed SEP sesam Server: ''Main selection'' -> ''Components'' -> ''Clients'' -> double-click the server (Client) to open its properties. In the '''''Interfaces''''' field, manually remove the old interfaces and enter the new interfaces for ''http'' and ''https''.</translate></li>

<translate><!--T:25--> [[image:RDS_interfaces.jpg|720px|link=]]</translate>
<br clear=all>
</ol>

=== {{anchor|system_limits}}<translate><!--T:107-->
How do I adjust SEP sesam limits?=== 

<!--T:108-->
The best way to adjust SEP sesam limits on the system is to create the <tt>Systemd</tt> override file. By using this file the settings are not overwritten during the update.

<!--T:109-->
To adjust the SEP sesam limits, proceed as follows:

<!--T:103-->
''Example''</translate>
 >
 > root@cefix:~# systemctl show sepsesam.service | grep ^LimitCORE=
 > LimitCORE=2147483648
 
<ol><li><translate><!--T:104--> Create the override file and adjust the value:</translate></li>
<pre> > mkdir -p /etc/systemd/system/sepsesam.service.d/
 > echo "[Service]" >
 > /etc/systemd/system/sepsesam.service.d/override.conf echo 
 > "LimitCORE=infinity" >> 
 > /etc/systemd/system/sepsesam.service.d/override.conf</pre>
<li><translate><!--T:105--> Reload the system by using the command:</translate></li>
<pre> > root@cefix:~# systemctl daemon-reload</pre>
<li><translate><!--T:106--> Then specify:</translate></li>
<pre> > root@cefix:~# systemctl show sepsesam.service | grep ^LimitCORE= 
 > LimitCORE=infinity</pre>
</ol>

=== {{anchor|data_store_calculation}}<translate><!--T:40-->
How do I calculate the data store capacity (free space calculation and license check)?  === 

<!--T:41-->
Data store volume sizing and capacity usage should be managed at the partition level. It is recommended that only SEP sesam data is stored on the respective volume. Note that it is possible to store non-SEP sesam data on the same partition as the data store without including it in the fill level calculation and thus the license check. For details, see [[Special:MyLanguage/Data_Store#capacity|Data store capacity]].

<!--T:42-->
When specifying the capacity value, a dedicated partition must have enough free space. The method for calculating the required disk space is:

<!--T:43-->
 space occupied by SEP sesam + free disk space = DS capacity

<!--T:44-->
where DS capacity is the configured capacity value in the SEP sesam's data store configuration. 

<!--T:45-->
{{Note|SEP sesam expects the configured data store space to be available.
*It is essential that the value of volume size of non-sesam data is always larger than the data store capacity value.
*If the configured data store capacity is not completely available for SEP sesam (i.e., if the non-sesam data occupies more space), backup or migration tasks will fail even if there is enough free space on disk.}}

<!--T:46-->
[[Image:datastorePositive.png|530px|link=]][[Image:datastoreNegative.png|530px|link=]]
[[File:datastorePositiveError2.png|530px|link=]]
<br clear=all>

<!--T:47-->
'''''Example'':'''

<!--T:48-->
 Volume size:     10 TB
    Used by SEP sesam:    4 TB
    Used by non SEP sesam 3 TB
    Free disk space:  3 TB
    ======================

<!--T:49-->
 DS capacity:      6 TB
    4 TB + 3 TB     > 6 TB:  -> Backup can start
    ----------------------
    DS capcity:       8 TB
    4 TB + 3 TB     < 8 TB:  -> Backup will fail

<!--T:50-->
For example, a data store reports the following error:

 <!--T:51-->
 Not enough disk space could be freed to reach high water mark of -100GB for data store Data-Store. 
 (Data store: Data-Store. Free space: 696GB . Freed: 3GB).</translate> <!-- Is this how the actual message is reported? -->

<translate><!--T:52-->
''Solution'': You have to correct the capacity value of your data store.</translate>

=== {{anchor|Oracle_SID_number}}<translate><!--T:53-->
How do I determine the number of SID for Oracle? === 

<!--T:54-->
You can determine the number of SID for Oracle in the following ways:</translate>
<ul><li><translate><!--T:55--> View the list of the operating system's running processes.</translate></li>
<translate><!--T:56-->
If an Oracle instance is running, the system monitor will also be running. The name of the Oracle process always contains part of the instance name. The common form is <tt>ora_<process_name>_<sid></tt>

<!--T:57-->
''Example:''</translate>

<pre> oracle@myhost:/ ps -ef | grep smon
 oracle 23557 11596 0 Dec 19 ? 0:22 ora_smon_rac1</pre>

<translate><!--T:58--> In this case, the SID is ''rac1''.</translate>
<li><translate><!--T:59--> Check the ''oratab''.</translate></li>
<translate><!--T:60-->
Open the ''oratab'' in <tt>/var/opt/oracle</tt>. You will find the name of the instance and the Oracle home for automatically starting Oracle instances.

<!--T:61-->
''Example:''</translate>

<pre> oracle@myhost:cat /var/opt/oracle/oratab
 rac1:/opt/app/oracle/product/10.2.0/db_1:N</pre>

<li><translate><!--T:62--> View the parameter file.</translate></li>
<translate><!--T:63--> In the Oracle ''home'' under dbs or database, you will find either <tt>init<sid>.ora</tt> or the relevant SP file. The parameters of the instance are stored here. The ''db_name'' and ''instance_name'' parameters provide information about the database name and SID.</translate>
<li><translate><!--T:64--> Sign in on the instance as DBA and query the relevant views.</translate></li>

<translate><!--T:65--> In SQL*Plus as DBA-User: SQL:</translate>

<pre> 1.	SHOW parameter db_name
 2.	SHOW parameter instance_name</pre>

<translate><!--T:66--> The following statements can be used from every tool:</translate>

<pre> 1.	SQL> SELECT instance_name FROM v$instance;
 2.	SQL> SELECT [name] FROM v$database;</pre>
</ul>

=== {{anchor|profile_configuration}}<translate><!--T:67-->
How do I configure the SEP sesam profile to run automatically during login?=== 

<!--T:68-->
Create a link in the directory <tt>/etc/profile.d/</tt> as follows:</translate>

 ln -s /var/opt/sesam/var/ini/sesam2000.profile /etc/profile.d/sesam.sh

=== {{anchor|GUI_client_permissions}}<translate><!--T:69-->
How do I set permissions for a GUI client? === 

<!--T:70-->
In previous SEP sesam versions, you have to set client permissions via the command line. As of version [[SEP_sesam_Release_Versions|4.4.3 ''Grolar'']], you can simply set client permissions by configuring ACLs in the SEP sesam GUI. For details, see [[Special:MyLanguage/Using_Access_Control_Lists|Using Access Control Lists]].

<!--T:110-->
[[Image:Authentication_permissions_Beefalo_V2.jpg|650px|link=]]</translate>
<br clear=all>

=== {{anchor|new_client_problems}}<translate><!--T:71-->
What problems may occur when adding a new client? === 

<!--T:72-->
The following errors may appear when adding new clients to the SEP sesam Server.

<!--T:73-->
'''Error message 1''':

<!--T:74-->
 No Access for Computer pc2 - please enter for pc1

<!--T:75-->
or

<!--T:76-->
 There is no SEP sesam installed on computer pc2, please install it.

<!--T:77-->
''The problem might be'':
* There is no SEP sesam Client software installed.
* The wrong system name is specified in the SEP sesam GUI.
* There is an active firewall between the two computers. 

<!--T:78-->
''Solution'':
* Install the SEP sesam software on the target client.
* If the name was entered incorrectly, delete it and then re-enter it.
* Deactivate the firewalls or install the SEP sesam firewall option.<!-- What does this mean?-->

<!--T:79-->
'''Error message 2''':

 <!--T:80-->
Rights Restriction -  [pc1.domain.de system] in pc2:<SESAM_VAR>/var/ini/sm_ctrld.auth

<!--T:81-->
''Problem'': The SEP sesam Server has no privileges to access the client.

<!--T:82-->
''Solution'': Enter the value in the square brackets into the client's {{Path|<SESAM_VAR>/var/ini/sm_ctrld.auth}}. 

<!--T:83-->
'''Error message 3''':

 <!--T:84-->
Test backup from pc2 does not restore to pc1 – please verify (ping, DNS, local STPD)

<!--T:85-->
''Problem'': The connection between the SEP sesam Client and Server is not functioning.

<!--T:86-->
''Solution'': Check DNS resolution. SEP sesam recommends using the <tt>sm_setup check_resolution</tt> command, as described in [[Special:MyLanguage/How_to_check_DNS_configuration#tools|How to check DNS configuration]]. Make sure that you have set up a SEP sesam profile before running the command; for details, see [[Special:MyLanguage/FAQ#profile_setting|FAQ: What happens when I set a profile?]]</translate>

=== {{anchor|Nagios}}<translate><!--T:87--> How do I use the Nagios plugin from Netway to query and monitor the SEP sesam database?</translate> ===  

{|style="margin-bottom: 1em; width:100%; border:1px solid #010050;"
| rowspan="2" style="padding:0px 10px 0px; width:5%"| [[File:SEP_Warning.png|35px|link=]]
| style="padding:0px 40px 0px 10px; font-size: 95%; color:black; text-align:left; width:95%" | '''<translate><!--T:88--> Attention </translate>'''
|-
| style="padding:0px 40px 0px 10px; color: black; font-size: 100%; text-align:left; width:90%" | 
<translate><!--T:89--> Open source monitoring tools like Nagios are not part of, nor are they supported by, SEP AG and/or its partners and subsidiaries. Neither are other programs or scripts which query data from the SEP sesam DB or any other SEP sesam module that are not specifically distributed by SEP AG. SEP cannot and will not make any guarantees or warranties as to the usability or functionality of such scripts. Therefore, for obvious reasons, SEP cannot offer support for any of these customer and client designed and implemented tools or programs. Consequently, there is no support for the client specific programs.</translate>
|}

<translate><!--T:90-->
NETWAYS GmbH has developed an open-source database query routine for SEP sesam – the [https://www.nagios.com/products/ '''Nagios plugin''']. In accordance with the OSF foundation rules, this is a free software package that comes with the standard disclaimers regarding warranty, usability, and functionality. In other words, use it for free at your own risk. You can download the plugin from {{download}}.

<!--T:91-->
'''Demo scripts from projects'''

<!--T:92-->
Various scripts have been written for specific projects to allow customers to query (retrieve information from) the SEP sesam DB. These scripts are very specific to the client environments and are in no way guaranteed to work in other environments. Sample scripts to query the SEP sesam database have been written illustrating the use of the Nagios methodology and are meant to be used for demonstration purposes only. They can be found at {{download}}.</translate>

=== {{anchor|command_event_configuration}}<translate><!--T:93-->
How do I configure a command event?=== 

<!--T:94-->
You can configure the command events in the SEP sesam GUI. You might have to set permissions to execute the commands. For details, see [[Special:MyLanguage/Creating_a_Command_Event|Creating a Command Event]].</translate>

=== {{anchor|follow-up}}<translate><!--T:95-->
How do I configure a follow-up event?=== 

<!--T:96-->
You can configure the follow-up events that are triggered on the SEP sesam Server once the initial event is completed. In the SEP sesam GUI, you can set up migration, saveset verify and other actions to be triggered immediately after the backup or other event is completed. For details on configuring such events, see [[Special:MyLanguage/Follow-up_Events|Follow-up events]].

<!--T:111-->
[[File:Follow_up_events_Beefalo_V2.jpg|650px|link=]]</translate>
<br clear=all>

==={{anchor|data_size}}<translate><!--T:97-->
How do I change data size units?=== 

<!--T:98-->
You can change the default unit for data size by using the ''menu bar'' -> ''Configuration'' -> ''Defaults'' -> select the ''Display Format'' tab. The data size can be specified either with (KB, MB, GB, TB) or binary prefix (KiB, MiB, GiB, TiB). 

<!--T:112-->
[[image:Defaults_data_size_Beefalo_V2.jpg|580px|link=]]</translate>
<br clear=all>

<translate><!--T:113--> You can also set a different data size unit for the individual table. For details, see [[Special:MyLanguage/Changing_Data_Size_Units|Changing data size units]].</translate>

<noinclude>{{Copyright}}</noinclude>