Copyright © SEP AG 1999-2011. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.
The SEP Community Version is available to the general private user community. Please note that the software, manuals, licensing and terms from SEP AG and SEP Software Inc remain unchanged.
During the installation of a SEP sesam demo version (can be found at SEP's download page) a Community License file is created automatically. This file has to be used in perpetuity and copied to the license file location after the 30-day trial period is over.
The file sm_lic.ini.com can be found at <SESAM_ROOT>/skel.
Copy the file to <SESAM_ROOT>/var/ini and rename it to sm_lic.ini.
You can check the license status under "Help -> License Info" in the GUI.
The SEP Community Version is available for Windows and Linux. You do not get technical support and it cannot be upgraded. However, the SEP Forum and the SEP Wiki are always available if you need help.
One of the essential advantages of SEP sesam is that not all information is filed in a database, but in simple text files.
Usually the really big files are the *.lis files. These contain information about the unique files of a backup and are used by the restore wizard for selecting and restoring unique files.
Those files are stored in the following directories:
These files can be compressed by SEP sesam automatically.
Before executing this command the SEP sesam profile has to be set.
To execute the process of compressing immediately, the command "sm_newday" can be used.
The compression then will be done directly with the "newday" schedule.
The reason why the *.lis files are not compressed directly after they are created but, as predefined in the command, three days later, is that in our experience most restores are triggered within three days after a backup.
Detailed description under: How to create a Remote Device Server (RDS).
<SESAM_ROOT>/bin/sesam/slu scan (e.g. Tape0 or /dev/nst0). If you've selected a disk drive you only need to enter the drive type DISK_HARD.
Free Backup for Zarafa environments
SEP sesam provides a complete Backup-, Restore- and Recovery solution for all types of IT environments from simple single server, single operating system solutions to multi-O/S, complex heterogeneous environments that are running various types of hardware and software applications.
Besides the usual server Operating Systems like Novell Netware, Linux, Windows, Unix and Solaris, SEP sesam offers extensions to execute hot backups of common groupware and database applications.
A complete overview of supported software is available in the SEP sesam OS and database support matrix
Zarafa users can get a complete SEP sesam environment to backup their Zarafa installation for free. The following modules are provided in the free download:
The free licenses for backing up the Zarafa Server do not expire. However, the license is limited to this dedicated environment. Please note that no upgrade service or technical support is included.
It is possible to upgrade the free version with the following enhancements:
are available at the SEP Homepage.
All SEP sesam Software is available at the SEP Download Center
SEP sesam Server for Linux http://download.sep.de/linux/
SEP sesam Server for Windows http://download.sep.de/windows/
Zarafa Module http://download.sep.de/extensions/groupware/zarafa/
MySQL Module http://download.sep.de/extensions/databases/mysql/
An introduction to setup a backup of the Zarafa Server with SEP sesam is available on the SEP Wiki:
SEP sesam Extension for Zarafa
Under the following link there is a list of different versions for the designated operating system and architecture (64 and 32 bit) of Sun's Java Runtime Environment. After accepting the license agreement the appropriate package can be downloaded.
SEP sesam NEWDAY gives System Managers 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 computers requiring backup exceed the time allotment between the End of Day and midnight. SEP sesam defines the period between two NEWDAY events as one backup day. This event is predetermined at the installation and may need to be adjusted for specific requirements.
When a daily NEWDAY event is set to 08:00 the backup day lasts until the morning of the next day 08:00 (8 a.m.). Backups that run after midnight - the real new day - will be administered (recorded) as a backup of the prior day.
Example: The SysAdmin begins a backup at 19:00 (7 p.m.) and the projected finish time is 02:00 (2 a.m.) By selecting a NEWDAY event at 08:00 (8 a.m.) the job has time to complete and all data is stored in the backup file of the day the job was started.
Weekends are often used for full-backups. If this is the case it is advisable to interrupt the Newday event on the weekend. Define the execution as a weekly event but without execution since a Full Backup is performed instead.
A NEWDAY event carries out the following tasks additionally:
You can configure the NEWDAY to a time other than 8 a.m. but you should not deactivate the NEWDAY event because the internal administration jobs in the system and database can't work without it. This could provoke malfunctions in the SEP sesam system in the medium term.
If you need a new license please contact sales@sep.de and provide the following information:
To determine which specific names SEP sesam uses (e.g. if more than one network card is installed on the server) you can use the information that's given in the SEP sesam GUI under "Help -> License info". Our compliance/sales team will send you a new license via e-mail.
If the SEP sesam Server is currently running in trial mode, you can examine the number of clients and modules needed by your configuration under "Help -> License info".
Follow these steps to activate your license:
<SESAM_ROOT>/var/ini
<SESAM_ROOT>/bin/sesam
If the program displays errors in the hostname or IP address please contact our licensing department immediately at support@sep.de. If all the information is correct please send the license file back to support@sep.de with a copy of the output file returned after running the above commands.
There are different services depending on whether you dealing with a SEP sesam Server, a SEP sesam Client or a SEP sesam Tapeserver.
The services can be found in the SEP sesam 'Install Directory' <SESAM_ROOT>/bin/sesam
to check the status of the services.
SEP sesam needs Java version 1.6 or higher. Either Oracle/Sun Java, as well as IBM Java or open JDK can be used.
The Java version currently in use can be checked with the following command:
Example:
IMPORTANT: If the SEP sesam Server is installed as an RPM package in Linux, Java has to be installed as an RPM package as well.
NOTICE: For the installation of the SEP sesam Server on an OES2 system, please note that the Java version 1.5 that is running there has to remain the default, so the Novell specific functions can be operated. If another Java version (e.g. 1.6) is installed in the system via RPM the default Java version is kept, i.e. the reinstallation doesn't overwrite it. This means that the installation of Java and the following installation of the SEP sesam Server can be done as described below.
The approach here is shown with a 64 bit Sun Java:
/opt/sesam/bin/sesam. In case of a Tarball installation of the SEP sesam Server and the Java, the link has to be set manually.
IMPORTANT: If the Java is installed as Tarball, the SEP sesam Server also has to be installed as Tarball. Installing a SEP sesam Server package with --nodeps is not supported by SEP AG.
The approach for a Java Tarball installation:
/opt/java
/opt/java
You can also operate several Java versions in Windows. Here the SEP sesam Server can also be working with a different Java version than the default Java version of the operating system. In the file <SESAM_ROOT>\var\ini\sm.ini in the section [JAVA] the path of the desired Java version has to be entered:
With this, SEP sesam Server gets its own Java environment on startup.
To allow access from a client to the SEP sesam Server you must insert a command from the administration console. The entry depends on the type of client platform.
Use the following to set the access rights: HKEY_LOCAL_MACHINE\SOFTWARE\SEP Elektronik GmbH\sesam\CommandEvents\{user}\{command} for the user and the command.
Call the Regedit editor and create a new key under HKEY_LOCAL_MACHINE\SOFTWARE\SEP Elektronik GmbH\sesam\ (right click, select "new Key") - if they don't exist already - CommandEvents, enter the user and then the command with full path information as the key. If other commands are present the last command is completed. It is possible to enter an asterisk (*) which allows all commands to be executed.
Copy the file sesam_cmdusers.allow from the directory <SESAM_ROOT>/skel to /etc on the client and adjust the file. This means you can enter a line for the user and command in the format {User} {command}. The wild card (*) means all commands are executed.
Note: No explicit permissions are required for the execution of SEP sesam commands like sm_loader. [edit]
On some Linux Systems the threads created by the SEP sesam GUI are shown in the process table. These are not real processes but only threads. There are a large number of processes since Java creates threads for all objects with 'Listener' functionality.
By setting the profile, the directories (and their subdirectories) <SESAM_ROOT>/bin, and <SESAM_ROOT>/var/db/ are added to the environment variable "$PATH" so SEP sesam commands can be executed globally, and you don't need to be in the actual "run directory".
The profile is set in the following manner:
Go to the directory
<SESAM_VAR>/var/ini and call
Important! Do not forget the dot and the space ( )!
Or simply use
Open a Command Window
Go to the directory
<SESAM_ROOT>\var\ini and call
Or use the Link
| Note: |
|
The profile is hereby just set for the current session. To set it permanent under Linux please look here. |
First your license must be amended to match the new server name and/or IP-address. Please send the original license, the new server name and IP-address to info@sep.de. Until you receive the license please change the following items in the database. Set the SEP sesam profile and execute the following commands:
In this table the name and ip_address must be changed.
When you receive the new license information you can change the SEP sesam Server name using sm_setup. First set the SEP sesam profile and enter the following command:
When using the standard configuration for SEP sesam the following ports must be opened to allow backups:
In some cases the backup must be performed with a higher loglevel in order to supply our developers with more detailed information.
There are two ways to set the loglevel: the backup loglevel and the restore loglevel.
The backup loglevel can be set in the additional call arguments.
Double-click the backup task. Go to the register "Options 1".
The following loglevels exist:
Set the loglevel like shown in this screenshot:
The loglevel for restore is set in the expert options of the last page of the restore wizard, like shown in this screenshot:
Even if you can reach a client from the backup server with nslookup and ping over DNS names it is still possible that the SEP sesam Server cannot connect to the client. In this case you can check the reachability of a client from the SEP sesam Server view. You have to enter the following command:
For Linux/UNIX client:
For Windows client:
The output should be as follows (example with Linux client) (standard output of the sbc command):
When a network problem occurs the output could look like:
...or a connection from SEP sesam Server to the SEP sesam Client is forbidden:
In order to be able to back up a client behind a firewall several ports need to be unlocked. First, a port range has to be adjusted. This can be done in the SEP sesam GUI via the options of the according clients via the STPD options:
It is necessary to check if "Timeouts" are considered in the firewall options if no traffic is running on a port. This specifically affects port 11001 because it only transfers data at the beginning and end of a backup.
Transferring of the OOB-signal has to be activated for all ports.
If you want to make a data mover communicate with an OES-NetWare (6.5/6.0) Server that's inside a DMZ only the following port has to be unlocked for the TSA: 40193
The following image shows the connection as well as the port range:
This means that the SEP sesam Client has to allow always port 11301 and all ports from the range defined above for incoming connections by the SEP sesam Server.
Using the Nagios plugin from Netway to query and monitor the SEP sesam Database
| 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 nor will make any guarantees or warranties as to the usability or functionality of such scripts. Therefore, for obvious reasons, SEP can not 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. |
NETWAYS GmbH has developed an Open Source database query routine for SEP sesam - the Nagios plugin. This is, in accordance with the OSF foundation rules 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.
| Note: |
|
Since many names of parameters in the SEP sesam database have changed in Version 4.0 you have to choose the adequate Version of the plugin. |
Download: http://download.sep.de/utils/nagios/
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 warranted to work in other environments. Sample scripts to query the SEP sesam DB have been written illustrating the use of the Nagios methodology are for demonstration purposes only. They can be found at the third party site:
http://download.sep.de/utils/nagios/SesamToNagios_DemoScripts.tgz
In 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 none for non-local or network drives.
For access to network drives the following configurations have to be modified:
Due to increased security since Windows 2000/2003 and XP it is not possible to assign dedicated drive letters, e.g. e:\. Instead the path must be entered using UNC Notation. The backup is carried out over the associated network devices but only after entering the UNC Names e.g. //fileserver/install/Driver.
Prerequisite: From SEP sesam Client the network share has to be accessible without retrieval of username and password. If this is not the case, the share on the providing computer has to be modified.
| Attention |
|
The VSS Option has to be disabled when backing up UNC paths. Only one path for each task is possible. |
To exclude a file or a directory the following has to be entered (with regular expressions):
The source being backed up in this example is:
Path that should be excluded:
File that should be excluded:
As mentioned in the section above the SEP sesam service has to be running on an administrator account. Then, you can enter the following command for a backup in the command line:
For a restore command use:
This saves the files in \pub\customers into the file (saveset) test.save, i.e. restores them from the saveset test.save into the folder \pub\customers_restore.
To install a SEP sesam GUI, the GUI software package must be loaded on the target computer. The actual software for the different Linux distributions can be downloaded from download.sep.de, like e. g. sesam_gui-3.4.1-31.SuSE.i586.rpm.
Install this package after the download. For example:
Afterwards please check if the SEP sesam Server is available by using the following command:
Now make a shortcut with the following path:
done
You need to create a link in the directory /etc/profile.d/.
If many directories or files have to be included in or excluded from a backup task it may be possible that the limit of counts or characters of the field (max. 255 character) will be exceeded. To solve such problem you can use files to define a backup source or an exclude list. This file has to be created on the backup client the backup is to be executed on.
Include:
Create a separate line for each directory or file item in a file (e.g. /etc/sesam/backupfiles.txt):
| Attention |
|
Wildcards are not allowed in the file or directory entries. |
At least one item has to be entered in the field Source, e.g. you can enter the include-file itself. Then this file is also included in the backup set (e.g. /etc/sesam/backupfiles.txt). In addition to that you have to set up the following entry in the field Save options of the register Options 1 in the backup task definition:
Beside the value of the source field all values that are containd in the file are backed up.
Exclude:
The behaviour of the exclude is quite similar. This file is called e.g. /etc/sesam/excludefiles.txt. Each file or directory you want to be excluded from the backup has to be entered in a separate line in the file, e.g.:
| Achtung |
|
Please keep in mind that the exclude entries have to be set up with a regular expressions syntax. |
For instance, all is entered in the source of the task definition. This means that the complete system is backed up excluding the items in the exclude file. In contrary to the include the field Exclude List is left empty. Then set up the following entry in the field Save options of the register Options 1 in the backup task definition:
SEP sesam will exclude all files and directories from the backup which are included in the file.
In order to install a SEP sesam GUI on a Linux system you need to have the current installation package. You can get the installation packages for the various distributions at download.sep.de, e.g. sesam_gui-3.4.1-31.SuSE.i586.rpm. Install this package after the download as shown in this example:
Afterwards, please check if the SEP sesam Server can be reached by using:
Lastly, create a shortcut with this path:
and you're done.
The following message appears when starting the SEP sesam GUI:
Please check if the SEP sesam RMI server component is active and if the used port matches.
The program is terminated.
If you get this error message, first check the java version with the following command:
If this java version is wrong it has to be updated.
The backup of a client ends with the following error message in the backup log:
The reason for this is the small size of the registry/paged memory area. This problem not only affects SEP sesam but also other backup tools like for example NTBackup. The following Technet article explains approaches for different Windows versions:
The Layered Service Provider (LSP) Chain is defective/damaged. The cause can be an Antivirus program or a Virus; another possibility is that DLLs were switched during the installation or deinstallation. This results in the subprocesses not being able to inherit open your Socket Handles
In this example event the SEP sesam CTRL connection takes the SM_CTRLD_MAIN daemon call from SM_CTRLC, it opens the necessary Sockets and passes them on to the newly created subprocesss SM_CTRLD. Due to the defective LSP the Sockets can not use this information and returns during an operation, e.g. setsockopt() the following error:
10038 - The descriptor is not a socket.
The easiest way to check this is to use the following free tools on the client computer:
Typical Action:
An example of a correct listdlls for an environment:
After removing the defective DLL the socket can be inherited by the subprocess SM_CTRLD. [edit]
This section explains how to create and use an exclude list.
If you want to exclude many directories from a backup source you can create a .txt-file on the computer that you want to backup. This file should contain all directories you want to exclude from the backup.
E.g.:
Create the file exclude.txt on the client in the directory C:\Programme\SEPsesam\var\ini.
Possible content of exclude.txt:
The backup task source is set to D: In the backup task window you can see the field Save options. Here, enter:
-X C:\Programme\SEPsesam\var\ini\exclude.txt
IMPORTANT:
|
In SEP sesam version 4.3.1-69 a double backslash has to be used (\\) instead of a single slash (/)! (known bug) |
In this example the whole drive D: is backed up except the directories that are declared in the exclude.txt.
In the configuration file <SESAM_VAR>/var/ini/sm.ini on the sesam client the entry
must be changed to
Since SEPsesam version 3.4.1.67 Archive bit are not used for incremental and differential backups on Windows. This can be switched, if necessary.
The use of archive bit may be set with
After setting the value to 'yes' the Windows Archive Bits of the files are treated in the following way according to the backup type COPY/FULL/DIFF/INCR:
Therefore, when selecting a backup strategy the following issues must be considered:
As a consequence of these issues we recommend to save on time based creation/modification. See below.
Attention: Since SEPsesam version 3.4.1.67 Archive bit are not used for incremental and differential backups on Windows!
To set the use of creation/modification time execute the following steps:
Got to the directory <SESAM_ROOT>/bin/sesam and call:
After this FULL, DIFF and INCR backups ignore Archiv Bits. DIFF and INCR backups use the start time of the last referenced backup in case of DIFF a preceding FULL - in case of INCR any preceding backup.
Optional resetting of Archiv Bits of backed up files is executed with the option
when it is inserted in the properties of the backup task in tab 'Options 1' in field 'Save options'.
Microsoft has released a Hotfix for older Windows 2000 Versions for the backup of encrypted data (Encrypting File System - EFS). Dated March 24, 2004. Please see:
http://support.microsoft.com/?scid=kb%3Ben-us%3B843198&x=10&y=8
Beginning with this Hotfix Unicode Patch Convention with Prefix \\?\ is supported.
1. Boot into Directory Services Restore Mode. This ensures that the directory is offline. During the normal boot menu while restarting the computer, notice the message at the bottom of the screen: For troubleshooting and advanced startup options for Windows 2000, press F8. Do this and then select "Directory Services Restore Mode" from the "Safe Mode and Other Startup Options" list.
2. Restore the "System_State" Backup using the SEP sesam GUI.
3. To authoritatively restore active directory data, you need to run the Ntdsutil utility - Example with Subtree organizational unit Marketing in the domain Anitpodes.com:
Refers to Microsoft Publication Windows 2000 Server Disaster Recovery Guidelines - Active Directory and Disaster Recovery: Active Directory Users and Groups section "Performing an Authoritative Restore"
You can see the following output in NOT-Log:
This is an inconsistency of the system configuration of the operating system. The reason is that a user profile has been deleted but the user account still exists. The System_State backup is looking for the corresponding files of the user in the file system, but these files don't exist anymore. To resolve the problem, delete the appropriate user or restore the profile date in the file system.
Please check the following Hive in your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
whether it still includes references to usernames which no longer exist.
By default Microsoft installs Windows Powershell with permission Restricted. This setting just allows to execute commands in Powershell, but no scripts.
This can be changed with following command in Powershell:
Set-ExecutionPolicy RemoteSigned
Click here for more information:
http://technet.microsoft.com/en-us/library/ee176961.aspx
Yes, it's possible to use the VSS functionality to backup MS SQL or MS Exchange environments. But it's only recommended for small installations.
For the consistent backup of a running MS Exchange or MS SQL environment exist two strategies. The usage of the SEP sesam Online Extensions for MS Exchange or MS SQL. Or the file system backup with the activation of the VSS Writer for MS Exchange or MS SQL (Volume Shadow Copy functionality of Windows).
SEP sesam Online Extensions
Backup via the VSS Writer of Microsoft
Critical
In distributed environments the different components have to be informed if a backup of one of the systems is performed to enable a consistent restore. For example in a Sharepoint Server environment, the Database and the Mailserver run on different servers. A VSS Backup of a single server will result in an inconsistent restore. Here only the backup via the SEP sesam Online Extensions will guarantee consistent data.
Summary
The Backup of MS Exchange or MS SQL environments via VSS is a valid option to get a consistent backup of the running environment – as long as the volume of data is not to big. It is an alternative for small environments with only 1-5 users. In critical productive environments the usage of the SEP sesam online Extensions for MS Exchange / MS SQL is highly recommended.
The following test commands should help you to isolate the problem. From a backup server or a client you can make a test backup for the target client without writing data to a tape drive or disk drive. Run the following commands in the directory <SESAM_ROOT>/bin/sesam/.
| Caution! |
|
All of the following commands produce a high network load. |
The data from Directory F:/ of the Windows computer is written over the network to the Unix computer to the directory: /dev/null.
To display this add -v 1 to the command above. Everything written to /dev/null is displayed that way.
or with the announcement of the read data:
With logging of backup data:
If the test backup is only to be run on the target backup client the command
in <sesam>/bin/sesam/ Unix directory is executed.
And entered <SESAM_ROOT>\bin\sesam\ in Windows
Enter -v 1 to show the backed up data on your monitor.
Please check your name resolution (DNS or etc/hosts file). The SEP sesam Server and SEP sesam Client must be reachable with or without FQDN. SEP sesam Server and SEP sesam Client should be able to resolve each other correctly including the so-called reverse lookup. If the resolution is correct please do the following:
In the SEP sesam GUI go to Tasks > by Clients and go to the client and its incorrect backup job.
Open the properties of the backup here and move to the register "Options 1".
Insert -v 4 at backup options .
Start the backup again and go to Backup by State. There go to the properties of the backup an then to Protocol. Here, search for the line "'Login incorrect. Password incorrect."' and correct the respective name resolution here.
The encryption key is stored encrypted in SEPsesam Database in the backup task entry - table tasks - and in the result entry - table results. If the encryption key is changed then the subsequent task will be executed with the new key and the new key is stored in table results.
A restore uses the stored encryption key from Table Results.
| Note |
|
The option "Compression" under the tab "Options 2" in the "Properties" of a backup task is only valid for Windows. |
To activate compression globally for all backup tasks under Linux the sms.ini under /var/opt/sesam/var/ini/ have to be modified. Under the caption [SMS_Server] the option Compresslevel can be enabled with
This entry is also valid in Windows.
Compression is done by the drive itself here. You can use the SEP sesam tool "slu" to check whether compression is activated or deactivated.
Linux:
If "compression" is set to 1 drive compression is active. Setting the compression can also be done with "slu" or alternatively with the Linux tool "mt":
The first thing that has to be done is establishing an IP address for the new interface. The IP address will then be entered the properties table of the (Tape) server under Topology - Clients (Interface). In the backup events the IP name must be selected from the tab "parameter" in the field interfaces.
Example: The computer 'testme' has a 2nd Interface Module with the name 'testmeb'. In the backup task select 'testmeb'.
Since OES SP2 a TSANDS is available for eDirectory on Novell OES Linux. SEP sesam provides a special backup type called "OES Novell Directory" for older versions. This backup type is using SEP's sbc_nds and Novell's ndsbackup to back up eDirectory. sbc_nds is generating an appropriate command line for backup levels FULL/DIFF and INCR. ndsbackup needs User and Password. These values must be defined in the properties of the Backup Task as Backup Option and Restore Option with -a user={your user},pass={your password}
For instance:
-a user=cn=admin.o=novell,pass=novell
There is no selective restore possible but you can filter specific subtrees. To do this you have to choose "Expert Options" in the restore wizard and enter the requested subtree under tab 'Filter'.
Since eDirectory version 8.8.1 ndsbackup is no longer located in /usr/bin but instead in /opt/novell/eDirectory/bin/ndsbackup.
To enable an execution with SEP sesam a link into the SEP sesam bin directory is necessary.
Use the following command in case of a standard installation:
SEP sesam can be set to full, incremental, differential or copy. The disadvantage of incremental is that only changes are backed up to a daily/weekly tape file. In the event of a data restore it will require loading all the incremental tapes up to the data restore. Differential does not require this extra effort. With Differential Backups, restores can be accomplished in Generational View. In this mode SEP sesam will automatically restore the base file and the latest differential backup. SEP sesam will request/mount the appropriate media, simplifying the restore process. It will manage this for all files selected for restore. Copy allows you to make a copy of the data without taking the place of the normal archival activity set by the Master Administrator--it is not to be used when doing a data or a system restore.
Users typically cannot backup their own computers but it is possible. The most efficient way to accomplish this would be to install a SEP sesam Server license on the target client (i.e. the user's computer). In this mode the user can be designated as the administrator for his/her desktop and the server can be backed up as if it were a client by the SEP sesam GUI administrator.
Backups can be written either to tape or disk, sesam after version 3.0 supports Disk-to-Disk-Tape functionality. All backup functions are written by the server and/or controlled by the server and may be written directly to the backup disk or tape or remote tape server. SEP sesam supports virtual tape libraries on disk with a pseudo autoloader function. Removable disk media is also supported.
Yes, Removable disk media including USB drives are supported.
In order to do this you can enter file patterns into the Restore Wizard. First the desired "Saveset" is selected in the registry tasks and the option "fully restore" is selected. With the button Expert Options the Expert Options Window is opened. Enter the file patterns in the register "Filter". Many patterns are separated with blanks. Only files which fit to this pattern will be restored. All others are ignored.
Examples:
Attention: the '/' is essential when writing the pattern.
In the 'root' directory create a Text File with the name: "selected.txt" and from the .lis File extract the desired lines, e.g.:
On the command line of the SEP sesam Server enter:
sm_restore -s SC20050809155617 -R c:/temp -v 1 -l s -c client -d 1 -V
Parameter:
To restore the data without a current license from SEP sesam the following restore procedure should be followed (SESAM DB Restore). Change directories to <SESAM_ROOT>/bin/sesam start the program sm_recover. In the first response you will see all known devices currently active on the system. It is possible to choose one of these drives.
By entering "2" sm_recover will look for the desired data on the physical tape drive. The next question should be answered with yes "y" if no other backups or restores are active
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 recover you don't need to block SEP sesam. Blocking SEP sesam during recovery prevents execution of backup activities scheduled for the other devices.
Verity with "y"
The next question should be answered with no "n" unless the search for data should continue with a desired filter.
The next response will be that the tape is rewinding.
In the next response you may choose the desired savesets. By entering the saveset number you can insert further instructions to restore the data. After finishing please restart all SEP sesam services, if desired.
If a backup has failed but some or most of the data was in fact backed up you can update the sesam database manually to show the backup in the restore wizard. First the saveset ID is required. This can be found in the GUI under backups by status-> failed backup> Properties> saveset (p. ..). Then on the command line use the following commands:
After this change the saveset for this backup should show in green on the status display and appear in the recovery wizard. Despite this sucessfull appearance you should check whether data was backed up sucessfully.
1. Boot into Directory Services Restore Mode. This ensures that the directory is offline. In order to do this during the normal boot menu (Please select the operating system to start) while restarting the computer notice the message at the bottom of the screen: For troubleshooting and advanced startup options for Windows 2000, press F8. Do this and then select Directory Services Restore Mode from the Safe Mode and Other Startup Options list.
2. Restore the "System_State" Backup with the SEP sesam GUI.
3. To authoritatively restore Active Directory data you need to run the Ntdsutil utility - Example with Subtree organizational unit Marketing in domain Anitpodes.com:
Refer to Microsoft Publication "Windows 2000 Server Disaster Recovery Guidelines-recovery.doc"
In this case the SID is rac1.
In SQL*Plus as DBA-User: SQL
The following statements can be used from every tool
For more information on the topic of SID, see: http://www.ordix.de/ORDIXNews/1_2004/db_1.html (German)
There are two ways to backup a Novell Grpupwise Server with SEP sesam. You can use the SEP sesam Groupwise Extension or the Admin can perform a file level backup of the Groupwise Server.
In general the backup of a Novell Groupwise Server is always performed via the TSA Interface of Novell. Either via tsagw or via tsafs (gw enabled). There is no difference between the two backup options. The difference is in the management of the Backup and Restore Jobs.
To find out more about the backup principles of SEP sesam in a Novell Netware / OES environment, please read Backup Principles of SEP in a Novell OES environment.
Summary:
For the file based backup and restore you need qualified knowledge of the Groupwise environment and the management of Groupwise systems. With the SEP sesam Groupwise Online Extension, a backup and - even more important - a restore of a Groupwise Systems can be performed from any administrator, no Groupwise knowledge is required.
Backup with SEP sesam Groupwise Agent
During the definition of a new backup job for a Client. The SEP sesam agent automatically recognizes there is a groupwise running on this client and offers the Admin a Groupwise backup.
The admin does not has to know where the Groupwise data are stored and which files are important to backup and which files not.
The backup process is started as a Groupwise backup process. The process is clearly identified as a Groupwise backup. The SEP sesam Server knows, this is a Groupwise backup and not just a normal file backup. This makes the management and problem location (in case there are problems) much more easier.
Technical it's only a file backup. But the SEP sesam agent ensures to backup the right files from the right directories.
For the restore we have a similar scenario. The SEP sesam Groupwise extension knows the backup (technical a file backup), is aware that all the files belong together to a Groupwise system. And the SEP agent now restores all the required files to the Groupwise Restore area on the Groupwise Server. Based on this data in the Groupwise Restore area Groupwise can start a recover process to restore the data (Mails or Mailboxes).
The Admin doesn't have to know, which files are the right ones and what the right place to restore is.
Backup without SEP sesam Groupwise Agent
Without the SEP sesam Groupwise Agent the backup of a Groupwise system
is performed like a regular file backup.
The Groupwise is shown as a regular NSS volume in the filesystem.
With it's volume name. The Admin has to know
- Which volume is the Groupwise volume
- Which files within the volume he has to backup
The backup process itself starts as a file backup process.
For the restore the admin - has to know which files he has to restore - where is the restore directory of Groupwise
Create a 'Pool' in the GUI under Components/Media pools. You can identify this pool with any recognizable name.
For example, if a Media Pool had a limitation of 1000MB it is possible to select 10 DISK_100 media types.
For 10 media the first would be Slot 0, the last slot 9. Automatic initialization must be activated. When the above steps have been performed successfully you can select 'Immediate Backup' on the new pool (Disk) to start the backup process.
Note: For the simple activation of SEP sesam commands no explicit permissions are required. Also see How do I schedule a backup task?
Put the tape into the drive, select the drive in the GUI under Components > drives and execute the drive action "identify label". In the display "Current Messages" the label, if found, will be displayed under the drive.
Alternatively you may go to the command line, change into the directory <SESAM_ROOT>/bin/sms and execute:
For Unix
For Windows
you will find the necessary device (switch -d) in GUI under Components >drives.
Go to the command line, change into the '<SESAM_ROOT>/bin/sms' directory and execute:
For Unix
./sm_sms_interface init -d /dev/(z.B. nst0) -t testpool00001:1
For Windows
sm_sms_interface init -d Tape0 -t testpool00001:1
Attention: The tape will be overwritten without any warnings!!
The media label consists of three parts:
The best way to accomplish tape removal after backup is by using sm_notify interface. You can find a complete description of this command interface with examples of how to unload tapes following backups in the SysAdmin Guide.
The standard command to unload is as follows:
sm_drive dismount 2 unload
This command refers to selected or desired drive, in this case drive 2.
At the current time a cleaning tape will not be explicitly identified. When selecting an "Archive Adjustment" the cleaning tape will be automatically loaded in sequence and an unwanted cleaning operation may be initiated.
To prevent an unwanted cleaning operation from starting it is recommended that you select the last (highest numbered) slot for the cleaning tape and reduce the number of slots by one (1).
Cleaning may take place by manually entering the cleaning tape or by using the manufacturer's instructions.
A little example is shown to explain this problem.
full-backup -> needed three tapes (backup00001, backup00002, backup00003)
inc-backup -> needed one tape (backup00004)
inc-backup -> needed one tape (backup00005)
inc-backup -> needed one tape (backup00006)
The first backup just 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), the third backup changes the EOL for the first five tapes (backup00001 to backup00005), and so on...<p>
If the next full backup fails, the following 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 just includes the changes from the last backup, no matter, whether this was full, differential or incremental. All tapes are needed to perform a successful restore.
With backup type differential instead of incremental sesam just locks the tapes from full backup and the tapes, which were used by the differential itself.
Sometimes it's very handy to know the next free medium of a pool, before a backup starts. To get this information just type this command:
This command tells the next free medium of pool full-disk in drive 1.
Every GUI client must be allowed access to the SEP sesam Server using sm_setup allow_gui {GUI-client} {user}
Example:
The following error messages may appear when adding new clients to the SEP sesam Server.
Error:
or
Possible Problems:
1. There might be no SEP sesam Client software installed; 2. A wrong system name has been entered in the SEP sesam GUI; 3. A firewall between the two computers is active.
Solution:
Error Message:
Problem: The SEP sesam Server has no privileges to access the client
Solution: Enter the value in the [___] into the client's <SESAM_VAR>/var/ini/sm_ctrld.auth
Error Message:
Problem: The connection between client and server is not functioning.
Solution: Check with the help of the nslookup command if the name resolution "Forward" with and without FQDN as well as "Reverse" is correct.
Attention: Check on the SEP sesam Server AND on the SEP sesam Client:
Example - check mysesam name resolution and reverse lookup:
If DNS is not being used and the verification is taking place over the etc/hosts file use ping to verify individual clients.
To define a backup source with more than 256 characters in the complete filename (path and filename) it is possible to use file with a list of all paths as backup source. Create the text file with a list of all paths (e.g. /opt/sesam/var/ini/large_source.txt). Each path must be written under the previous one which means you'll have a fully qualified file or directory name on each line.
In the properties of the backup task is a flag called Option 1 in the lower portion of the Expert Options. There, enter the backup option -f {file} e.g.
The SEP sesam Server reads this file during the backup and stores the additional files and directories named in the source directories.
Exclude patterns may be entered into a file. Create a text file where all pathes are listed one below the other (e.g. /tmp /opt/sesam/var/ini/large_exclude.txt/......) and save this file in a folder of your choice. During the creation of a backup enter the folowing statement.
During the backup all directorys in .txt file be excluded also.
See also Windows Exclude with file patterns
This is usually a problem with CTRLD privileges. The error message:
scd-1136: Error: Host [{SEPsesam}] is not allowed to connect or security problem for user: [{user}].
There is a problem with the RMI GUI Server on SEPsesam Server. The system requires CTRLD privileges to complete SEP sesam commands. Look in the directory <SESAM_VAR>/var/ini/sm_ctrld.auth. It is possible that there has been a change the computer name, the domain name or the entry in sm_ctrld.auth.
Please check these directories and if necessary run 'sm_setup set_client {SEPsesam}'.
For example: If SEPsesam Server 'backup_1 is called:
If the server name has been changed it has to be reset.
Please check if the CTRLD switch permission is set to <on>, if not please activate.
This may occur if Java 1.3 is installed. If this is the case, please install SUN JRE Java version 1.4.2. After the installation the Java link must be changed. In the <SESAM_ROOT>/bin/sesam directory the link java still refers to the old Java path. Change it to the new Java version and restart server portion of the SEP sesam GUI by entering:
After SLES9 Unicode is 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.
Essentially, no. The most efficient method to handle this is for the user to convey his needs to the System Administrator. Upon initial installation the backup periods are established and entered by 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 could be added.
The sesam Master GUI can be installed on the client but this would give the client/user all privileges. Another solution that requires more overhead is to install a GUI with restricted privileges. Obviously this requires more work on the part of the administrator.
To set the GUI permission for a GUI client you can use the program <SESAM_ROOT>/bin/sesam/sm_setup with the syntax
sm_setup allow_gui -u (User) -c (Hostname of GUI client} -m (Permission: "admin" - all, "operator" - configure and start backups, "restore" - start restores)
Example for a Windows client with the hostname "ruoffnix". User "cr" will get all permissions for SEP sesam.
<SESAM_ROOT>/bin/sesam/sm_setup allow_gui -u cr -c ruoffnix -m admin
After this call the RMI server receives the changes and restarts. It should now be possible to restart the GUI. Start the GUI from the host "ruoffnix" user "cr".
Please be careful with upper and lower case and check FQDN or NOFQDN.
In case of an error you may get information of missing entries in "Current Messages" in an active SEP sesam GUI or by using <SESAM_ROOT>/bin/sesam/sm_info p
Every GUI Client must have permissions entered on the SEP sesam Server. Move to the directory <SESAM_ROOT>/bin/sesam and enter sm_setup. After this command you will receive information regarding all possible combinations.
The complete command should be as follows:
sm_setup allow_gui -u (System user that will be GUI administrator) -c (Hostname of server/client where the GUI will be opened) -m (Sets privileges for individual GUI users): "admin" - all, "operator" - creation and start of backups, "restore" - initiate restores)
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 rpm -U <sesam serverpackage>.
The following error messages appear when starting the SEP sesam GUI:
Please verify if the SEP sesam RMI Server component is active and if the Port being used is correct.
If this message appears, first check the Java Version with the following command:
If the Java Version is not 1.4.2 or greater you will need to update the Java files.
SBC_SMDR
First, look at the media pool where you tried to enter the tape drive if there is no (X) number, (e.g. 0,1,2, etc.) behind 'Tape' it means the drive was not detected by SEP sesam. You can also do this by moving to a command line prompt and enter slu scan. If the device is not listed the driver is not installed correctly. Go to the manufacturer's site or look for the appropriate driver on the Internet. When you find it, download it to your computer's desktop. Then run the program to install the driver. Look at the media pool and you should now see Tape (0). Now begin to initialize tapes as described in the User Manual.
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 GUI to tape type selection and change [VXA] to [EXA]. This will fix the problem.
The OS enables PAE (Physical Address Extension) automatically on x86 system, if more than 3.25GB RAM are in use and with PAE the OS cannot write more than 32KB to a tape drive, SEP sesam needs 64KB in case of LTO. The most efficient way is to switch to an x64 OS, otherwise decreasing RAM to max 3.25GB should solve the problem, too. Furhter information can be found here: http://support.microsoft.com/kb/289261/en-us
Data encrypted by the system and transferred to the server will be compressed if stored to tape using the manufacturer's compression algorithms. If it is stored to disk data can either be encrypted or compressed but not both.
For example, if members of a workgroup are all sent the same Power Point Presentation and store it on their respective desktops, does it make separate copies or one with pointers to changes?
SEP sesam stores separate files for each user. We have thought about the alternative and unless there is a very large amount of data being stored in the files, any changes that might be made to the main data array would have to be stored in multiple areas or tapes and, if a restore was required, more overhead would be required to restore the data.
Yes, SEP sesam can backup open files for both Linux and Windows.
SEP sesam for Linux does backup open files.
Open files can be backed up with the Volume Shadow Copy Service by Microsoft. To do an open file backup a Windows Snapshot of the data and partition that are to be backed up is made and then the partition is backed up. Databases should be backed up using the appropriate SEP sesam database module.
System Requirements:
Client O/S: Windows 2003 SEP sesam Server after Version 3.0 SEP sesam Client after Version 3.0
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.
Yes. Specialized scripts may be written and inserted for execution both pre and post operations utilizing the commands execute_pre or execute_post. Due to stringent EU requirements for reporting, data security and data restore, many desired reports may already be included without additional effort by the administrator.
SEP sesam provides both a summary and detailed information about every backup run. In addition, the system can send a summary report over the SEP sesam notify interface to an email account after finishing the last backup. This is possible because SEP sesam summarizes the backup information daily. The time schedule and sequence is selectable 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.
We recommend to configure Support Accounts and to use sm_notify templates from
resp.
Please copy into
and modify to your needs, especially in the line:
-A {account} must be modified to the required email account that was configured with the GUI.
After the execution of the last backup or command event the sm_notify interface is called with the module "ALL_JOBS_DONE" and the SEP sesam Daily Protocol will be sent to the specified email account.
This problem usually occurs on SLES-based Linux systems. Here you need to check the file
and change the according entry for the loopback-adress "127.0.0.2" or remove it from the /etc/hosts file entirely.Our sales team would be happy to assist you!
Browse and discover videos by SEP.