View source for FAQ

<div class="noprint"><languages /></div>
<translate><!--T:1-->
{{Copyright SEP AG en}}

== {{anchor|license_and_version}}LICENSES & VERSIONS== <!--T:2-->

=== {{anchor|version requirement}}Does SEP sesam require identical versions of SEP sesam Client and Server? === <!--T:3-->
To avoid general version compatibility issues, the SEP sesam Client and the SEP sesam Server / Remote Device Server should always have the same version number.<br>
Forward and backward compatibility is limited to path backups only.

=== {{anchor|license order}}How do I order a new licence?=== <!--T:4-->
{{How do I order a new license}}

=== {{anchor|license activation}}How do I activate a license?=== <!--T:5-->
{{How do I activate a license}}

=== {{anchor|error}}Why does the W008-License TCPIP address not match the local address 127.0.0.2? === <!--T:6-->

<!--T:7-->
This problem usually occurs on SLES-based Linux systems. Check the file <tt>/etc/hosts</tt> and change the relevant entry for the loopback address''127.0.0.2'' or remove it from the <tt>/etc/hosts</tt> file entirely.

=== {{anchor|community version}}How do I obtain the community version? === <!--T:8-->
{{How do I obtain the community version}}</translate>

<translate>=== {{anchor|free Zarafa extension}}How do I obtain the free [http://sepsoftware.com/fileadmin/user_upload/datenblaetter/en/SEPsesam_Zarafa_emea.pdf Zarafa extension]? === <!--T:9-->
'''Free [http://sepsoftware.com/fileadmin/user_upload/datenblaetter/en/SEPsesam_Zarafa_emea.pdf Backup for Zarafa environments]'''

<!--T:10-->
In addition to the most common server operating systems such as Novell Netware, Linux, Windows, Unix and Solaris, SEP sesam provides extensions that execute hot backups on common groupware and database applications. A complete overview of supported software is available in the '''[[SEP sesam OS and Database Support Matrix]]'''.

<!--T:11-->
'''[http://www.zarafa.com Zarafa]''' users can download the complete SEP sesam environment to backup their Zarafa installation for free. The following modules are provided in the free download:

<!--T:12-->
* ''SEP sesam ONE Server'' for scheduling and managing all backup and restore tasks. ''SEP sesam ONE'' supports backup to tape and disk. A 500 GB Virtual Tape Library is integrated into the base product.

<!--T:13-->
* ''SEP sesam Zarafa Online Module'' for up to 10 users. The module supports online backup and restore of the complete Zarafa server environment for up to 10 users, including restore and recovery of single mailboxes and e-mails.

<!--T:14-->
* ''SEP sesam MySQL Online Module''. The module supports hot backup and restore of the Zarafa database.

<!--T:15-->
* ''SEP sesam Graphical User Interface (GUI)'', which includes the powerful restore wizard.

<!--T:16-->
The free Zarafa Server backup license does not expire but is limited to this dedicated environment. Note that no upgrade services or technical support are included.

<!--T:17-->
The free Zarafa version can be upgraded with the following additions, available at the '''[http://sepsoftware.com/produkte/ SEP homepage]''':
* High-capacity SEP sesam Servers License (Standard Server with 5 streams and 1TB or Advanced Server with 124 data streams and 1TB)
* Additional SEP sesam Clients to back up servers other than the Zarafa Server
* Additional online database extensions
* Autoloader support
* Disaster recovery modules
* SAN backup capability
* Citrix XenServer or VMware ESX/ESXi disaster recovery
* Expanded storage capability
* or additional Zarafa users

<!--T:18-->
To apply for a free Zarafa backup, send the following information to [mailto:sales@sep.de sales@sep.de]:

 <!--T:19-->
* Name of your company
 * Complete address
 * Contact person, including phone and email
 * Which additional servers do you use in your IT environment?
 * Which backup software do you use besides SEP sesam?

<!--T:20-->
Additionally, provide the Zarafa related information:
 * SEP sesam Server installation – is it on a Zarafa server or on a dedicated SEP sesam Server?
 * IP address of the SEP sesam Server
 * Hostname of the SEP sesam Server
 * Operating system of the SEP sesam Server
 * Number of Zarafa users

<!--T:21-->
'''All SEP sesam software is available at the {{download}}.'''

<!--T:22-->
[https://download.sep.de/linux/ SEP sesam Server for Linux]<br>
[https://download.sep.de/windows/ SEP sesam Server for Windows]<br>
<!--Broken link: [http://download.sep.de/extensions/groupware/zarafa/ Zarafa module]-->Zarafa module (included in SEP sesam Client for Linux since version 3.6)<br>
[https://download.sep.de/extensions/databases/mysql/ MySQL module] (included in SEP sesam Client for Linux since version 3.6)<br>
An introduction on backing up the Zarafa server with SEP sesam is available on the SEP Wiki:
[[SEP sesam Extension for Zarafa]].</translate>

<translate>== {{anchor|requirements}}REQUIREMENTS== <!--T:23-->

=== {{anchor|HV and SV requirements}}What are the hardware and software requirements for a SEP sesam Server? === <!--T:24-->
'''SEP sesam Server hardware requirements'''

<!--T:25-->
{{:Hardware_requirements/en}}

<!--T:1157-->
'''Si3 deduplication hardware requirements'''
*For the minimum Si3 hardware requirements that apply to SEP sesam Si3 deduplication server, see the above requirements list. Keep in mind that these requirements represent the demand for deduplication only. In addition, the amount of memory for the operating system and other services should be taken into account.
{{:Si3_Deduplication_Hardware_Requirements/en}}

<!--T:26-->
'''SEP sesam Server software requirements'''
* '''Java''': The required Java version depends on SEP sesam version. See [[Special:MyLanguage/FAQ#JAVA_version|Java Compatibility Matrix]].
* '''Linux''': PostgreSQL server package from the Linux distribution is required for 64-bit Linux. Note that SEP sesam RPM packages already include PostgreSQL server package, however, for some older SEP sesam versions, you may have to install the PostgreSQL manually. For details, see [[Special:MyLanguage/4_4_3:Installing_PostgreSQL|Installing PostgreSQL]].
* '''Microsoft Windows''': Check [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#windows|prerequisites for Microsoft Windows installation]].

<!--T:27-->
{{Box Hint|Note|
We recommend that you use a separate partition for the SEP sesam metadata in order to prevent SEP sesam metadata from filling up the operating system partition.<br>
* Linux: create a mount point for <tt>/var/opt/sesam/var</tt> (see recommended size above)
* Microsoft Windows: add a new drive (see recommended size above) and install SEP sesam on this drive.}}</translate>

<translate>=== {{anchor|JAVA version}}Which Java version does SEP sesam require? === <!--T:28-->

<!--T:579-->
The required Java version depends on SEP sesam version. Check the following Java compatibility matrix for details. Oracle/Sun Java, IBM Java or OpenJDK can be used. For details on how to install Java, see [[Special:MyLanguage/4_4_3_Beefalo:Installing_and_Managing_Java|Installing and Managing Java]]. 
{{:Java Compatibility Matrix/en}}

<!--T:580-->
You can check your Java version with the following command:

   <!--T:29-->
java -version

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

 #> java -version
 java version "1.7.0_45"
 Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
 Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

<translate>==== Linux – RPM ==== <!--T:581-->

<!--T:582-->
If the SEP sesam Server is installed as an RPM package, Java must also be installed as an RPM.

<!--T:583-->
'''Note:''' To install a SEP sesam Server on an OES2 system, Java 1.5<!-- Is this the correct version? --> must remain the default version so that Novell-specific functions can operate. If a different Java version (such as 1.6)<!-- Is this the correct version? --> is installed on the system via RPM, the default Java version is kept, i.e. the reinstallation doesn't overwrite it. Java and the SEP sesam Server can be installed as described below.

<!--T:584-->
In the example below, 64-bit Sun Java is used:

<!--T:585-->
* After the download is complete, give the package execution rights:
 #> chmod +x jre-6u25-linux-x64-rpm.bin

<!--T:586-->
* Install the JRE Binary package:

 <!--T:587-->
#> ./jre-6u25-linux-x64-rpm.bin
 Unpacking...
 Checksumming...
 Extracting...
 UnZipSFX 5.50 of 17 February 2002, by Info-ZIP (Zip-Bugs@lists.wku.edu).
   inflating: jre-6u25-linux-amd64.rpm
 Preparing...                ########################################### [100%]
    1:jre                    ########################################### [100%]
 Unpacking JAR files...
         rt.jar...
         jsse.jar...
         charsets.jar...
         localedata.jar...
         plugin.jar...
         javaws.jar...
         deploy.jar...
 Done.

<!--T:588-->
* Verify that the Sun Java version was properly registered in the package database:

 <!--T:589-->
#> rpm -qa | grep jre
 jre-1.6.0_25-fcs

<!--T:590-->
* The SEP sesam Server is installed via an RPM package. The SEP sesam installer finds the Java information in the package manager and automatically creates a link to it in the directory {{Path|/opt/sesam/bin/sesam}}. If the SEP sesam Server and Java are installed via Tarball, you must create the link manually.</translate>

<translate>==== Linux – Tarball ==== <!--T:31-->

<!--T:32-->
If Java is installed as Tarball, the SEP sesam Server must also be installed as Tarball. The installation of a SEP sesam Server package with <tt>'''--nodeps'''</tt> is not supported.

<!--T:33-->
Install Java Tarball as follows:

<!--T:34-->
* Download a Java version that is compatible with your operating system, such as SUN Java 64-version <tt>jre-7u<version>-linux-x64.tar.gz</tt>, to{{Path|/opt/java}}.
* Go to the directory {{Path|/opt/java}}.

<!--T:35-->
* Extract the Tar archive ./jre-7u<version>-linux-x64.tar.gz to the folder {{Path|/opt/java}}. 

<!--T:36-->
* Java is now unpacked into the subfolder <tt>jre1.7.0_45</tt> and is ready to use. Java functions can be tested as follows:</translate>
 #>  /opt/java/jre1.7.0_45/bin/java -version
 java version "1.7.0_45"
 Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
 Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

<translate><!--T:37-->
* Create the directory structure {{Path|/opt/sesam/bin/sesam}} to link Java to the SEP sesam Server installation:</translate>
 #> ln -s /opt/java/jre1.7.0_45/bin/java /opt/sesam/bin/sesam/java

<translate><!--T:38-->
* You can now proceed with the installation of SEP sesam Server via Tarball.</translate>

<translate>==== Windows ==== <!--T:591-->

<!--T:40-->
You can operate several Java versions on Windows. The SEP sesam Server can work with a Java version other than the operating system's default Java version. Enter the path of your Java version into the {{Sesamroot|\var\ini\sm.ini}} file in the ''[JAVA]'' section:</translate>

   [JAVA]
   java_interpreter="C:\Program Files\Java\jre7\bin\java"
   java_home="C:\Program Files\Java\jre7"
   java_exit_on_fail=no

<translate><!--T:41-->
This gives the SEP sesam Server its own Java environment on startup.</translate>

<translate>=== {{anchor|Java download}}Where can I get the latest 64-bit version of Sun's JRE? === <!--T:42-->

<!--T:43-->
The link below takes you to a list of different versions of Sun's [http://en.wikipedia.org/wiki/JRE Java Runtime Environment] for your operating system and architecture (64- and 32-bit). After accepting the license agreement, you can download the relevant package.

<!--T:44-->
;{{Current-JRE}}</translate>

<translate>== {{anchor|installation and configuration}}INSTALLATION & CONFIGURATION == <!--T:45-->

=== {{anchor|RDS installation}}How do I install a Remote Device Server (RDS)?=== <!--T:46-->

<!--T:592-->
Detailed instructions can be found at [[How to create a Remote Device Server (RDS)]].
#*''Linux/UNIX'': Select and install the SEP sesam Remote Device Server package (for example, <tt>sesam_rts-4.0.2-13.rhel5.i386.rpm</tt> for RedHat) from the SEP download center.
#*''Windows'': Select the SEP sesam Server package (for example, <tt>sesam-srv-4.0.2.13-windows.exe</tt>) from the SEP download center. Start the installation and choose '''SEP sesam Remote Tape''' as the package.
#Add the computer as a normal SEP sesam Client under '''Components -> Topology'''. Ensure that the DNS between the SEP sesam Server and SEP sesam Remote Device Server is properly handled.
#Create a new drive group  under '''Components -> Disk Drives''' and select the drive from the remote computer as a '''New drive'''.
#To see the name of the new device on the Remote Device Server, use the command: {{Path|<SESAM_BIN>/sesam/slu topology}} (for example, <tt>Tape0</tt> or<tt>/dev/nst0</tt>). If you selected a disk drive, you only need to enter the drive type ''DISK_HARD''.
#Create a new media pool and assign it to the new drive group.
#Register the new media to the media pool.</translate>

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

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

 <!--T:1224-->
nslookup <SEP sesam Server name>

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

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

 <!--T:53-->
 /opt/sesam/bin/gui/sesam_gui -S <SEP sesam Server name></translate>
</ol>

<translate>=== {{anchor|RPM problems}}What problems may occur after installing the SEP sesam RPM package? === <!--T:54-->

<!--T:55-->
The following message appears when starting the SEP sesam GUI:

 <!--T:56-->
The connection to the server sesamserver was denied.

<!--T:57-->
The last message was:</translate>

   java.rmi.RemoteException: Connection refused to host: [SEP sesam-Server]; nested
   exeption is:
   java.net.Connect.Exception: Connection refused

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

 <!--T:59-->
The program is terminated.

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

 /opt/sesam/bin/sesam/java -version

<translate><!--T:61-->
If the Java version is not 1.7 or higher, you will need to update the Java files.

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

<!--T:593-->
Your license must first be [[Special:MyLanguage/FAQ#new_server_name|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:67-->
When you receive the new license information, you can change the SEP sesam Server name using <tt>sm_setup</tt>. Set the [[Special:MyLanguage/FAQ#profile_setting|SEP sesam profile]] and enter the following command:
 sm_setup change_servername <mynewserver>

<!--T:936-->
After executing the command, check the interfaces of the renamed SEP sesam Server: ''Main selection'' -> ''Components'' -> ''Clients'' -> double-click the server to open the properties. In the '''''Interfaces''''' field, manually remove the old interfaces and enter the new interfaces for ''http'' and ''https''.

<!--T:937-->
[[image:manual_add_remove_interfaces.png|link=]]
<br clear=all>

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

<!--T:1238-->
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:1239-->
To adjust the SEP sesam limits, proceed as follows:

<!--T:1240-->
''Example''</translate>
 >
 > root@cefix:~# systemctl show sepsesam.service | grep ^LimitCORE=
 > LimitCORE=2147483648
 
<ol><li><translate><!--T:1241--> Create the override file and adjust the value:</translate></li>
 > 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
<li><translate><!--T:1242--> Reload the system by using the command:</translate></li>
 > root@cefix:~# systemctl daemon-reload
<li><translate><!--T:1243--> Then specify:</translate></li>
 > root@cefix:~# systemctl show sepsesam.service | grep ^LimitCORE= 
 > LimitCORE=infinity
</ol>

<translate>=== {{anchor|antivirus scanner}}What effect does an antivirus scanner have on SEP sesam? === <!--T:68-->
Antivirus scanners may negatively impact the backup and restore operation:

<!--T:69-->
* The SEP sesam install process is very slow
* The GUI is slow or hangs for several seconds
* Backup and restore jobs are terminated abruptly
* Reduced data throughput and speed
* Sesam server / client is not available (Errorcode 10060)

<!--T:70-->
'''Solution'''<br>
Use antivirus exclusions rules for SEP sesam. The following items must be excluded from any virus scanning activities:

<!--T:71-->
* All SEP sesam [[Sesam_Admin_Manual#SEP_sesam_Directory_Structure|installation directories]] on the SEP sesam Server, Client and Remote Device Server (RDS):
** <tt>SESAM_BIN</tt> directory including all subfolders
** <tt>SESAM_VAR</tt> directory including all subfolders

<!--T:72-->
* Data store on the SEP sesam Server and Remote Device Server:
** Any partition on which data store has been configured for backup must be excluded from virus scanning.

<!--T:73-->
* All SEP sesam processes on the SEP sesam Server, Client and Remote Device Server:
** Exclude all executable files from the following directories:</translate>

  <SESAM_ROOT>/bin/sesam/*.*
  <SESAM_ROOT>/bin/sms/*.*

<translate><!--T:74-->
With some virus scanners, you can disable the ''Child Process Monitoring'' rule option. In this case, only the following SEP sesam processes must be excluded:</translate>

'''Windows:'''
  sm_main.exe
  sm_ctrld_main.exe
  sm_sshd.exe
  sm_db_main.exe
  sm_passd.exe
  sm_rmi_main.exe
  sm_sepuler.exe
  sm_sms_main.exe
  sm_data_server.exe
  sm_stpd_main.exe
  sbc.exe

'''Linux:'''
  sm_qm_main
  sm_ctrld_main
  sm_sshd
  sm_db_main
  sm_passd
  sm_rmi_main
  sm_sepuler
  sm_sms_main
  sm_data_server
  sm_stpd_main
  sbc

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

<!--T:76-->
In SEP sesam version 4.2.2, if non-SEP sesam data is stored on the same volume as the SEP sesam data store, then a SEP sesam storage license is required for this data. Now only SEP sesam data is counted.

<!--T:77-->
The method for calculating the required disk space changed with SEP sesam version 4.4. It is now possible to store non-SEP sesam data on the same partition as the data store. The new formula is as follows:<br><br>
<tt>space occupied by Sesam + free disk space > DS capacity</tt><br><br>

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

<!--T:79-->
{{Box Hint|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 free space on disk.}}

<!--T:80-->
[[Image:datastorePositive.png|500px]][[Image:datastoreNegative.png|500px]]
[[File:datastorePositiveError2.png|500px]]

<!--T:81-->
<br><br>
Example:

    <!--T:82-->
Volume size:     10 TB
    Used by Sesam:    4 TB
    Used by non Sesam 3 TB
    Free disk space:  3 TB
    ======================

    <!--T:83-->
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:84-->
For example, data store reports the following error:

  <!--T:85-->
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? -->

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

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

<!--T:88-->
'''View the list of the operating system's running processes'''

<!--T:89-->
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:90-->
;Example:</translate>

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

<translate><!--T:91-->
In this case, the SID is rac1.

<!--T:92-->
'''Check the oratab'''

<!--T:93-->
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:94-->
;Example:</translate>

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

<translate><!--T:95-->
'''View the parameter file'''

<!--T:96-->
In the Oracle home under dbs or database, you will find either <tt>init<sid></tt>.ora 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.

<!--T:97-->
'''Sign in on the instance as DBA and query the relevant views'''

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

 1.	SHOW parameter db_name
 2.	SHOW parameter instance_name

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

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

<translate><!--T:100-->
For more information on SID, see: http://www.ordix.de/ORDIXNews/1_2004/db_1.html (German).</translate>

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

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

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

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

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

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

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

<!--T:115-->
'''Error message''':

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

<!--T:117-->
or

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

<!--T:119-->
''The problem might be'':
* There might be no SEP sesam Client software installed.
* The wrong system name has been entered in the SEP sesam GUI.
* There is an active firewall between the two computers. By default, a firewall is active on Windows XP with SP2 and SuSE Linux after 9.1.

<!--T:120-->
''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.</translate>

<translate><!--T:121-->
'''Error message''':

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

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

<!--T:124-->
''Solution'': Enter the value in the [___] into the client's <tt><SESAM_VAR>/var/ini/sm_ctrld.auth</tt>.</translate>

<translate><!--T:125-->
'''Error message''':

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

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

<!--T:128-->
''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?]]

=== {{anchor|freeware version installation}}How can I install the freeware version of SEP sesam on SuSE LINUX 10.0 Prof. Community Version?=== <!--T:1188-->                  

<!--T:133-->
The installation can be accomplished using ''YasT''. If there is no SUN Java currently running on your computer, it will be automatically selected by ''YasT''. In addition, SEP sesam can be installed using the <tt>rpm -U <sesam serverpackage></tt>.</translate>

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

<!--T:135-->
{{Box_Attention|Attention – Disclaimer|
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.}}

<!--T:136-->
[http://www.netways.de/ NETWAYS GmbH] has developed an open source database query routine for SEP sesam – the '''Nagios plugin'''. In accordance with the OSF foundation rules, this is a free software package and comes with the standard disclaimers regarding warranty, usability and functionality. In other words, use it for free at your own risk.

<!--T:137-->
{{Box_Hint|Note|Since many names of parameters in the SEP sesam database have changed in version 4.0, you have to choose the relevant version of the plugin. You can download it from {{download}}.}}

<!--T:138-->
'''Demo scripts from projects'''
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>

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

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

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

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

<translate>==={{anchor|data_size}}How do I change data size units?=== <!--T:939-->
As of SEP sesam v. 4.4.3 ''Tigon'', you can change the default unit for data size. Data size can be specified either with decimal (KB, MB, GB, TB) or binary prefix (KiB, MiB, GiB, TiB). You can also set different data size unit for the individual table. For details, see [[Special:MyLanguage/Changing_Data_Size_Units|Changing data size units]].</translate>
<translate>== {{anchor|GUI}}GUI== <!--T:139-->

=== {{anchor|language setting}}How do I set a specific language for the SEP sesam GUI? === <!--T:140-->

<!--T:141-->
By default, the SEP sesam GUI always starts with the language of the operating system. This can be changed by adjusting the parameter <tt>-r</tt> of the GUI client. The parameter can be used when calling the GUI directly (i.e. on Linux) or when editing the link itself. The following settings are possible (do not use space after the parameter!):</translate>

 -rde
 -ren
 -ren_us
 -ren_gb

<translate><!--T:142-->
The first option represents German. The other three options represent English: the first English option shows time in 24-hour format whereas the second and the third option show time in the 12-hour format (AM and PM).

=== {{anchor|font setting}}How to set Chinese fonts? === <!--T:1189-->                  

<!--T:144-->
The default GUI font type ''Tahoma'' does not supply Chinese characters. The default type can be modified with the entry 'key= default_font[_...]' in the SEP sesam '''Defaults''' table.

<!--T:145-->
As the available Chinese font sets depend on the operating system, the following platform specific keys are provided:</translate>

* Windows: 'default_font_windows'
* Linux: 'default_font_linux'
* Common setting: 'default_font'

<translate><!--T:146-->
Example to set 'MS Song' as 'default_font_windows':</translate>

 sm_db "INSERT INTO defaults (key,user_name,value,host,protection)
 VALUES ('default_font_windows','sesam','MS Song',NULL,NULL);"
<!-- obsolete=== Why can't I type anything into the GUI? ===
This may occur if Java 1.3 is installed. In this case, install SUN JRE Java version 1.4.2. After installation, the Java link must be changed. In the <tt><SESAM_ROOT>/bin/sesam</tt> directory the Java link still refers to the old Java path. Change it to the new Java version and restart the server portion of the SEP sesam GUI by entering:

 ./sm_main reload rmi

With SLES9, Unicode became the standard character setting/coding for SuSE Linux. All SEP sesam versions for SLES9 and higher are in Unicode. Reset you system to Unicode or install a new toolkit. -->
<translate>=== {{anchor|server administration}}Can I administer more than one SEP sesam Server via the GUI? === <!--T:149-->

<!--T:150-->
To administrate more that one SEP sesam Server, enable the ''Master GUI'' functionality.

<!--T:151-->
'''Configuration'''
* '''Important!''' All SEP sesam Servers must be of the same version to use this functionality!
* No special license is required.
* Use the switch '''-M1''' to enable this function.

<!--T:152-->
On a Windows system, edit the SEP sesam desktop shortcut and add the parameter '''-M1''' to the target:</translate>

 "C:\Program Files\Java\jre6\bin\java.exe" -classpath sm_gui.jar;sm_lib.jar;
 de.sep.sesam.gui.client.Frame -ucr -sbackupserver -lwindows -p11401 -P local -v2 -ren -M1

<translate><!--T:153-->
On a Linux system, start the GUI executable <tt>/opt/sesam/bin/gui/sesam_gui</tt> with the parameter '''-M1''':</translate>

 ./opt/sesam/bin/gui/sesam_gui -M1

<translate>== {{anchor|network}}NETWORK== <!--T:154-->

=== {{anchor|client full access}}How can I verify that the SEP sesam server has full access to a specific client? === <!--T:1190-->                  

<!--T:156-->
Even if you can reach a client from the SEP sesam Server with [http://en.wikipedia.org/wiki/Nslookup nslookup] and [http://en.wikipedia.org/wiki/Ping ping]over DNS names, it is still possible that the SEP sesam Server cannot connect to the client. In this case, check the availability of the client from the SEP sesam Server with the following command:

<!--T:157-->
'''For Linux/UNIX client:'''</translate>

 sm_ctrlc -l root {nameofclient} sbc

 sm_ssh -l root {nameofclient} sbc

<translate><!--T:158-->
'''For Windows client:'''</translate>

 sm_ctrlc -l system {nameofclient} sbc

 sm_ssh -l system {nameofclient} sbc


<translate><!--T:159-->
The output should be similar to the following standard output of the sbc command (example for a Linux client):</translate>

   smsrv:~ # sm_ctrlc -l root dbsrv.local sbc
 2016-11-22 13:11:44: sbc-3036: Info:     # @(#)SESAM BACKUP CLIENT FOR UNIX FILE SYSTEMS, VERSION: 4.4R3 Build: 3ed0977 20161122 11:34:51 Linux x86_64 sles11fix #
 2016-11-22 13:11:44: sbc-3162: Info:     Client Host name: buildfix11
 2016-11-22 13:11:44: sbc-3253: Info:     Sesam version: [server,4.4.3.24,20161122114206]
 2016-11-22 13:11:44: sbc-3257: Info:     Sesam package: [sesam_srv-4.4.3-24_pg.sles11.x86_64.rpm]
 2016-11-22 13:11:44: sbc-3019: Info:     OS info:          SUSE Linux Enterprise Server 11 (x86_64)
 2016-11-22 13:11:44: sbc-3000: Info:
 
 usage:
  sbc -b|r|g|p|k|h   [-C <control_host>] [-d <device>] [-f <list_source>]
           [-F <data_format>] [-i <saveset_info>] [-j <job_name>]
           [-l <level>] [-L <control_target>] [-n <segment_number>]
           [-o {options}] [-O <STOR/RETR_direct>]
           [-R <restore_target>] [-s <saveset_spec>][-S <storage_node>]
           [-t <tape_spec>] [-T <since_time>][-x <exclude_patterns>]
           [-X <exclude list>] [-v <level>] [-V <throughput_interval>]
 # Backup  #   [<backup_source1>[ <backup_source2> <backup_sourceN>]] |
 # Restore #   [<restore_source1>[ <restore_source2> <restore_sourceN>]] |
 # Get     #   [<remote_file> [<local_file>]] |
 # Put     #   [<local_file> [<remote_file>]]
 {options}: comma separated list of
                      compress, encrypt[_plain]=[{aes}|{bf}]<passwd>
                      noacl                 # process without ACL (Trustees)
  only for backup:    verify                # verify data after backup
                      plain                 # do not descend into subdirectories
                      hard=defer            # defer hardlinks
                      hard=sort             # expect i-node sorted input
                      ignore_finderr        # ignore errors from sbc_find
  only for restore:   rename, overwrite     # rename/overwrite if file exists
                      over=new, over=old    # overwrites newer/older files
                      plain, tree           # restore plain/tree in target dir
                      next                  # start from subsequent tape
 2016-11-22 13:11:44: sbc-3001: Info:     Exiting.

<translate><!--T:160-->
When a network problem occurs, the output may look like:</translate>

   2007-10-26 13:25:59: scc-1128: Error: Network communication problem: STDLIB
   error: 110 - Connection timed out. connect() call failed for host:
   [dbsrv.sep.de].

<translate><!--T:161-->
Or a connection from SEP sesam Server to the SEP sesam Client may be forbidden:</translate>

   2007-10-26 13:28:29: scc-1128: Error: Network communication problem: CTRLD
   reply: 2007-10-26 13:37:55: scd-1136: Error: Host [smsrv.local] is not
   allowed to connect or security problem for user: [root].

<translate>=== {{anchor|TCPIP_ports}}Which are SEP sesam default TCP ports? === <!--T:1229--> 

<!--T:1230-->
SEP sesam client-server communication requires certain TCP ports to be open to enable SEP sesam components to communicate with each other through a firewall. The required ports may be SEP sesam version-specific; as of version ≥ [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|4.4.3 ''Beefalo'']] SEP sesam uses fewer ports than in the previous versions. For the complete list of SEP sesam ports and their configuration, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].

=== {{anchor|network communication error}}Why do I get the error: "Network communication problem: SOCKET error: 10038 – The descriptor is not a socket" when I try to connect to a client?=== <!--T:602-->

<!--T:186-->
The Layered Service Provider (LSP) chain is defective or damaged. The cause can be an antivirus program or a virus. Another option is that the DLLs were switched during installation or uninstallation. This results in sub-processes not being able to inherit/open your socket handles.

<!--T:187-->
In this example, the SEP sesam CTRL connection takes the SM_CTRLD_MAIN daemon call from SM_CTRLC, opens the necessary sockets and passes them onto the newly created sub-process SM_CTRLD. Due to the defective LSP, the sockets cannot use this information and return the following error during an operation such as setsockopt():

 <!--T:188-->
10038 – The descriptor is not a socket.

<!--T:189-->
Use the following free tools on the SEP sesam Client:
 * lspfix.exe – identifies blocked DLL's, for example, bmnet.dll and removes them
 * listdlls.exe – checks the chain of DLLs (alternatively use sm_list -f {PID of SM_CTRLD_MAIN})

<!--T:190-->
Corrective measures:

<!--T:191-->
# Check if the Layered Service Provider (LSP) links with lspfix.
# Check the sm_ctrld[_main].exe indirectly used DLLs with listdlls.
# Remove the conflicting DLL with lspfix.

<!--T:192-->
An example of a correct listdlls for an environment:</translate>

       #> listdlls.exe sm_ctrld
       D:\kit\su\src\gui>listdlls sm_ctrld
       .
       ListDLLs v2.25 - DLL lister for Win9x/NT
       Copyright (C) 1997-2004 Mark Russinovich
       Sysinternals
       ------------------------------------------------------------------------------
       sm_ctrld_main.exe pid: 4872
       Command line: D:\programme\SEPsesam\bin\sesam\sm_ctrld_main.exe -D
       .
       Base Size Version Path
       0x00400000 0x23000
       D:\programme\SEPsesam\bin\sesam\sm_ctrld_main.exe
       0x7c910000 0xb7000 5.01.2600.2180 D:\WINDOWS\system32\ntdll.dll
       0x7c800000 0x106000 5.01.2600.2945 D:\WINDOWS\system32\kernel32.dll
       0x71a10000 0x17000 5.01.2600.2180 D:\WINDOWS\system32\WS2_32.dll
       0x77be0000 0x58000 7.00.2600.2180 D:\WINDOWS\system32\msvcrt.dll
       0x71a00000 0x8000 5.01.2600.2180 D:\WINDOWS\system32\WS2HELP.dll
       0x77da0000 0xaa000 5.01.2600.2180 D:\WINDOWS\system32\ADVAPI32.dll
       0x77e50000 0x91000 5.01.2600.2180 D:\WINDOWS\system32\RPCRT4.dll
       0x719b0000 0x40000 5.01.2600.2180 D:\WINDOWS\system32\mswsock.dll
       0x66710000 0x59000 5.01.2600.2180 D:\WINDOWS\system32\hnetcfg.dll
       0x77ef0000 0x47000 5.01.2600.3099 D:\WINDOWS\system32\GDI32.dll
       0x7e360000 0x90000 5.01.2600.3099 D:\WINDOWS\system32\USER32.dll
       0x719f0000 0x8000 5.01.2600.2180 D:\WINDOWS\System32\wshtcpip.dll

<translate><!--T:193-->
After removing the defective DLL, the socket can be inherited by the sub-process SM_CTRLD.

=== {{anchor|loopback_mtu_size}}Why is the throughput for local backups very low? === <!--T:866-->

<!--T:867-->
In some Linux systems, e.g., SLES 12, the local loopback device lo is often configured with MTU (Maximum Transmission Unit) size 65536 (64K).
This may decrease the local transfer throughput because the MTU size is equal to the transfer buffer size used in SEP sesam.

<!--T:868-->
Proceed as follows to check and modify the MTU size for local loopback:
# To check the local loopback MTU size: ''ifconfig lo''
# To set the MTU size to 16K: ''ifconfig lo mtu 16384''
# Add or change MTU='16384' in ''/etc/sysconfig/network/ifcfg-lo'' for SLES12

<!--T:869-->
Example:</translate>

  srv1:/ # ifconfig lo
 lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:61869492 errors:0 dropped:0 overruns:0 frame:0
           TX packets:61869492 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:5001500685 (4769.8 Mb)  TX bytes:5001500685 (4769.8 Mb)
  srv1:/ # ifconfig lo mtu 16384
  srv1:/ # grep MTU ifcfg-lo /etc/sysconfig/network/ifcfg-lo
  srv1:/ # echo MTU=16384 >> /etc/sysconfig/network/ifcfg-lo

<translate><!--T:870-->
See also: 
* [https://www.suse.com/communities/blog/sles-1112-network-cpu-tuning-optimization-part-2/ SUSE blog: Network, CPU Tuning and Optimization]
* [https://www.cyberciti.biz/faq/centos-rhel-redhat-fedora-debian-linux-mtu-size/ nixCraft article: Linux MTU Change Size]

== {{anchor|SEP sesam specific}}SEP SESAM SPECIFIC== <!--T:194-->

=== {{anchor|SEP sesam newday}}What is SEP sesam ''Newday''? === <!--T:1191-->                  

<!--T:196-->
SEP sesam ''Newday'' is a predefined SEP sesam daily event that resets the backup event calendar and is managed by  [[Special:MyLanguage/SEP_sesam_Glossary#SEPuler|SEPuler]]. A Newday event is used by SEP sesam to reorder its database and enable uninterrupted activity of SEP sesam processes, therefore it must never be completely deactivated or it will cause SEP sesam to stop working properly. It also gives system administrators the flexibility to extend backup routines to run after midnight and retain the backup date of the prior day. This is very useful when the clients requiring backup exceed the time allotment between the end of day and midnight. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Newday_Event|Newday Event]].  

=== {{anchor|services overview}}Is there an overview of SEP sesam services?=== <!--T:1192-->                  

<!--T:203-->
There are different services depending on whether you are dealing with a SEP sesam Server, a SEP sesam Client or a SEP sesam Remote Device Server. 

<!--T:204-->
The services can be found in the SEP sesam installation directory {{Sesamroot|/bin/sesam}}. To check the status of the services, use the following commands:

<!--T:205-->
* Linux/UNIX:</translate>

 ./sm_main status

<translate><!--T:206-->
* Windows:</translate>

 sm_main status

<translate><!--T:207-->
'''SEP sesam Server services'''

 <!--T:208-->
sm_qm_main   SEP sesam main processes, provides also the qm service
 sepuler      SEP event calendar to control all tasks
 db           SEP sesam databank services
 qm           Queue Manager, administers backups, restores and devices
 rmi          server part of the graphical user interface
 sms          read/write of SEP sesam media
 stpd         linking protocol from the SEP sesam Client to the SEP sesam Server
 passd        security administration for SEP sesam
 ctrl         linking protocol from the SEP sesam Server to the SEP sesam Client
 sshd         secure linking protocol from the SEP sesam Server to the SEP sesam Client

<!--T:209-->
'''SEP sesam Client services'''

 <!--T:210-->
sm_qm_main    SEP sesam main processes
 ctrl          linking protocol from the SEP sesam Server to the SEP sesam Client
 sshd         secure linking protocol from the SEP sesam Server to the SEP sesam Client

<!--T:211-->
'''SEP sesam Remote Device Server services'''

 <!--T:212-->
sm_qm_main    SEP sesam main processes
 ctrl    linking protocol from the SEP sesam Server to the SEP sesam Client
 sms     read/write of SEP sesam Media
 stpd    linking protocol from the SEP sesam Client to the SEP sesam Server
 passd   security administration for SEP sesam
 sshd         secure linking protocol from the SEP sesam Server to the SEP sesam Client</translate>

<translate>=== {{anchor|backup by state}}In ''Backups by state'', what do the flags in the column ''type'' mean? === <!--T:605-->

<!--T:214-->
The first letter shows the type of backup:

 <!--T:215-->
F/D/I/C:  Backup level (full, differential, incremental, copy)
 M:        Media event
 N:        SEP sesam NEWDAY
 S:        SEP sesam startup
 X:        SEP sesam command event

<!--T:216-->
The second letter is used when a database backup is performed. It has no significance for regular path backups.

 <!--T:217-->
 H:  Hot - online backup of a database
 C:  Cold - offline backup of a database</translate>

<translate>=== {{anchor|profile setting}}What happens when I set a profile? === <!--T:607-->

<!--T:231-->
By setting a profile:
* the {{Sesamroot|/bin}} and {{Sesamroot|/var/db/}} directories (and their subdirectories) are added to the "<tt>$PATH</tt>" environment variable so that SEP sesam commands can be executed globally,
* you do not need to be in the actual "run directory".

<!--T:232-->
Set the profile as follows:

<!--T:233-->
'''Linux/UNIX'''

<!--T:234-->
Go to the directory {{Path|<SESAM_VAR>/var/ini}} and call:</translate>

 . sesam2000.profile

<translate><!--T:235-->
'''Important!''' Do not forget the '''dot''' and the '''space'''!

<!--T:236-->
Alternatively, use:
 source sesam2000.profile

<!--T:237-->
{{Box Hint|Note|This sets the profile only for the current session. To set it permanently under Linux, see [[Special:MyLanguage/FAQ#profile configuration | How do I configure SEP sesam profile to run automatically during login?]]}}</translate>

<translate><!--T:238-->
'''Microsoft Windows'''

<!--T:239-->
Open a command window, then go to the directory {{Sesamroot|\var\ini}} and call:</translate>

 sm_prof.bat

<translate><!--T:240-->
Alternatively, use the link {{Sesamroot|\var\ini\sm_prof.bat.lnk}}</translate>

<translate>=== {{anchor|JAVA processes}}Why does the SEP sesam GUI create so many Java processes under Linux? === <!--T:608-->

<!--T:242-->
On some Linux Systems, the [http://en.wikipedia.org/wiki/Thread_%28computer_science%29#Programming_Language_Support threads] created by the SEP sesam GUI are shown in the process table. These are not real processes but only threads. There is a large number of processes because Java creates threads for all objects with ''Listener'' functionality.

=== {{anchor|disk space}}Why does SEP sesam Server use so much disk space on the local hard disk? === <!--T:243-->
One of the essential advantages of SEP sesam is that not all information is filed in a database but, instead, in simple text files. The largest files are usually the <tt>''*.lis''</tt> files which contain information about the backup's unique files and are used by the restore wizard to select and restore unique files. <tt>''*.lis''</tt> files are stored in the following directories:

<!--T:244-->
'''Linux/UNIX:'''</translate>

 /<SESAM_ROOT>/var/lis

<translate><!--T:245-->
'''Microsoft Windows:'''</translate>

 C:\<SESAM_ROOT>\var\lis

<translate><!--T:246-->
SEP sesam can compress <tt>''*.lis''</tt> files automatically. See [[Admin_Manual#Compressing_SEP_sesam_Listing_files|Compressing SEP sesam Listing Files]].

<!--T:247-->
Before compressing the files, set the SEP sesam profile as follows:</translate> 

'''Linux/UNIX:'''

  source /var/opt/sesam/var/ini/sesam2000.profile
 
'''Microsoft Windows:'''  

  C:\<SESAM_ROOT>\var\ini\sm_prof.bat

<translate><!--T:248-->
Use the "<tt>sm_newday</tt>" command to run file compression immediately. The files will be compressed directly by the NEWDAY schedule.

<!--T:249-->
As predefined in the command, ''*.lis'' files are not compressed immediately but three days after they are created. This is because most restores are triggered within three days after a backup.

<!--T:250-->
All <tt>''*.lis''</tt> files are converted into a compressed file format and are uncompressed by SEP sesam automatically whenever necessary.</translate>

<translate>== {{anchor|backup_overview}}BACKUP (general overview)== <!--T:251-->
=== {{anchor|data store}}Is data that is collected for backup stored in a flat file or a database? ===

<!--T:252-->
Data is stored in a flat file but information about the backup is stored in the SEP sesam database, including index pointers for fast and easy data recovery.

=== {{anchor|open files backup}}Does SEP sesam back up open files?=== <!--T:1193-->                  

<!--T:254-->
Yes, SEP sesam can back up open files on both Linux and Microsoft Windows.

<!--T:255-->
'''Microsoft Windows'''

<!--T:256-->
Open files can be backed up with Microsoft's Volume Shadow Copy Service. To perform an open file backup, a Windows snapshot is made of the data and partition intended for backup and the partition is backed up. Databases should be backed up using the relevant SEP sesam database module.

<!--T:257-->
System requirements:

<!--T:258-->
* Client O/S: Microsoft Windows 2003
* SEP sesam Server Version 3.0 or higher
* SEP sesam Client Version 3.0 or higher</translate>

<translate>=== {{anchor|backup type performance}}Does SEP sesam perform incremental backups after the initial backup? === <!--T:259-->

<!--T:260-->
Depending on your backup strategy, SEP sesam can be set to perform any [[Special:MyLanguage/SEP_sesam_Glossary#backup_level|backup level]] in the desired sequence.{{:Backup Level/en}}

=== {{anchor|backup performance}}Are backups performed directly to disk or tape?=== <!--T:261-->

<!--T:262-->
Backups can be written directly to either tape or disk. SEP sesam version supports disk-to-disk-to-tape (D2D2T) functionality. Additionally, it can write directly from the backup tape to the server. This is beneficial and saves a lot of time when performing a disaster recovery.

<!--T:263-->
All backup functions are written and/or controlled by the server and may be written directly to the backup disk, tape or remote tape server. SEP sesam supports virtual tape libraries on disk with a pseudo autoloader function. Removable disk media are also supported.

=== {{anchor|files backup}}When several users save the same file on separate clients, does SEP sesam backup all the files? === <!--T:264-->

<!--T:265-->
For example, if members of a workgroup save the same file to their respective desktops, does SEP sesam make separate copies of the file or a single file with pointers to the changes?

<!--T:266-->
Typically, SEP sesam stores separate files for each user, unless you are using the '''SEP Si3 target deduplication'''.  With SEP Si3 target deduplication only one instance of the same data is stored directly on backup media. Si3 deduplication can be easily configured, but it also requires a special license. For explanation, see [[Special:MyLanguage/SEP sesam Glossary#SEP Si3|SEP Si3 target deduplication]] and [[Special:MyLanguage/SEP sesam Glossary#SEP sesam extensions|SEP sesam extensions]].

==={{anchor|initial_seed}}How to set up an Si3 deduplication store for replication?=== <!--T:976-->
The easiest way is to use the initial seed functionality - you can import the preconfigured Si3 deduplication store and use it for the purpose of replication. When replicating from origin to new Si3 store, the save sets on the new Si3 deduplication store are recognized and the content of the new Si3 store is updated in the SEP sesam database. For details, see [[Special:MyLanguage/Seeding_Si3_Deduplication_Store|Seeding Si3 Deduplication Store]].

=== {{anchor|archive bits}}How are archive bits processed?=== <!--T:267-->

<!--T:268-->
As of SEP sesam version 3.4.1.67, archive bits are no longer used for incremental and differential backups on Microsoft Windows. This can be changed if necessary.</translate>

{| WIDTH= "95%" style= "background-color: #E0E0FF; border: solid 2px #A0A0FF;"
|-
|
<translate><!--T:269-->
'''Note:'''
As of SEP sesam version 4.2.1, file system backups on Microsoft Windows are always executed as a backup level COPY. Two new options were introduced:</translate>

* "-o add_archive_ready" to add files with the ''Archive ready'' attribute
* "-o clear_archive" to reset the ''Archive ready'' attribute.

<translate><!--T:270-->
If "with_archive_bit" is set to the value 'yes', then all FULL/DIFF/INCR backups will be executed as COPY. The following are additional options:</translate>

* FULL: -o clear_archive
* DIFF: -T {since_last_full} -o add_archive_ready
* INCR: -T {since_last_backup} -o add_archive_ready,clear_archive
|}

<translate><!--T:271-->
You can set the use of archive bits with the command:</translate>

 sql "update defaults set value= 'yes' where key= 'with_archive_bit'"

<translate><!--T:272-->
After setting the value to 'yes', the Windows archive bits are treated as follows, depending on the [[Special:MyLanguage/SEP_sesam_Glossary#backup_level|backup level]]:

<!--T:273-->
;COPY: Saves all files without regard to the archive bit, archive bit is not reset.
;FULL: Saves all files without regard to the archive bit, resets archive bit.
;DIFF: Only files with archive bit are saved, archive bit is not reset.
;INCR: Only files with archive bit are saved, resets archive bit.

<!--T:274-->
The following issues must be considered when selecting a backup strategy:

<!--T:275-->
# A backup sequence FULL-DIFF-INCR-DIFF... is not logical. Following an INCR backup with a DIFF will not save files saved by the INCR backup because the archive bit is reset!
#If the file archive bits are reset manually or by other programs, a following DIFF or INCR backup may not save the files!
#If archive bits are not changeable, for example, if they cannot be reset because they are in ''Read only'' directories, warnings will be returned during FULL and INCR backups.</translate>

<translate>=== {{anchor|VSS functionality}}Can I back up MS SQL/MS Exchange with the Volume Shadow Copy (VSS) functionality of Microsoft Windows? === <!--T:610-->

<!--T:277-->
Yes, the VSS functionality can be used to back up MS SQL or MS Exchange environments but it is only recommended for small installations.

<!--T:278-->
There are two strategies for consistently backing up a running MS Exchange or MS SQL environment:
# Using the SEP sesam online extensions for MS Exchange or MS SQL. For details, see [[Special:MyLanguage/4_4_3_Grolar:Exchange_Backup|MS Exchange Backup]] and [[Special:MyLanguage/4_4_3:MS_SQL_Backup|MS SQL Backup]].
# A regular file system ''path'' backup with the activated VSS writer for MS Exchange or MS SQL. For details, see [[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows|SEP sesam Volume Shadow Copy Service (VSS) for Windows]].

<!--T:279-->
'''SEP sesam online extensions'''

<!--T:280-->
* Dedicated backup of Groupware data/database data, independent of the files in the file system.
* Available are FULL, DIFF (differential) and INCR (incremental) backup levels.
* Provide granular backup of single databases and database instances.
* Backup of the transaction log – other systems accessing the database are aware that a backup is performed.
* Restore of the database/Groupware data only (without files from the file system)
* Provide granular restore of single instances and databases. In a restore scenario, there is no need to restore the complete database – this is beneficial for larger databases/Groupware systems.
* Perform online restore.

<!--T:281-->
'''Backup via the Microsoft VSS Writer'''

<!--T:282-->
* The Volume Shadow Copy (VSS) functionality of Microsoft Windows is included in the regular SEP sesam file backup agent for Microsoft Windows. It also supports the VSS backup of MS Exchange and MS SQL.
* A VSS-based backup of a database/Groupware system is always a file system backup. If the file backup agent starts backing up a file system with a MS SQL / MS Exchange database, the VSS functionality is used to inform the database about the backup. The database/Groupware system delivers the data consistently.
* A VSS backup of a database/Groupware system always backs up all of the data. Incremental or differential backups are not supported and the backup of single databases or single instances is also not supported.
* A database-only restore cannot be performed because the database/Groupware system is part of the complete file system backup, therefore the complete file system backup must be restored in order to restore the database.
* Restore of single instances or single databases is not supported.
* The transaction log file is not backed up – other applications are not informed about the backup of the database.

<!--T:283-->
To enable a consistent restore in distributed environments, the different components must be informed if a backup of one of the systems is performed. For example, in a SharePoint Server environment, the database and mail server run on different servers. A VSS backup of a single server will result in an inconsistent restore. In this case, only the backup with the SEP sesam dedicated online extension can guarantee consistent data.

<!--T:284-->
In summary, the backup of MS Exchange or MS SQL environments via VSS is a viable option to get a consistent backup of the running environment as long as the data volume is not too large. It is an alternative for small environments with 1-5 users. In critical productive environments, the use of the SEP sesam online extensions for MS Exchange/MS SQL is highly recommended.</translate>

<translate>=== {{anchor|Groupwise backup}}What is the difference between a Groupwise backup with the SEP sesam online extension and one without the extension on an OES Server? === <!--T:611-->

<!--T:286-->
There are two ways to back up a Micro Focus (formerly Novell) Groupwise Server with SEP sesam. You can use the SEP sesam Groupwise extension or the administrator can perform a TSA based file-level backup of the Groupwise Server.

<!--T:287-->
In general, the backup of a Groupwise Server is always performed via TSA interface, either via <tt>tsafsgw</tt> or <tt>tsafs</tt> (gw-enabled). There is no difference between the two backup options. The difference is in the management of the backup and restore jobs.

<!--T:288-->
To find out more about SEP sesam's backup in a Micro Focus (formerly Novell) Netware/OES environment, read [[Backup_principles_using_SEP_sesam_in_a_Micro _Focus_OES_environment|Backup principles using SEP sesam in a Micro Focus OES environment]].

<!--T:289-->
For file-based backup and restore, you will need qualified knowledge of the Groupwise environment and the management of Groupwise systems. With the SEP sesam Groupwise online extension, the backup and – more importantly – restore of Groupwise systems can be performed by an administrator without any knowledge of the Groupwise environment.

<!--T:290-->
'''Backup with SEP sesam Groupwise extension'''

<!--T:291-->
When a new backup job is being defined for a client, the SEP sesam extension automatically recognizes that Groupwise is running on the client and offers the administrator a Groupwise backup. The administrator does not need to know where the Groupwise data is stored or which files are to be backed up.

<!--T:292-->
The backup is started as a Groupwise backup process and is clearly identified as such. The SEP sesam Server recognizes that this is a Groupwise backup and not a normal file backup. This makes management and problem location (in the event of a problem) much easier. Technically, it is only a file backup but the SEP sesam agent ensures that the right files are backed up from the right directories.

<!--T:293-->
The scenario for a restore is similar. The SEP sesam Groupwise extension recognizes the backup (technically a file backup) and is aware that all the files belong together to a Groupwise system. The SEP agent then restores all the relevant files to the Groupwise restore area on the Groupwise Server. Based on the data in the Groupwise restore area, Groupwise can start a recovery process to restore the data (mail or mailboxes). The administrator does not need to know which files need to be restored or where they should be restored to.

<!--T:294-->
'''Backup without SEP sesam Groupwise extension'''

<!--T:295-->
Backing up a Groupwise system without the SEP sesam Groupwise extension is performed much like a regular file backup. Groupwise is shown as a regular NSS volume in the file system with its volume name. The administrator needs to know:
* which is the Groupwise volume
* which files within the volume need to be backed up

<!--T:296-->
The backup process itself starts as a file backup process. For the restore, the administrator needs to know:
* which files need to be restored
* the location of the Groupwise restore directory</translate>

<translate>== {{anchor|backup configuration}}BACKUP CONFIGURATION== <!--T:297-->
=== {{anchor|UNC path backup}}How do I set up a UNC path backup from a CIFS share? ===

<!--T:298-->
This example assumes that the SEP sesam Server or the SEP sesam Client is on a Microsoft Windows system. Not all rights of the backed up files and ACLs are considered. For a NetApp CIFS share backup, see [[NetApp-CIFS-Backup|NetApp CIFS backup]].

<!--T:299-->
In Microsoft Windows, services – and therefore the SEP sesam processes – usually run under the special SYSTEM account. This account has all local access rights but, for security reasons, no access rights for non-local or network drives. To access network drives, the following configurations must be modified:

<!--T:300-->
* For SEP sesam Clients to which the backup task is assigned, the SEP sesam service should run under an administrator account (services.msc -> SEP sesam Server-> logon under an administrator account) with full read and write privileges for the network drive.
* Share the network drive in such a way that it is not necessary to login for read and write privileges. This can be tested by opening the shared path on the SEP sesam Server in Windows Explorer. If the content of the share is displayed without a user and password request, the UNC path can be used as a source for the backup task.

<!--T:301-->
Because of the enhanced security introduced after Microsoft Windows 2000, you cannot assign a dedicated drive letter (for example, <tt>e:\</tt>). Instead, the path must be entered using UNC notation. The backup is performed over the UNC names, for example, {{Path|//fileserver/install/Driver}}.

<!--T:302-->
The image below is an example of a backup task configured in SEP sesam GUI:

<!--T:303-->
[[Image:NetApp_CIFS_4.4.3.jpg|link=]]

<!--T:304-->
{{Attention Box|Attention|The '''VSS''' option must be disabled when backing up UNC paths. You can only use one path for each task.
}}

<!--T:305-->
'''Testing with the command line'''

<!--T:306-->
The SEP sesam service must be running under an administrator account. In the command line, enter the following for a backup:</translate>

 C:\Programme\SEPsesam\bin\gui>sm_ctrlc -l system rmpc1(hostname of the system) sbc -b -s @test.save
 -v 2 \\fileserver\pub\customers

<translate><!--T:307-->
For a restore command, enter:</translate>

 C:\Programme\SEPsesam\bin\gui>sm_ctrlc -l system rmpc1(hostname of the system) sbc -r -s @test.save
 -v 2 -R \\fileserver\pub\customers_restore

<translate><!--T:308-->
This saves the files from {{Path|\pub\customers}} to the file (save set) <tt>test.save</tt>, i.e., it restores them from the saveset <tt>test.save</tt> to the folder {{Path|\pub\customers_restore}}.

<!--T:309-->
'''Excluding a UNC directory'''

<!--T:310-->
The excluded UNC path in this example is: <tt>\\server\share\subfolder1\subfolder2</tt>. 

<!--T:311-->
* UNC path exclude syntax using ''/ (slash)'' is: <tt>//server/share/subfolder1/subfolder2</tt>.
* UNC path exclude syntax using ''\ (backslash)'' (works from version 4.2.1.41) is: <tt>\\\\server\\\share\\\subfolder1\\\subfolder2</tt>.</translate>

<translate>=== {{anchor|new interface}}How can I configure a backup using another network or interface? === <!--T:612-->

<!--T:313-->
You must first establish an IP address for the new interface. The IP address is then automatically entered to the properties table of the SEP sesam Remote Device Server under '''Components''' -> '''Topology''' -> '''Clients''', field '''Interfaces'''. In the backup events, the IP name must be selected from the '''Parameter''' tab in the field '''Interfaces'''.

<!--T:314-->
For example, the computer "testme" has a 2nd interface module with the name "testmeb". In the backup task properties, select "testmeb" in the '''Interfaces''' field.

===  {{anchor|backup source}}How can I enter a backup source with more than 256 characters? === <!--T:316-->
If you want to define a backup source with more than 256 characters in the complete filename (path and filename), create a text file with a list of all the paths as the backup source (for example, /opt/sesam/var/ini/large_source.txt). Each path must be written below the previous one, resulting in a fully qualified file or directory name on each line.

<!--T:317-->
Enter the backup option -f {file} in the '''backup task properties''' -> tab '''Options''' -> '''Backup options''' (previously ''Save options''):</translate>

 -f /opt/sesam/var/ini/large_source.txt

<translate><!--T:318-->
The SEP sesam Server reads this file during backup and stores the additional files and directories listed in the source directories.

===  {{anchor|creation modification time}}How do I get backups to ignore archive bits and use creation/modification time?=== <!--T:1194-->                  

<!--T:320-->
As of SEP sesam version 3.4.1.67, ''archive bits'' are not used for incremental and differential backups on Microsoft Windows.

<!--T:321-->
To set the use of creation/modification time, go to the <SESAM_ROOT>/bin/sesam directory and call:</translate>

 sm_db "INSERT INTO defaults (key,user_name,value) VALUES ('with_archive_bit','sesam','no');"

<translate><!--T:322-->
FULL, DIFF and INCR backups will now ignore archive bits. DIFF and INCR backups use the start time of the last referenced backup – for DIFF, the preceding FULL backup and for INCR, any preceding backup.

<!--T:323-->
The option below executes optional resetting of archive bits when it is inserted in the backup task properties in the '''Options''' tab of the '''Backup options''' (previously ''Save options'') field:</translate>

 -o clear_archive

<translate>=== {{anchor|backup_to_disk}}How do I set up a backup to disk?=== <!--T:615-->

<!--T:325-->
SEP sesam uses  a data store to back up data directly on one or several configured storage locations. The default data store type is ''Path'', also available are ''SEP Si3 deduplication store'' and (depending on version) ''NetApp Snap Store'', ''HPE StoreOnce'' and ''HPE Cloud Bank Store''.

<!--T:1231-->
Data stores are easily configured. Note that prerequisites differ depending on the selected data store type. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Data_Store|Data Store Overview]].

===  {{anchor|cluster}}How do I perform a file backup of a Linux/Windows cluster? === <!--T:1195-->                  

<!--T:330-->
To perform a file backup of a Linux/Windows cluster:

<!--T:331-->
# Install the standard SEP sesam Client on each physical node.
# Check if every node and every resource of the cluster can be correctly resolved using DNS forward and reverse lookup.
# Add each physical node and each cluster resource as a backup client under '''Components''' -> '''Topology'''.
# After the clients have been successfully recorded, a backup task can be created for each cluster resource. During backup, the data is automatically transferred from the active node.

===  {{anchor|exclude directory}}How can I exclude a directory from a backup? === <!--T:1196-->                  

<!--T:333-->
You can exclude a directory by creating a special file – ''.nosbc'' (UNIX) or ''nosbc'' (Windows) in the directory itself. The behavior can be switched off for a specific backup task by entering the ''-o noexcl'' switch under the '''backup task properties''', tab '''Options''' -> '''Backup options''' (previously ''Save options'').

===  {{anchor|exclude VSS writers}}Can I exclude specific VSS writers from a backup? === <!--T:1232-->
Yes, it is possible to manually exclude a VSS writer from the backup. For details, see [[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows#exclude|Manually excluding a VSS writer from backup]].

===  {{anchor|exclude list}}How can I specify an exclude list that is longer than 150 characters?=== <!--T:336-->

<!--T:337-->
Create a text file where all the paths are listed one below the other (for example, {{path|/opt/sesam/var/ini/large_exclude.txt}}) and save this file to a folder of your choice. During the creation of a backup, enter the folowing statement.</translate>

 -X /example/directory/text file.txt

<translate><!--T:338-->
Example for a Linux client:</translate>

   -X /opt/sesam/var/ini/large_exclude.txt

<translate><!--T:339-->
Example for a Windows client:</translate>

   -X "C:\Program Files\SEPsesam\var\ini\large_exclude.txt"

<translate><!--T:340-->
During backup, all directories in the .txt file will also be excluded.

<!--T:341-->
[[Image:File_exclude_4.4.3.png|link=]]

<!--T:342-->
See also [[Special:MyLanguage/FAQ#SBC|How can I set the SBC so that the exclude list always uses the file pattern (?,*) instead of using regular expressions?]].</translate>

<translate>===  {{anchor|incl-excl_files}}How do I include or exclude a large number of files/folders for backup? How do I use a file for in- or exclude of files/folders?=== <!--T:343-->
If several directories or files are to be included in or excluded from a backup task, you can exceed the character count limit of the field:
*SEP sesam version ≥ 4.4.3: max. 1024 characters
*SEP sesam version ≤ 4.4.2: max. 255 characters

<!--T:801-->
Use a file to define a backup source or an exclude list. This file must be created on the backup client on which the backup will be executed.

====Include list==== <!--T:344-->
Note that an include list, introduced by option -f, behaves differently on different platforms.</translate>
<translate><!--T:802-->
;On Windows:The <tt>-f <list_source></tt> option overrides the backup source specified in the [[Special:MyLanguage/Creating_a_Backup_Task|backup task]]. For example, creating a backup task with source ''g:\x'' and specifying an SBC option <code> -f C:/sesam/backup_file_list.txt</code>  will back up only the data from the ''backup_file_list.txt'' while ignoring the directory ''g:\x'', which was specified as a backup source.</translate>
<translate>
<!--T:803-->
;On Unix/Linux:Both, the source and the data from the ''backup_file_list.txt'' are considered for backup. At least one item must be entered in the ''Source'' field. It is therefore recommended that the specified <list_source> file is specified as a source in the ''Source'' field (to be included in the backup set, for example, ''etc/sesam/backup_file_list.txt'') and entered again with a -f switch in the ''Backup options'' (previously ''Save options'') field: <code>-f C:/sesam/backup_file_list.txt</code>.

<!--T:345-->
When creating an include list, create a separate line for each directory or file item in a file (for example, <tt>/etc/sesam/backupfiles.txt</tt>):</translate>

  /lib
  /usr/share
  /usr/bin/a2ps
  /srv/Dos6.22.img
  /var/opt/sesam/var/ini

<translate><!--T:661-->
{| WIDTH= "95%" style= "background-color: #FFF0F0; border: solid 2px #DEB0B0;"
| style= "background-color: #DEB0B0;" | <font size= "-1"><b>Attention</b></font>
|-
|
Wildcards are not allowed in file or directory entries.
|}

====Exclude list==== <!--T:349-->

<!--T:350-->
The procedure for exclude is similar. The exclude file may be called <tt>/etc/sesam/excludefiles.txt</tt>, for example. Each file or directory that you want to exclude from the backup must be entered on a separate line in the file, for example:</translate>

  \./tmp$
  \./home/John Doe/videos.zip$
  \./home/John Doe/Business Documents/YearEnd Closing for business year 2006$

<translate><!--T:662-->
{| WIDTH="95%" style="background-color: #FFF0F0; border: solid 2px #DEB0B0;"
| style="background-color: #DEB0B0;" | <font size="-1"><b>Attention</b></font>
|-
|
The exclude entries have to be set up with a regular expressions syntax.
|}

<!--T:352-->
If, for instance, ''all'' is entered in the source of the task definition, the complete system is backed up, excluding the items in the exclude file. Leave the exclude list empty.

<!--T:353-->
Set up the following entry in the '''Backup options''' (previously ''Save options'') field of the '''Options''' tab in the backup task properties:</translate>

  -X /etc/sesam/excludefiles.txt

<translate><!--T:354-->
SEP sesam will exclude all listed files and directories from the backup.

===  {{anchor|exclude file}}How do I use an exclude file in Microsoft Windows? === <!--T:618-->

<!--T:356-->
To exclude several directories from a backup source, create a .txt file that contains all the directories you want to exclude from the backup. This file should be created on the computer that you want to backup. For example:

<!--T:357-->
Create the file {{path|exclude.txt}} on the client in the directory {{path|C:\Programme\SEPsesam\var\ini}}. The {{path|exclude.txt}} may, for example, contain the following:</translate>

  D:/DOWNLOAD
  D:/PREKITS
  D:/Dev
  D:/kit_2_3_1_7
  D:/kit_2_3_1_5
  D:/knoppix
  D:/ACHIM
  D:/gui

<translate><!--T:358-->
The backup task source is set to D:. In the backup task window, tab '''Options''' -> '''Backup options''' (previously ''Save options'') field, enter:</translate>

 -X C:\Programme\SEPsesam\var\ini\exclude.txt

<translate><!--T:359-->
'''IMPORTANT:'''
* Use only "/" (slash) in the exclude file and NOT "\" (backslash)!
* Every directory and file must be entered in a new line. This also applies to paths that contain spaces. Quotation marks (") must not be used in the in-/exclude lists.
* Known bug: in the SEP sesam version 4.3.1-69, you must use a double backslash (\\) instead of a single slash (/)!

<!--T:360-->
In this example, the entire drive D: is backed up except the directories that are listed in the <tt>exclude.txt</tt>.

===  {{anchor|SBC}}How can I set the SBC so that the exclude list always uses the file pattern (?,*) instead of using regular expressions?=== <!--T:1197-->                  

<!--T:362-->
In the configuration file <tt><SESAM_VAR>/var/ini/sm.ini</tt> on the SEP sesam Client, the entry</translate>

 [SBC_OPTIONS]
 EXCLUDE_MATCH= REGEXP

<translate><!--T:363-->
must be changed to</translate>

 EXCLUDE_MATCH= PATTERN

<translate>===  {{anchor|TSA based backup}}How do I exclude files and folders during a TSA based backup? === <!--T:620-->

<!--T:365-->
You can use the '''Exclude list''' field on the first – '''Task''' tab of the backup task. If several directories or files are to be excluded from a backup task, it may be possible that the count or character limit of the field (max. 255 character) will be exceeded. To solve this problem, use a file to define an exclude list. This file must be created on the backup client on which the backup is to be executed.</translate>

<translate><!--T:664-->
{| WIDTH= "95%" style= "background-color: #FFF0F0; border: solid 2px #DEB0B0;"
| style= "background-color: #DEB0B0;" | <font size= "-1"><b>Attention</b></font>
|-
|
Only a pattern format can be used for exclude. Wildcards are allowed in the file or directory entries. An exclude folder must end with a slash.
|}

<!--T:367-->
Create a separate line for each directory or file item in a file (for example, <tt>/etc/sesam/backupfiles.txt</tt>):</translate>

  /media/nss/VOL1/tmp/
  /media/nss/VOL1/USR/*/Notes/Workspace/
  /media/nss/VOL1/data/do_not_backup.txt

<translate><!--T:368-->
For instance, ''/media/nss/VOL1'' is entered in the source of the task definition. This means that the complete VOL1 is backed up, excluding the items in the exclude file. Next, set up the following entry in the '''Backup options''' (previously ''Save options'') field of the '''Options''' tab in the backup task definition:</translate>

  -X /etc/sesam/excludefiles.txt

<translate><!--T:369-->
SEP sesam will exclude all the files and directories from the backup that are listed in the file.

===  {{anchor|Novell OES Linux}}How do I back up the eDirectory on Novell OES2 Linux without SP2? === <!--T:1198-->                  

<!--T:371-->
Starting with OES2 SP2, a TSA-NDS (Target Service Agent – NetWare Service Directory) is available for eDirectory on Novell OES Linux. Note that it is recommended to update to SP2. A special [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]] called ''OES Novell Directory'' is only provided for OES2 without SP2. This task type uses SEP's <tt>sbc_nds</tt> and Novell's <tt>ndsbackup</tt> to back up the eDirectory. Using <tt>sbc_nds</tt> generates the appropriate command line for backup levels FULL/DIFF and INCR. The <tt>ndsbackup</tt> function requires user and password information. These values must be defined in the properties of the backup task as '''Backup option''' and '''Restore option''' with <tt>-a user= {your user},pass= {your password}</tt>.

<!--T:372-->
For example:</translate>

 -a user= cn= admin.o= novell,pass= novell

<translate><!--T:373-->
Selective restore is not supported but you can filter specific subtrees. To do this, choose '''Expert options''' in the restore wizard and enter the requested subtree under the '''Filter''' tab.

<!--T:374-->
;Availability of backup task type ''OES Novell directory'' :Provided for OES2 without SP2.
;Availability of recent <tt>sbc_nds</tt>:Use the recent version : {{DDL|netware/}} <tt>sbc_nds_*.*</tt> or <tt>sesam-novell-client-*.*</tt>
:Is <tt>sbc_nds</tt> in <tt>bin/sesam</tt> on client side available and executable?
;Backup task with user and password :If it doesn't exist, define a backup user and password for eDirectory backup in Novell iManager.
:Define a backup task with the task type ''OES Novell directory''. The source is the identifier of your eDirectory tree or subtree. You may check this with the<tt>ndsbackup</tt> scan function.
:Set the '''Backup option''' and '''Restore option''' to: <tt>-a user= {your user},pass= {your password}</tt>
;Restore :Use the target '/' to restore into the original tree.
:With '''Expert options''' you may set the filter to the requested subtree.

<!--T:375-->
'''Path for ndsbackup after eDirectory 8.8.1'''

<!--T:376-->
As of eDirectory version 8.8.1, ndsbackup is no longer located in <tt>/usr/bin</tt> but instead in <tt>/opt/novell/eDirectory/bin/ndsbackup</tt>. Therefore you have to link to the SEP sesam <tt>bin</tt> directory to enable SEP sesam operation. Use the following command (note that this for default SEP sesam installation):</translate>

  ln -sf /opt/novell/eDirectory/bin/ndsbackup /opt/sesam/bin/sesam

<translate>===  {{anchor|TSAFS backup}}Which mode should I use for TSAFS backup of OES Novell file systems? === <!--T:622-->

<!--T:378-->
The TSAFS should generally be loaded in ''Linux mode''. The ''Netware mode'' and ''Dual mode'' are only intended for mixed environments (backup of native Netware servers) or for a Novell cluster in mixed mode.

<!--T:379-->
* On cluster nodes of a pure Linux OES cluster, use the TSAFS ONLY in ''Linux mode''.
* On a mixed cluster (OES Netware and OES Linux nodes), the TSAFS must be loaded in ''Netware or Dual mode''. For the backup of the cluster volumes, the ''Netware Cluster filesystem'' target must be used.</translate>

<translate>=== {{anchor|EOL}}How can I set or modify a retention time (EOL) for backup === <!--T:1234-->

<!--T:1235-->
When configuring SEP sesam environment, you set up media pools and define the retention time. The retention time period starts with the date a saveset is written to the medium (at the end time of the first backup) and thus defines the expiration date of the saveset (saveset EOL). The EOL property can be managed for three object types: ''Saveset EOL'' (the expiration date for each saveset), ''Backup EOL'' (the expiration date for all data that belongs to the same backup), and ''tape media EOL''. If a saveset is part of a backup chain, its EOL follows the rules of dependency-based retention to retain the consistency of backed up data and ensure successful restore.

<!--T:1236-->
However, you can check or modify the expiration date (EOL) manually by setting the exact expiration date; for this you can use the ''calendar function'' to extend or shorten the saveset's/backup retention under all media-related views, e.g., in the ''Media'', ''Media Pools'' and ''Data Stores'' properties. You can also directly expire the saveset or backup by clicking the ''Expire'' -> ''Saveset EOL/Backup EOL'' button. You should only expire the saveset (individual EOL) or backup (EOL of the entire backup set) if you know what the ''Expire function'' does and are aware that the expired savesets and backups are irrevocably lost! For details, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].</translate>

<translate>==  {{anchor|backup errors}}BACKUP ERRORS == <!--T:1221--> 

=== {{anchor|backup_failure}}How to deal with a failed backup === <!--T:1222--> 

<!--T:1219-->
There are various causes why the backups fail, e.g., file-size issues, insufficient permissions, etc. 
When a backup fails check the [[Special:MyLanguage/SEP_sesam_Glossary#logging|day log]] and search for errors. Then identify the problem by following the basic troubleshooting procedure in the [[Special:MyLanguage/Troubleshooting_Guide#identify|Troubleshooting Guide]]. After fixing the problem, restart your backup to ensure that all your data is properly protected.

<!--T:1223-->
{{Note|In case of a failed backup, SEP sesam will delete the backup automatically after 3 days. If you want to keep any failed backup for a longer time, you may manually extend the backup EOL of a particular saveset. For details, see section [[Special:MyLanguage/Managing_EOL#manual_extend|Manually extending EOL]].}}

===  {{anchor|client backup problem}}A client backup did not function properly. How can I determine where the problem is? === <!--T:380-->

<!--T:381-->
The following test commands should help you isolate the problem. You can run a test backup for the target client from a SEP sesam Server or Client without writing data to a tape drive or disk drive. Run the following commands in the directory {{path|<SESAM_ROOT>/bin/sesam/}}.</translate>

<translate><!--T:666-->
{| WIDTH= "95%" style= "background-color: #FFF0F0; border: solid 2px #DEB0B0;"
 | style= "background-color: #DEB0B0;" | <font size= "-1"><b>Caution!</b></font>
 |-
 |
The following commands produce a high network load.
 |}

<!--T:383-->
'''Backup server Unix, client Windows'''</translate>

 sm_ctrlc -l system  {client name} sbc -b -s -  f:/test  >/dev/null

<translate><!--T:384-->
Data from the F:/ directory on Windows is written over the network to the directory {{path|/dev/null}} on Unix.

<!--T:385-->
To display this, append <tt>-v 1</tt> to the command above. Everything written to {{path|/dev/null}} will be displayed.</translate>

 sm_ctrlc -l system  {client name}   sbc  -b -s  -  -v 1      f:/test  >/dev/null

<translate><!--T:386-->
'''Backup server Unix, client Unix'''</translate>

 sm_ctrlc -l root  {client name}   sbc  -b -s -  /usr  >/dev/null

<translate><!--T:387-->
To display the read data:</translate>

 sm_ctrlc -l root  {client name}   sbc  -b -s -  -v  1   /usr  >/dev/null

<translate><!--T:388-->
'''Backup server Windows, client Unix'''</translate>

 sm_ctrlc -l root  {client name}   sbc  -b -s -             /usr    > NUL

<translate><!--T:389-->
With backup data logging:</translate>

 sm_ctrlc -l root  {client name}   sbc  -b -s -  -v  1   /usr    > NUL

<translate><!--T:390-->
If the test backup is to be run on the target backup client only, execute the following command:

<!--T:391-->
'''In the Unix directory {{path|<sesam>/bin/sesam/}}:'''</translate>

 sbc -b -s  -  /usr   >/dev/null

<translate><!--T:392-->
'''In the Windows directory</translate> {{path|<SESAM_ROOT>\bin\sesam\}}:'''

 sbc  -b -s  -  f:/test    > NUL

<translate><!--T:393-->
Enter <tt>-v 1</tt> to show the backed up data on your monitor.

===  {{anchor|name resolution}}Why do I receive the message: "Login incorrect. Password incorrect." during backup?=== <!--T:1199-->                  

<!--T:395-->
Check your name resolution (DNS or <tt>etc/hosts</tt> file). The SEP sesam Server and SEP sesam Client must be reachable with or without FQDN and should be able to resolve each other correctly, including the reverse lookup. In case you have changed an entry in your DNS configuration, but Windows still reports a wrong hostname/IP, try to run "ipconfig /flushdns" as administrator. If the resolution is correct, do the following:
# In the SEP sesam GUI, go to '''Main Selection''' -> '''Tasks''' -> '''By clients''', and select the client where the backup problem is.
# Open the properties of the backup and click the tab the '''Options'''.
# Insert ''-v 4'' in the '''Backup options''' (previously ''Save options'') field.
# Start the backup again. Then go to '''Main Selection''' -> '''Job state''' -> '''Backups''', and double-click the backup task to open its properties. 
# Go to the '''Logging''' -> '''Day log''', and search for the line ''Login incorrect. Password incorrect.'', then correct the respective name resolution.

===  {{anchor|client backup failure}}What should I do when a client backup fails with a WIN32 API error: "1450 - Not enough system resources to execute the requested service"? === <!--T:396--></translate>

<translate><!--T:397-->
The backup of a client may end with the following error message in the backup log:

 <!--T:398-->
sbc-1148: Error:   W2KSS Error: [WIN32 API error: 1450 - Not enough system resources to execute the requested service.
 Cannot store registry key: [SOFTWARE]. RegSaveKey() call failed in BackupRegistry().].

<!--T:399-->
This is caused by insufficient size of the registry/paged memory area. This problem affects SEP sesam as well as other backup tools, such as NTBackup. The following Microsoft article explains approaches for different versions of Microsoft Windows: http://support.microsoft.com/kb/304101/en-us

===  {{anchor|encrypted data failure}}Why does the backup of encrypted data fail on Microsoft Windows 2000 with the message "The network path was not found"?=== <!--T:1200-->                     

<!--T:401-->
Microsoft released a hotfix for older Microsoft Windows 2000 versions for the backup of encrypted data (Encrypting File System - EFS). See: http://support.microsoft.com/?scid=kb%3Ben-us%3B843198&x=10&y=8</translate> <!-- link no longer working --> 

<!--T:402-->
<translate><!--T:577-->
Beginning with this hotfix, there is support for the Unicode patch convention with the \\?\ prefix.

===  {{anchor|System_state backup}}What does the warning "The system cannot find path. RegLoadKey()..." during System_State backup mean? === <!--T:403-->
You may see the following output in NOT-Log</translate><!-- What is NOT-Log? -->:

<translate><!--T:578-->
C:\Program Files\SEPsesam\var\tmp\usr_wf_S-1-5-21-220523388-1123561945-839522115-1003].
 2010-04-13 02:04:20: sbc-2074: Warning: W2KSS Warning: [WIN32 API error: 3 -
 The system cannot find path. RegLoadKey() call failed for
 file: [C:\Documents and Settings\nn\ntuser.dat] in BackupUserProfiles().].

<!--T:405-->
There are inconsistencies in the OS configuration. The reason is that a user profile has been deleted but the user account still exists. The ''System_State''backup is looking for files corresponding to the user in the file system but the files no longer exist. To resolve the problem, delete the user in question or restore the profile date in the file system.

<!--T:406-->
Check the following in your registry to see whether it still includes references to usernames which no longer exist:</translate>

 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

<translate>===  {{anchor|Powershell script}}Why is the Powershell script not executed on a target machine? === <!--T:407-->
By default, Microsoft installs Windows Powershell with the permission set to '''Restricted'''. This setting only allows the execution of commands in Powershell but no scripts.

<!--T:408-->
This can be changed with following command in Powershell:

 <!--T:409-->
Set-ExecutionPolicy RemoteSigned

<!--T:410-->
For more information, see http://technet.microsoft.com/en-us/library/ee176961.aspx

===  {{anchor|backup via VSS}}Why does a Microsoft Windows backup via VSS stop with "[CVssBaseObject::CreateVssBackupComponents] - Access denied?" === <!--T:411-->

<!--T:412-->
SEP sesam is not allowed to create a snapshot with the current user. Check the user running the SEP sesam daemon and make sure that the user has all permissions to access the volume(s).

===  {{anchor|stream data size}}What does "Stream data length bigger than buffer can accept. Input buffer length = [65536], Stream data size = (High part)[0] (Low part)[65564]" mean? === <!--T:625-->

<!--T:414-->
SEP sesam uses 64 kB to back up Windows ACL files and folders and one object exceeds this buffer. You can use the Windows command ''icacls'' to display the ACL of a file or folder. The output looks like this:</translate>

  C:\>icacls "C:\Documents and Settings\LocalService\Local Settings\Temp"
  C:\Documents and Settings\LocalService\Local Settings\Temp NT AUTHORITY\LOCAL SERVICE:(I)(F)
                                                           NT AUTHORITY\LOCAL SERVICE:(I)(OI)(CI)(IO)(F)
                                                           NT AUTHORITY\SYSTEM:(I)(F)
                                                           NT AUTHORITY\SYSTEM:(I)(OI)(CI)(IO)(F)
                                                           BUILTIN\Administrators:(I)(F)
                                                           BUILTIN\Administrators:(I)(OI)(CI)(IO)(F)
  Successfully processed 1 files; Failed processing 0 files

<translate><!--T:415-->
If you get several hundred or thousand lines, there is something wrong with the ACL. You should reset the permissions of the file's respective folder by using the command:</translate>

  C:\>icacls "C:\Documents and Settings\LocalService\Local Settings\Temp" /reset

<translate><!--T:416-->
This command inherits the permissions of the parent object. You may have to adjust the permissions after running this command if manual settings have been applied for this object.

==  {{anchor|permissions}}PERMISSIONS == <!--T:417-->
===  {{anchor|user performance}}Can users perform their own backup and restore?===

<!--T:418-->
Typically, users cannot backup their own computers, but it can be done by installing a SEP sesam Server license on the target client (the user's computer). This way, the user becomes the SEP sesam administrator of the respective client/server and can backup and restore the files on this computer.

===  {{anchor|Master schedule changes}}Can the ''Master schedule'' be changed by a user?=== <!--T:420-->
Essentially, no. The most efficient method of handling this is for the user to convey his needs to the system administrator. Upon initial installation, the backup periods are established and entered into the ''Master GUI''. This would be an appropriate time to have input from the users when any special backup and restore commands are required and have them administered centrally. If necessary, a SEP sesam Server license can be added.

<!--T:421-->
The sesam ''Master GUI'' can be installed on the client but this would give the client/user all privileges. Another solution that requires greater overheads (more work on the part of the administrator) is to install a GUI with restricted privileges.

==={{anchor|access}}How do I get access to SEP sesam Server?=== <!--T:952-->
SEP sesam uses the authentication module to grant and restrict access to SEP sesam Server. You can connect to SEP sesam Server only if you are granted appropriate user permissions. Your user rights depend on the specified user type (admin, operator or restore). For details on how to configure authentication, see [[Special:MyLanguage/4_4_3_Grolar:About_Authentication_and_Authorization|About Authentication and Authorization]].

==  {{anchor|encryption and compression}}ENCRYPTION & COMPRESSION == <!--T:422-->

==={{anchor|encryption_types}}What encryption types are available with SEP sesam?=== <!--T:984-->
SEP sesam provides data encryption types on different levels: [[Special:MyLanguage/4_4_3_Beefalo:Backup#encryption|backup-task encryption]] for savesets (set in the backup task), [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Si3 encryption]] for Si3 deduplication store, and hardware-based [[Special:MyLanguage/LTO_Encryption|LTO encryption]] for LTO tape drives (generation 4 and higher), which is done on a media pool level. For every encryption you must create and store an encryption key. 

==={{anchor|Si3_encryption}}How to encrypt an Si3 deduplication store?=== <!--T:985-->
As of SEP sesam v. 4.4.3 ''Tigon'', you can encrypt an Si3 deduplication store by creating the deduplication security password file and specifying it in the relevant drive properties. If the encryption key is not available, the Si3 encrypted data cannot be read. For details, see [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]].

===  {{anchor|data encryption}}When encryption is selected before transferring data to the server, does SEP sesam do a compression before it encrypts the data?=== <!--T:423-->

<!--T:424-->
Data encrypted by the system and transferred to the server will be compressed if stored to tape using the manufacturer's compression algorithms.

===  {{anchor|encryption key storage}}Where is the encryption key stored? === <!--T:425-->

<!--T:426-->
The encryption key is stored in the SEP sesam database. If the encryption key is changed, the subsequent task will be executed with the new key and the new key will be stored in the SEP sesam database.

<!--T:427-->
A restore uses the stored encryption key.

===  {{anchor|compression settings}}How to set compression? === <!--T:428-->
'''Compression for backup to virtual tape media'''

<!--T:430-->
To activate compression for backing up to a ''Path'' [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]], modify the file {{path|sms.ini}} under {{path|/var/opt/sesam/var/ini/}} on the [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. The ''Compresslevel'' option under the caption ''[SMS_Server]'' can be enabled with

 <!--T:431-->
 Compresslevel=1

<!--T:843-->
Note that [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 deduplication store ]] always uses compression for the deduplicated data.

<!--T:433-->
'''Compression on tape drives'''

<!--T:434-->
Compression is done by the drive itself. Use the SEP sesam tool <tt>slu</tt> to check whether compression is activated or deactivated.

<!--T:435-->
'''''Step 1''''': Display a list of attached SCSI devices</translate>

<translate><!--T:1076-->
<tt>slu topology</tt> is a SEP sesam SCSI loader utility that provides information about the loaders and drives connected to the system and their relation. To be able to run the SEP sesam commands globally, you must first set up a profile as described in [[Special:MyLanguage/FAQ#profile setting|FAQ: What happens when I set a profile?]]</translate><br />
<translate><!--T:1077-->
Then run <tt>slu topology</tt> to list all attached SCSI devices.</translate>

  <SESAM_BIN>/sesam/slu topology
<translate><!--T:1078-->
For details on the output, see [[Configuring Loaders and Drives#slu_topology|Using ''slu topology'' for detecting devices]].</translate>

<translate><!--T:436-->
'''''Step 2''''': Check the tape drive settings</translate>

  [root@sinus sesam]# ./slu <b>0020</b> -s
  Tape Info
  Read Attribute not supported
  internal_status_byte= 0x0
  buffered_mode= 1
  block_length= 0 (variable)
  media_type= unknown (0)
  write_protect= 0
  density_code= 44
  <b>compression= 1</b>
  STATUS= SUCCESS MSG= "OK"

<translate><!--T:437-->
If compression is set to 1, drive compression is active. Setting the compression can also be done with <tt>slu</tt> or alternatively with the Linux tool <tt>mt</tt>.

<!--T:438-->
'''''Step 3''''': Activate compression</translate>

  [root@sinus sesam]# slu <b>0020</b> -c 1
  DCE= 1
  DATA COMPRESSION ENABLE:1
  TRY MODE SELECT (6) SET COMPRESSION DCE
  compression= 1
  DONE MODE SELECT (6) SET COMPRESSION DCE
  STATUS= SUCCESS MSG= "OK"

<translate><!--T:439-->
On Windows systems, check if the compression is enabled in the '''Device Options'''. When performing a check, make sure that the tape is in the drive.

<!--T:440-->
[[File:Tape-compression.jpg|link=]]

==  {{anchor|restore}}RESTORE== <!--T:441-->

===  {{anchor|single file restore}}Is it possible to restore only single files if the SEP sesam listing file is no longer available ?=== <!--T:1201-->                  

<!--T:443-->
Yes. In order to do this, enter the file patterns into the restore wizard. First, the desired save set is selected in the registry tasks and the option'''Complete restore''' is selected. Click the '''Expert options''' button to open the ''Expert options'' window. Click the '''Filter''' tab and enter the file patterns. Separate each entered pattern with a space. Only files which fit into specified pattern will be restored. All others are ignored.

<!--T:444-->
Examples:

  <!--T:445-->
/*.xls          -> restores all files with the ending ".xls"
  /*/X11/XF86*    -> restores all files from the directory "/X11" which start with
                     "XF86".
  /*.ini /*.conf  -> restores all files which end on ".ini" or ".conf"

<!--T:446-->
'''Note''': is is essential to use '/' when writing the pattern.

===  {{anchor|selective restore commands}}How do I use the selective restore commands?=== <!--T:1202-->                 

<!--T:448-->
# Create a new directory root in the <tt><SESAM_ROOT>\var\work</tt> directory.
# You will need the <tt>.sgm</tt> and <tt>.lis</tt> files from the backup.
# Execute "Sesamprofile".

<!--T:449-->
In the <tt>root</tt> directory, create a text file with the name "selected.txt" and extract the desired lines from the <tt>.lis</tt> file, for example:</translate>

      "C :/WINDOWS/system32/config/AppEvent.Evt" f 8.10.2004 13:26:54 8.8.2005 15:56:07 1 4096 540672

<translate><!--T:450-->
In the command line of the SEP sesam Server, enter:</translate>

 sm_restore -s SC20050809155617 -R c:/temp -v 1 -l s -c client -d 1 -V

<translate><!--T:451-->
'''Parameters''':

  <!--T:452-->
-j Original task name of the backup job
  -s The save set name of the backup job must be entered. You can find this in the .sel file from the restore job.
  -r Restore target (note the slash "/"!)
  -l The "s" is used for selective restore
  -S The hostname of the SEP sesam servers
  -v 1 increase the log levels
  -V Suppress output to the background
  -c Hostname of the client to be restored
  -d Disk drive entry of the drive where the SEP sesam media is kept, for example, "1"

===  {{anchor|tape media}}How do I restore all the data from tape media without the SEP sesam DB?=== <!--T:1203-->                  

<!--T:454-->
To restore data without a current license from SEP sesam, follow the restore procedure described below (SESAM DB restore):

<!--T:455-->
Change to the <tt><SESAM_ROOT>/bin/sesam</tt> directory and run the program <tt>sm_recover</tt>. In the first response, all known devices currently active on the system will be displayed. You can choose one of these drives.</translate>

 azurix:~ # sm_recover
 num device          name            typ
  1  disk1           Drive-1         DISK_HARD
  2  /dev/nst0       Drive-2         DLT
 Enter drive number, (r) to repeat list, (q) to quit:

<translate><!--T:456-->
By entering "2", <tt>sm_recover</tt> will look for the desired data on the physical tape drive. The following question should be answered with yes ("y") if no other backups or restores are active:

 <!--T:457-->
Analyse media: restore data or listings of savesets

<!--T:458-->
Restoring data while SEP sesam is active may cause conflicts due to concurrently running tasks on the drive. If you're sure that there are no activities scheduled during recovery, you do not need to block SEP sesam. Blocking SEP sesam during recovery prevents the execution of backup activities scheduled for the other devices.

 <!--T:459-->
Do you want to block SEP sesam ? (y|n] >

<!--T:460-->
Confirm by typing "y"

 <!--T:461-->
wait until SEPuler - the timecontrol of SEP sesam - finishes its current work ...
 SEPuler is blocked ...

<!--T:462-->
The following question should be answered with no ("n") unless you wish the data search to continue with a desired filter.

 <!--T:463-->
Do you wish to enter label, saveset-name and segment-number directly ( no searching on media ) (y/n) > n

<!--T:464-->
You will then be notified that the tape is rewinding.

 <!--T:465-->
The tape will now rewind and scanned to the end EOT...

<!--T:466-->
In the next step, you may choose the desired save sets. By entering the save set number, you can insert further instructions to restore the data. After finishing, restart all SEP sesam services.

===  {{anchor|data store media}}How do I restore all the data from a disk/data store media without the SEP sesam DB?=== <!--T:467--></translate>

'''Microsoft Windows''':

 sbc.exe -r -S $SERVER_HOSTAME -s @SF.....data -v 1 -R c:\target\

'''Linux''':

 sbc -r -S $SERVER_HOSTAME -s @SF.....data -v 1 -R /target/

<translate>===  {{anchor|backup with errors}}How can I restore a backup that has errors? The backup log file reported that the backup was partially successful.=== <!--T:630-->

<!--T:469-->
If a backup has failed but some or most of the data was backed up, you can update the SEP sesam database manually to show the backup in the restore wizard. First, the save set ID is required. This can be found in the GUI under '''Backups''' -> State -> failed backup -> Properties -> save set. Proceed as follows:

<!--T:470-->
#Source the sesam profile from <tt>$SESAM_ROOT/var/ini/sesam2000.ini</tt>.
#Modify the entry in the DB. The save set must be changed below.
#In the command line use the following commands:</translate>

 sm_db "update results set state= '1',blocks= 1 where saveset= 'SC20060101121314'"

<translate><!--T:471-->
After this change, the save set for this backup should be shown in green on the status display and appear in the recovery wizard. Nevertheless, you should still verify whether the data was backed up successfully.

===  {{anchor|restore wizard}}Why don't the data lists appear in the restore wizard?=== <!--T:472-->

<!--T:473-->
If the data lists don't appear in the restore wizard, verify whether the CTRLD switch permission is set to <on>, and if not, activate it.

===  {{anchor|restore termination}}How do I avoid the problem "553 RETR Failed. Data Synchronization lost - Restore terminating"? === <!--T:474-->
Linux/UNIX data is stored in CPIO save set which is checked during the restore to ensure that the CPIO format is correct. If a format error is detected, the restore is aborted and ends with

 <!--T:475-->
'BSA Call BSAEndData (closing saveset) failed: System detected error, operation aborted.
 TRANSIENT or PERMANENT NEGATIVE reply: 553 RETR Failed. Data Synchronization lost - Restore terminating'

<!--T:476-->
The following settings allow you to avoid a premature termination of the restore.

<!--T:477-->
;Avoid the current restore task: Enter the sbc option <tt>'-F none'</tt> to the restore command in the last tab of the restore wizard -> '''Expert options''' -> '''Restore options'''.
;Avoid all further CPIO restores on the RDS: Set the SEP sesam GLBV <tt>restore_no_abort</tt> at the RDS with <tt>'sm_glbv w restore_no_abort yes'</tt>. If the suspicious (non-CPIO) bytes lead to further problems, they can be skipped with <tt>'sm_glbv w restore_no_junk yes'</tt>.</translate>

<translate>===  {{anchor|active directory subtrees}}How can I restore Active Directory subtrees in a clustered environment? === <!--T:478-->

<!--T:479-->
# Boot into Directory Services Restore Mode. This ensures that the directory is offline. In order to do this during the normal boot menu while restarting the computer, press F8 when the message "For troubleshooting and advanced startup options for Microsoft Windows 2000, press F8" appears at the bottom of the screen. After pressing F8, select Directory Services Restore Mode from the Safe Mode and Other Startup Options list.
# Restore the ''System_State'' backup by using the SEP sesam GUI.
# To authoritatively restore Active Directory data, you need to run the <tt>ntdsutil</tt> utility. See the following example (subtree organizational unit Marketing in the domain Anitpodes.com):</translate>

     #> ntdsutil
        ntdsutil: authoritative restore
      authoritative restore: restore subtree OU= Marketing,DC= Antipodes,DC= COM

<translate><!--T:480-->
Refer to the Microsoft publication [http://windows.uwaterloo.ca/Server/Disaster/MS_docs/recovery.htm#_Toc475176610  Windows 2000 Server Disaster Recovery Guidelines - Active Directory]
and [http://technet.microsoft.com/en-us/magazine/cc162459.aspx Disaster Recovery: Active Directory Users and Groups]
section "Performing an Authoritative Restore".

===  {{anchor|path reduction usage}}Can I use path reduction of a TSA backed up volume/directory when restoring data ? === <!--T:1204-->                  

<!--T:482-->
Path relocation has been available as of Sesam Novell Client version 4.2.1-37.

<!--T:483-->
With older versions of the Sesam Novell client, this functionality is not available when using a TSA backup or restore operation. You must always select '''no relocation''' in '''Expert options''' of the restore wizard (this is the default value).

<!--T:484-->
Thus, the complete directory structure is re-created to the target directory using the directory from the selected backup. Using the command '''Restore to original target path''', the directory is restored to the original storage space with all of the files.

<!--T:485-->
[[Image:Restore_relocation_4.4.3.png|link=]]

===  {{anchor|TSA restore}}Is it possible to restore flat files/directories from multiple locations when restoring a TSA backed up file? === <!--T:1205-->                  

<!--T:487-->
This functionality is not possible with TSA backups/restores. You should select '''Original tree structure''' in the restore wizard, regardless of whether '''Restore to original target path''' or a '''New restore target''' is desired.

<!--T:488-->
[[Image:Novell_restore_path_4.4.3.png|link=]]

==  {{anchor|storage etc}}STORAGE, DEVICES & MEDIA MANAGEMENT== <!--T:489-->

===  {{anchor|backup storage usage}}Use a NAS/CIFS (QNAP, Synology ...) storage as backup target === <!--T:490-->

<!--T:633-->
The below prerequisites must be met to use a NAS or a CIFS share as a backup storage. Depending on whether your [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server@|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server (RDS)]] is Windows or Linux based, proceed as follows:
*To avoid double network traffic, connect the storage via an '''additional network card''' to the SEP sesam Server or RDS.
*If your SEP sesam Server or RDS is a '''Windows system''', create a valid user in your AD/LDAP with administrative rights. Then add this new user to your storage (NAS/CIFS) with full access to the storage part for SEP sesam. Adjust the SEP sesam system service and specify it to run under your newly created user account. Restart the service. Now you can create a [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] with a path, such as ''\\192.168.x.x\sepsesam''.
*If your SEP sesam Server or RDS is a '''Linux system''', create a permanent mount point to the server and use this mount point as a backup target for your data store.

===  {{anchor|automatic archive adjustment}}How do I set up automatic archive adjustment? === <!--T:491-->

<!--T:492-->
# Go to '''Scheduling''' -> '''Schedules''' and create a new schedule. For details, see [[Special:MyLanguage/Creating_a_Schedule|Creating a schedule]].
# Link the event to the schedule. For details, see [[Special:MyLanguage/Creating_a_Command_Event|Creating an event]]. Then enter the following:

<!--T:493-->
 Priority:      Standard set to 1.
 Name:          Enter a description that is easily recognizable.
 Command:       Example for tape loader 1, drive 2 and 10 slots: sm_robot -l 1 -d 2 -s 0-9
 Client:        Choose the desired SEP sesam Server name
 User:          For a Unix System enter: root. For Microsoft Windows: system.

<!--T:494-->
'''Note''': No explicit permissions are required for the simple activation of SEP sesam commands.

===  {{anchor|removable or USB media}}Does SEP sesam support removable or USB media for backup?=== <!--T:1206-->                  

<!--T:496-->
There is limited support for removable disk media, including USB drives.

===  {{anchor|SEP sesam tape}}How can I determine whether a tape is a SEP sesam tape or not?=== <!--T:498-->
Place the tape into a drive, select the drive in the GUI under '''Components''' -> Drives and execute the '''Identify label''' drive action. If the label is found, it will be diplayed under the drive in the ''Current messages'' display.

<!--T:499-->
Alternatively, go to the command line, change to the directory <tt><SESAM_ROOT>/bin/sms</tt> and execute the following:

<!--T:500-->
'''Unix'''</translate>

  ./sm_sms_interface getlabel -d /dev/nst0
'''
<translate><!--T:501-->
Microsoft Windows'''</translate>

  sm_sms_interface getlabel -d Tape0

<translate><!--T:502-->
The necessary device (switch -d) can be found in GUI under '''Components''' -> '''Drives'''.

===  {{anchor|label}}How can I manually write a label on a tape (e.g. to overwrite an existing label without performing a check of the SEP sesam database)?=== <!--T:1207-->                  

<!--T:504-->
Go to the command line, change to the <tt><SESAM_ROOT>/bin/sms</tt> directory and execute the following:

<!--T:505-->
'''Unix'''</translate>

 ./sm_sms_interface init -d /dev/(z.B. nst0) -t testpool00001:1

<translate><!--T:506-->
'''Microsoft Windows'''</translate>

 sm_sms_interface init -d Tape0 -t testpool00001:1

<translate><!--T:507-->
'''Note''': The tape will be overwritten without warning!

<!--T:508-->
The '''media label''' consists of three parts:

<!--T:509-->
# Name of the pool (in the above example, the name is "testpool").
# The tape ID, a 5-digit number.
# A number after the colon (':') that complies with the preceding number.

===  {{anchor|tape}}How do I automatically remove a tape after a backup is finished?=== <!--T:510-->

<!--T:511-->
The best way of removing a tape after the backup is by using the <tt>sm_notify</tt> interface. You can find a complete description of this command interface with examples of how to unload tapes following backups in the [[SEP_Sesam_Admin_Manual|SEP sesam Administration Manual]].

<!--T:512-->
The standard unload command is:</translate>

 sm_drive dismount 2 unload

<translate><!--T:513-->
This command refers to the selected drive, in this case drive 2.

===  {{anchor|cleaning tape installation}}Where do I install the cleaning tape?=== <!--T:1208-->                  

<!--T:515-->
Currently, a cleaning tape is not explicitly identified. When selecting an '''Archive adjustment''', the cleaning tape will automatically be loaded in sequence and an unwanted cleaning operation may be initiated. To prevent an unwanted cleaning operation from initiating, select the last (highest numbered) slot for the cleaning tape and reduce the number of slots by one (1).

<!--T:516-->
Cleaning may take place by manually entering the cleaning tape or by following the manufacturer's instructions.

===  {{anchor|tape locking}}Why does SEP sesam lock tapes that were not involved in a backup?=== <!--T:1209-->          

<!--T:518-->
This is related to FULL->DIFF or FULL->INC->INC->INC-> ... backups.

<!--T:519-->
The following example explains this problem:

<!--T:520-->
* full backup      ->     requires three tapes (backup00001, backup00002, backup00003)
* inc backup       ->     requires one tape (backup00004)
* inc backup       ->     requires one tape (backup00005)
* inc backup       ->     requires one tape (backup00006)

<!--T:521-->
The first backup merely changes the EOL (end of lifetime) for the three tapes (backup00001 to backup00003), the second backup changes the EOL for the first four tapes (backup00001 to backup00004) and the third backup changes the EOL for the first five tapes (backup00001 to backup00005), and so on.

<!--T:522-->
If the next full backup fails, the succeeding incremental backup will use the chain from the last successful backup(s) and so the chain expands. This is necessary for a generation restore because an incremental backup includes only the changes from the last backup, regardless of whether it was a full, differential or incremental backup. All tapes are needed to perform a successful restore.

<!--T:523-->
With a differential rather than an incremental backup, SEP sesam locks the tapes from full backup and the tapes that were used by the differential backup.

===  {{anchor|the oldest tape}}How do I get information on the oldest tape in a pool before backup starts? === <!--T:1210-->                  

<!--T:525-->
It is sometimes very useful to know which the next free medium in a pool will be before a backup starts. To get this information, type the folowing command:</translate>

 sm_arch_getoldest 1 full-disk

<translate><!--T:526-->
The command shows the next free medium of pool '''full-disk''' in drive 1.

===  {{anchor|data store consistency}}How do I check the consistency of a data store? === <!--T:528-->
The following command allows you to check the consistency of a data store:</translate>

 sm_data_store check_db -L {datastore} | -d {drive_num}

<translate><!--T:529-->
'''Example 1:'''
The example shows a data store check that detects 2 save sets with the wrong data file size (sizes smaller than stored in the SEP sesam database). The state of both backup operations is either a fail ('X') or broken data transfer ('3') and the result status is therefore 'SUCCESS'.</translate>

 #>sm_data_store check_db -L DATA_STORE2
 2014-08-28 14:39:59: $Id: sm_data_store.py,v 1.105 2013/08/18 18:06:36 sesam Exp $
 2014-08-28 14:39:59: Arguments: sm_data_store check_db -L DATA_STORE2
 2014-08-28 14:39:59: $Id: sm_data_store.py,v 1.105 2013/08/18 18:06:36 sesam Exp $  Sesam Id: None
 2014-08-28 14:39:59: Arguments: sm_data_store check_db -L DATA_STORE2
 2014-08-28 14:39:59: DB:               select * from data_stores where name= 'DATA_STORE2'
 2014-08-28 14:39:59: DB:               select * from hw_drives where data_store= 'DATA_STORE2' order by drive_num
 2014-08-28 14:39:59: DB:               select results.saveset,fdi_type,state,task,sesam_date,cnt,media_pool,results.uuid,data_size from results,result_lbls where
  results.saveset= result_lbls.saveset and results.saveset in (select saveset from result_lbls where label in (select label from media where location= 'DATA_STORE2'))
  and results.data_size>0 and results.state not in ('a','q') order by start_time
 2014-08-28 14:39:59: DB:               select results.saveset,fdi_type,state,task,sesam_date,cnt,media_pool,results.uuid,data_size from results,result_lbls where
  results.saveset= result_lbls.saveset and results.saveset in (select saveset from result_lbls where label in (select label from media where location= 'DATA_STORE2'))
  and results.data_size= 0 and results.state not in ('a','q') order by start_time
 2014-08-28 14:39:59: DB:               select label,pool from media where location= 'DATA_STORE2'
 2014-08-28 14:39:59: Looking for savesets: sm_client dir "G:/DATA_STORE2/DATA_STORE2/DataStore1/DataStore100002"
 2014-08-28 14:40:00: Looking for savesets: sm_client dir "G:/DATA_STORE2/DATA_STORE2/I_DS_POOL/I_DS_POOL00001"
 2014-08-28 14:40:00: ==================================================================================
 2014-08-28 14:40:00: Savesets in Sesam DB:          187.
 2014-08-28 14:40:00: Saveset files found:           187.
 2014-08-28 14:40:00: Saveset in DB and on FS:       187.
 2014-08-28 14:40:00: Savesets not found on disk:      0.
 2014-08-28 14:40:00: Saveset files not in DB:         0.
 2014-08-28 14:40:00: -------------- List of savesets with wrong data file size ------------------------
 2014-08-28 14:40:00: 3  SF20140826212205682@gp_o1hNIc8g  miraculix_dev 2014-08-26 00:00:00 4430717952 > 4430686656
 2014-08-28 14:40:00: X  SC20140825083202946@iW9ZD7vcSw2  SESAM_BACKUP 2014-08-21 00:00:00 1323736064 > 1323385536
 2014-08-28 14:40:00: -------------------- List of savesets without data file --------------------------
 2014-08-28 14:40:00: -------------------- List of files without DB entry ------------------------------
 2014-08-28 14:40:00: -------------------- List of files without data file -----------------------------
 STATUS= SUCCESS MSG= OK

<translate><!--T:530-->
'''Example 2:'''
A data store check that detects a save set with the wrong data file size and with a successful backup state ('0'). The result status shows 'ERROR'.</translate>

 G:\DATA_STORE2\DATA_STORE2\DataStore1\DataStore100002>sm_data_store check_db   -L DATA_STORE2
 2014-08-28 15:03:05: $Id: sm_data_store.py,v 1.105 2013/08/18 18:06:36 sesam Exp $
 2014-08-28 15:03:05: Arguments: sm_data_store check_db -L DATA_STORE2
 ...
 2014-08-28 15:03:06: Looking for savesets: sm_client dir "G:/DATA_STORE2/DATA_STORE2/DataStore1/DataStore100002"
 2014-08-28 15:03:06: Looking for savesets: sm_client dir "G:/DATA_STORE2/DATA_STORE2/I_DS_POOL/I_DS_POOL00001"
 2014-08-28 15:03:06: ==================================================================================
 2014-08-28 15:03:06: Savesets in Sesam DB:          188.
 2014-08-28 15:03:06: Saveset files found:           188.
 2014-08-28 15:03:06: Saveset in DB and on FS:       188.
 2014-08-28 15:03:06: Savesets not found on disk:      0.
 2014-08-28 15:03:06: Saveset files not in DB:         0.
 2014-08-28 15:03:06: -------------- List of savesets with wrong data file size ------------------------
 2014-08-28 15:03:06: 0! SI20140826150006895@ch-Gdm3Id_6  miraculix_dev 2014-08-26 00:00:00 106962944 > 1274932
 2014-08-28 15:03:06: -------------------- List of savesets without data file --------------------------
 2014-08-28 15:03:06: -------------------- List of files without DB entry ------------------------------
 2014-08-28 15:03:06: -------------------- List of files without data file -----------------------------
 2014-08-28 15:03:06: ERROR: File size does not match:        1.
 STATUS= ERROR MSG= ERROR: File size does not match: 1.

<translate><!--T:531-->
In this case, the save set is corrupted. You have to determine the reason for the corrupted save set (disk IO problem, file system with limited file size, etc.). To avoid the corrupted save set from being used, its result state must be changed to broken data transfer ('3').</translate>

 sm_db "update results set state= '3', msg= 'corrupt saveset (size)' where saveset= 'SI20140826150006895@ch-Gdm3Id_6'"

<translate><!--T:532-->
If the data is still available on the backup source, the backup operation must be restarted.

===  {{anchor|single tape drive}}Why can't I find my Exabyte single tape drive in the list of devices when I try to initialize it?=== <!--T:1211-->                  

<!--T:534-->
First, inspect the media pool to which you tried to enter the tape drive. If there is no number (0,1,2, etc.) behind ''Tape'', the drive was not detected by SEP sesam. You can also check this by entering <tt>slu topology</tt> in the command line prompt.

<!--T:535-->
If the device is not listed, the driver is not installed correctly. Look for the appropriate driver at the manufacturer's site or elsewhere on the internet, download it to your computer and run the program to install the driver. The media pool should now show the ''Tape (0)''. Finally, initialize the tapes. For details, see [[4_4_3_Beefalo:Media_Strategy|Media Strategy]].

===  {{anchor|skipping blocks error}}Why do I get the error message ''skipping blocks'' when I try to perform a SEP sesam backup with an Exabyte VXA172?=== <!--T:1212-->                  

<!--T:537-->
Some manufacturers often require a different driver for each tape model they manufacture. In this case, the VXA tape you initialized is not recognized by SEP sesam in the Exabyte tape drive. Go to the tape type selection in the GUI and change [VXA] to [EXA]. This will fix the problem.

===  {{anchor|LTO drive}}Why does SEP sesam not write to my LTO drive on my x86 system? === <!--T:538-->

<!--T:539-->
The OS enables PAE (Physical Address Extension) automatically on x86 systems if more than 3.25 GB RAM are in use. With PAE, the OS cannot write more than 32 KB to a tape drive whereas SEP sesam needs 64 KB for LTO. The most efficient solution is to switch to an x64 OS. Decreasing the RAM to a maximum of 3.25 GB should also solve the problem. <!--Broken link: Additional information can be found at [http://support.microsoft.com/kb/289261/en-us Microsoft support site].-->

==  {{anchor|notification and logging}}NOTIFICATIONS & LOGGING== <!--T:540-->

===  {{anchor|notification meaning}}What does the notification "Disk space for listings and logging below critical threshold" mean? === <!--T:541-->
In the NEWDAY task, SEP sesam Server checks the free disk space on the partition where the log files and listings are stored.</translate>

 <SESAM_ROOT>\var\log
 <SESAM_ROOT>\var\lis

<translate><!--T:542-->
If free space falls below the critical threshold value, the server sends an email notification.

<!--T:543-->
The threshold value (default = 5000, 5000 MB) can be configured in <tt>sm.ini</tt> under the [Params] section <tt><SESAM_ROOT>\var\ini\sm.ini</tt>.</translate>

 [Params]
 gv_min_free= 5000

<translate><!--T:544-->
{{Box Hint|ATTENTION|
If there is no more disk space available on the partition, the server cannot write additional logs and listings. This can result in critical errors and lead to data loss. This error should be addressed at the earliest possible opportunity.}}

===  {{anchor|higher logging level}}How do I set a higher logging level? === <!--T:1213-->                  

<!--T:1233-->
You can increase the logging level for specific backup or restore task in the GUI: ''Main selection'' -> ''Tasks'' -> ''By Clients'' -> double-click the backup or restore task to open the ''Properties''. You can also set the logging level globally for SEP sesam kernel modules, as described in [[Special:MyLanguage/Setting_Log_Level#globally|Setting log level globally for SEP sesam kernel modules in <tt>debug.ini</tt>]]. Note that running SEP sesam with a higher logging level than default (0 for backup and restore) increases the amount of information being logged and may negatively affect the performance of SEP sesam. For details, see [[Special:MyLanguage/Setting_Log_Level|Setting Log Level]].</translate>

<translate>===  {{anchor|audit_log}}Is it possible to generate audit logs? === <!--T:1244-->

<!--T:1245-->
As of SEP sesam v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']], it is possible to use the <tt>sm_gui_server_requests.log</tt> as a source for audit logs by generating a more readable version of the log file with evidence of each action that was triggered by a user. Audit trail records may contain the following details:

<!--T:1249-->
*date and time
*API request for the executed action
*user associated with the activity
*user IP address

<!--T:1247-->
The below example shows that the restore task was deleted by the user Administrator.
 
 2021-02-03 10:55:08,592 - [GET] /sep/api/restoreTasks/rs_task01/forceRemove [User: Administrator, IP: 192.168.21.12:59111]

<!--T:1248-->
For detailed procedure, see [[Special:MyLanguage/4_4_3_Beefalo:Audit_Logging|Audit Logging]].

===  {{anchor|client access problem}}Why do the request status or daily protocol (log files) return "Host SEP sesam is not allowed to connect or security problem for user"? === <!--T:1214-->                  

<!--T:556-->
Typically, there is an issue with client's access privileges. The error message reads:</translate>

 scd-1136: Error: Host [{SEPsesam}] is not allowed to connect or security problem for user: [{user}].

<translate><!--T:557-->
There is a problem with the RMI GUI Server on the SEP sesam Server. The system requires '''CTRL''' or '''SMSSH''' privileges to complete the SEP sesam commands. On the backup client add permission for the SEP sesam server so the server is allowed to connect to the client.

<!--T:558-->
Execute the following command at the client:</translate>

  sm_setup set_client <SEP sesam server hostname>

<translate><!--T:559-->
For example, if the SEP sesam Server hostname is <tt>backup01</tt>:

<!--T:560-->
* On Microsoft Windows, in the directory <tt>C:\Program Files\SEPsesam\bin\sesam</tt>, call:</translate>

  sm_setup set_client backup01

<translate><!--T:561-->
* On Linux, call:</translate>

  /opt/sesam/bin/sesam/sm_setup set_client backup01

<translate>==  {{anchor|report}}MONITORING & REPORTING == <!--T:562-->

===  {{anchor|dashboard_access}}How can I access SEP sesam dashboard? === <!--T:1215-->                  

<!--T:933-->
SEP sesam dashboard (Web UI) is an online monitoring tool that allows you to check if all your backups and restores have been completed successfully. You can access it online at the following address: http://[servername]:11401/sep/ui or https://[servername]:11401/sep/ui. For example, on the SEP sesam Server the following 'localhost' link will open the SEP sesam dashboard: [http://localhost:11401/sep/ui http://localhost:11401/sep/ui]. The dashboard (Web UI) is also available in the GUI. For details, see [[Special:MyLanguage/SEP_sesam_Web_UI|SEP sesam Web UI]].

===  {{anchor|special report}}Can special reports be generated for backups, backup time, performed restores, etc.? === <!--T:1216-->                  

<!--T:564-->
Yes. Special scripts can be written and inserted for the execution of both pre- and post-operations using the commands <tt>execute_pre</tt> or <tt>execute_post</tt>. For details, see [[Special:MyLanguage/Using_Pre_and_Post_Scripts|Using Pre and Post Scripts]].

<!--T:1155-->
Due to stringent EU requirements for reporting, data security and data restore, many required reports may already be included without additional administrator intervention.

===  {{anchor|backup reports}}I would like to generate both summary and detailed reports for backups. Does SEP sesam provide this extra granularity?=== <!--T:1217-->                  

<!--T:566-->
SEP sesam provides both a summary of and detailed information on every backup executed. In addition, the system can send a summary report over the SEP sesam notify interface to an email account after finishing the last backup. SEP sesam summarizes the backup information on a daily basis. The time schedule and sequence can be selected by the user or system manager and may be set to any 24-hour period. For example, if you specify a backup time of Monday 11 p.m. to 8 a.m. on Tuesday, all backups performed within this window will be recorded as Monday.

===  {{anchor|daily protocol}}How can I send a SEP sesam daily protocol to an email account? === <!--T:568-->
We recommend that you [[Special:MyLanguage/4_4_3_Beefalo:Configuration#mail|configure support accounts]] and use <tt>sm_notify</tt> templates from

 <!--T:648-->
{sesam_Root}\skel\templates\sm_notify.cmd

<!--T:649-->
or

 <!--T:650-->
{sesam_Root}/skel/templates/sm_notify

<!--T:569-->
Copy the templates to:</translate>

 {sesam_Root}/bin/sesam
<translate><!--T:570-->
and modify them as necessary, especially in the line:</translate>

 sm_smtp -A sesam -M gv_dayfile: -a gv_prot: -s "Sesam backup status: "+%1+" "+%2+
<translate><!--T:571-->
"<tt>A</tt>" {account} must be changed to the email account that was configured with the GUI.

<!--T:572-->
After the execution of the last backup or command event, the <tt>sm_notify</tt> interface is called with the module "ALL_JOBS_DONE" and the SEP sesam daily protocol will be sent to the specified email account.</translate>