SEP sesam Glossary

From SEPsesam
Jump to: navigation, search
This page contains changes which are not marked for translation.

This SEP sesam glossary contains terms and definitions found in the SEP sesam manuals. Most of the terms are specific to the SEP sesam product.

Contents  * A B C D E F G H I J K L M N O P Q R S T U V W X *

A

access mode
Defines the communication method and access type between the SEP sesam Client and the SEP sesam Server. The following access modes are available: CTRL (default), SMSSH (SEP sesam SSH based control communication), PROXY (available vendor-specific protocols are: vSphere (vCenter Server), Citrix Xen Server, NetApp and Novell SMS for NetWare 5.1/6.0/6.5), SSH (Secure Shell), and RSH (Remote Shell). Access mode is defined in the Client Properties dialog. For details, see client properties.
access rights
See user's permissions.
ACL
An access control list (ACL) is a list of permissions attached to an object. It specifies which access rights each user has to a particular object, as well as what operations are allowed on particular objects.
admin
A person with the administrator role that is responsible for managing SEP sesam. Admin role is the only user role with full control over the SEP sesam. See also user types.
alarm (sm_alarm)
One of the SEP sesam configurable interfaces, intended for system administrators. Alarm is executed on the SEP sesam Server to warn the system administrator when a fatal error occurs. It can only be used if it has been activated before. See interfaces.
alternate data streams (ADS)
A file in NTFS consists of the primary or unnamed data stream where the data is actually contained ($Data), and of alternate data streams that can store additional metadata. ADS are used by many applications for storing file attributes or other non-critical information, such as thumbnails for graphical files, parsing information for program sources, etc. As of SEP sesam version 4.4.3, ADS are backed up by default when backing up a NTFS file system, and automatically restored to any ADS-aware system. For details, see Support for NTFS alternate data streams (ADS) for Windows.
ASR
Automated system recovery (ASR) is a Windows XP/Windows Server 2003 feature that simplifies recovering from a disaster by performing an automated backup and an automated restore. SEP sesam supports system disaster recovery based on ASR writer. ASR writer is used as part of a VSS backup-and-recovery application that performs disaster recovery. See also VSS.
authentication
Authentication is used to grant and restrict access to SEP sesam Server. Users can connect to SEP sesam Server only if they are granted appropriate permissions. Their user rights depend on the specified user type. For details, see Authentication.
autoloader
See loader.

B

backup
The process of copying and storing file system and/or application data. .
backup day
A time interval between two NEWDAY events. SEP sesam enables you to define a backup day according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. A backup day is defined by time set in the NEWDAY event. See also NEWDAY.
backup client
See SEP sesam Client.
backup EOL
See EOL.
backup level
Used to specify the level of data that is copied from source to destination. It is defined when configuring a new backup event in the Main Selection window -> Scheduling -> New Backup Event, tab Parameter, option Backup Type. Available backup level types are: FULL, DIFF, INCR and COPY.
backup plans
An overview of all configured migrations, task groups, tasks and related backup events. Backup plans overview is selected in the Main Selection window -> Tasks -> Backup Plans. In the Backup Plans window you can also configure a new backup event.
backup server
See SEP sesam Server.
backup task
Used to configure a backup for the selected client. A backup task always contains specification of the backup type, client and source information. Optionally, other parameters can also be specified when configuring a backup task, such as the pre- and post-exec scripts. A backup task or group can be configured as a follow-up event.
backup type
Used to select the type, according to which the data is backed up. It is defined in the Main Selection window->Tasks -> By clients, when configuring a New backup task. Possible backup types are: Path backup system state backup, SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphereetc.
bare metal recovery (BMR)
See disaster recovery.
bare system recovery (BSR)
Also called bare metal recovery. See disaster recovery.

C

calendar
See calendar sheet and custom calendar.
calendar sheet
An overview of scheduled as well as expired events and their current status. Calendar sheet is selected in the Main Selection window -> Scheduling -> Calendar Sheet. In the content pane the day view is displayed, showing all events in the range of 24 hours. The weekly and monthly view are displayed at the upper right side corner. All events are recorded by SEPuler.
Changed Block Tracking (CBT)
A VMware feature that backs up only the blocks that have changed, thus enabling incremental backups for VMware virtual machines (VMs). From SEP sesam version 4.4.3, CBT is globally enabled by default. For versions ≤ 4.4.3, CBT has to be enabled manually as described in Activating CBT globally. CBT for particular backup task can be set when configuring a VMware backup task. SEP sesam uses CBT to perform block level incremental (INCR) and differential (DIFF) backups of VMDKs after a full (FULL) backup has been successfully executed.
circular logging
Circular logging is a Microsoft Exchange Server method of conserving hard disk space by periodically overwriting the transaction log file contents. In order to perform incremental (INCR) and differential (DIFF) backups of the Exchange databases, circular logging has to be disabled. For details, see Microsoft article that also provides information on disabling circular logging.
client
See SEP sesam Client.
cold backup (C)
An offline backup of VMs and databases. See also hot backup.
command line
The prompt, where you enter commands.
Command Line Interface (CLI)
A utility that provides an alternate way to execute SEP sesam commands in UNIX and Windows environments. The CLI supports most of the commands that are available in the SEP sesam GUI. In addition, you can create, modify or delete SEP sesam objects, and generate reports (lists) in different output formats. The CLI may be called from operating system batch files. The CLI description is available at SEP sesam CLI.
command task (command event)
Allows the execution of an arbitrary program together with arguments on a SEP sesam Client. For details, see Creating a command event.
complete restore
A process by which an entire save set is restored. The other restore types are selective restore and generation restore.
components
The first item in the Main Selection window of the SEP sesam GUI that provides a list of the components of the SEP sesam environment. The following components are available: topology, clients, data stores, loaders, drives, media pools, and media. Selecting a component opens the corresponding main window for the selected option. See also GUI.
compression
Used for compressing data in save sets. SEP sesam provides data compression for backup tasks and data store Path, and allows for hardware compression of tape devices. Si3 deduplication store always uses compression for the deduplicated data. You can select the backup task compression under the Encryption and compression tab in the backup task properties. You can activate compression for a data store in the sms.ini file on RDS. You can also set compression for a tape device. For details on setting compression, see FAQ: How to set compression. See also encryption.
COPY (C)
A backup level in which all data defined by the backup task is backed up (e.g. files), regardless of when it was last changed. The difference from full (FULL) backup is that COPY save sets are not referred by any differential (DIFF) or incremental (INCR) save sets.
custom calendar
Can be specified by using a schedule option User defined. Use it to manage working and non-working days in relation with your scheduled data protection tasks. A custom calendar can be used to simplify exclusion or inclusion of individual events (such as backup, migration or replication) to run on certain dates, for example, to prevent scheduled backups to run on holidays. The importance of a calendar event is defined by event priority. You can create a custom calendar in the schedule properties: Main Selection window ->Scheduling -> Schedules -> User defined tab. For details, see Creating a custom calendar. You are able to modify, import, export and delete a calendar.

D

daemon
A long-lived program that implements a service. For instance, sm_qm_main is a daemon that implements the queuing and execution of the SEP sesam tasks.
daemons
Daemons specific to the SEP sesam Client/SEP sesam Server/SEP sesam Remote Device Server (RDS) installation.
dashboard
See SEP sesam dashboard.
Data Management Application (DMA)
DMA controls the NDMP session. NDMP is based on a master-slave relationship. DMA is the session master, which initiates the backup and restore operations. NDMP services are the slaves. See also SDMA and SEP sesam NDMP. For details on SEP sesam NDMP integration, see NDMP Backup.
data mover
See SEP sesam data mover.
data store
A device type used for writing the save sets directly on one or several configured storage locations — into the file system. Data store configuration consists of specifying data store capacity and watermarks: HWM and LWM. The default data store type is Path. This data store type is relevant for configuring all storage locations, except for SEP sesam additional archiving and deduplication module that uses a dedicated SEP Si3 deduplication store. As of SEP sesam version 4.4.3, SEP EasyArchive data store and FDS deduplication store are no longer supported. For more details, see Data Store.
data store capacity
The space reserved exclusively for the SEP sesam data store. When specifying the capacity value, a dedicated partition must have enough free space. The reserved space is only meant for storing SEP sesam data. If any other data is also stored on the dedicated partition, backup and migration fail even if there is still free space on the partition. See also HWM and LWM.
deduplication
Deduplication is a data compression technique that eliminates redundant blocks of data by not backing up duplicate data. SEP sesam provides two deduplication solutions — offline and online Si3 deduplication. Si3 deduplication is a hybrid of both, target-based (Si3T) and source-based deduplication (Si3S). See SEP Si3 target deduplication and SEP Si3 source-side deduplication.
device
The backup device connected to the SEP sesam Server or SEP sesam Remote Device Server (RDS), used for backing up and recovering client data.
DIFF (D)
A differential backup level in which all data specified by the backup task is backed up (e.g. files). A differential backup records only data which was created or changed after the last FULL save set had been created. See also backup level.
disaster interface (sm_disaster)
One of the SEP sesam configurable interfaces, intended for system administrators. You have to configure this interface to enable the disaster recovery of SEP sesam Server. For details, see Configuration: Disaster Interface. See also interfaces.
disaster recovery
Recovering server data from the save sets after the data was lost due to a disaster. Disaster recovery requires special preparation and configuration. The SEP sesam disaster recovery solutions are Bare Metal Recovery Linux, Bare Metal Recovery MS Windows and SEP sesam Server self-recovery. See also restore.
D2D2T
SEP sesam provides disk-to-disk-to-tape (D2D2T) backup and storage technique where data is initially backed up on a disk and then later copied again on tape. See also virtual tape library.

E

encryption
SEP sesam provides data encryption types on different levels: software-based encryption for save sets (set in the backup task), hardware-based LTO encryption for LTO tape drives (generation 4 and higher), which is done on a media pool level, and Si3 encryption for Si3 deduplication store (set in the Si3 deduplication store properties). For every encryption you must create and store an encryption key. For details, see Software-based Encryption, LTO Encryption and, Encrypting Si3 Deduplication Store.
environment
See SEP sesam environment.
EOL
End of Life (EOL) is a media pool related parameter, based on the media pool retention time that specifies the number of days, for which the data that belongs to the respective media pool is protected. When the protection expires, SEP sesam can re-use the media for backups again. The EOL property can be managed for four object types:
Media pool EOL
The media pool EOL specifies the retention time for save sets written to the respective pool. The save set's EOL is calculated when the data is written to the medium: it starts with the date a save set is created and lasts for the period defined by media pool's EOL. For example, a media pool retention time is 30 days, and the data is backed up to the medium on the 1st of January, therefore the save set's EOL is 31st of January.
Saveset EOL
EOL can be adjusted (extended or reduced) for each individual save set stored on the respective medium (for save sets on tape, see tape media EOL). If the adjusted save set is a part of a backup chain, the whole chain is affected. TheSaveset EOL parameter can be modified under several properties views, for example, by changing the Locked until option in the backup task properties or media properties, or by modifying Saveset EOL (e.g., Components -> Data Store -> Properties -> tab Savesets -> Saveset EOL).
Backup EOL
EOL can also be adjusted for all save sets containing the same data, including migrated and replicated save sets. The Backup EOL parameter can be modified under Components -> Data Store -> Properties -> tab Savesets -> Backup EOL. For example, adjusting backup EOL of a migrated save set from 2.12.2016 to 12.12.2017 results in changed EOL for all related backup data, i.e., original backup, replicated backup, as well as for all backups in a backup chain, if a save set with adjusted backup EOL is a part of it.
Tape media EOL
When a save set is stored on tape, the media EOL (tape's EOL) matches the save set's EOL to prevent deletion of the tape before the save set's EOL is reached. The expiration date of each tape corresponds to the maximum retention time (the longest EOL) identified on tape. Only when all of the save sets on tape have their retention time expired and the tape is no longer locked (write-protected), the entire tape is eligible for re-use. If a tape should be re-used (init) or deleted before the current EOL is reached, the media EOL (identified by tape label) can be manually reduced (note that the reduced EOL is valid for all save sets on tape). If the media EOL date has been reached, but the tape should not be re-used, the media EOL can be increased or the tape can be locked (write-protected).
EOL refers only to backups. SEP sesam logs, readability check logs, calendar sheet entries and restore tasks have separate retention parameters, see retention periods. For more details on media strategy, see Retention time and EOL.
EOM
End of Media (EOM) is a media properties related parameter that specifies whether there is still free space left on the medium or tape. If there is no free space left, the medium or tape is full and can no longer be used for storing data.
event
Every task, which is started by the SEP sesam scheduler based on regular schedules, a single execution of a task, or a task triggered by the end of a previous task or by notification. Event can also be configured as a follow-up event. See also SEPuler.
event priority
When configuring a new event, such as backup, migration, replication or restore, you can also specify the priority of an event. Event priority is used by SEPuler for resolving scheduling conflicts: tasks scheduled for the same execution time are executed according to their priority parameter. The tasks with the highest priority prevail and are executed first, while the execution referring to the same event with lower priorities is suppressed. You can set the priority for each configured event. Default priority level is 1, which is the lowest priority (the highest is 99). SEPuler always executes the schedules with higher priority first. The only exception are the schedules with priority 0 (they are always executed), which override all other priorities and are executed first, but they do not suppress other executions. See also SEPuler.
exclude list
Used to specify patterns to exclude items (files, directories or components, e.g., a VSS writer) that you want to exclude from backup. You can specify the exclude list under the Properties dialog of a backup task: Main Selection window -> Tasks -> By clients -> select backup task -> open Properties. For details on additional exclude options, see Creating Exclude List.

F

file index
A database which stores information on every backed up file, file system and application specific items, such as emails.
follow-up events
Events (migration, save set verify, replication and other actions) that are started on the SEP sesam Server once the initial event is completed. For details, see Follow-up events. See also SEP sesam Client.
frequency
The recurrence of backups and other scheduled tasks performed by SEP sesam. Backup NEWDAY is a daily event set by default when SEP sesam is installed. The task interval is defined in a schedule. See also SEPuler.
FULL (F)
A backup level in which all data specified by the backup task is backed up (e.g. files), regardless of whether it has been changed or not. A save set created as FULL is the basic save set for subsequent DIFF or INCR save sets. See also backup level.
full restore
See complete restore.

G

generation restore
A process by which all generations of backed up files – all files and directories from the backup chain fulldifferentialincremental until the selected save set are displayed and automatically processed for restore. The other restore types are complete restore and selective restore.
granularity level (MS Exchange specific)
Relevant only for SEP sesam version ≤ 4.4.2. A backup parameter, available for MS Exchange Servers, which allows to set the granularity level of items to be backed up and used as a selection criteria for restore. There are three granularity levels: single items (backup of single items, e.g. e-mails, contacts), mailboxes (backup of whole mailboxes), databases (backup of complete Exchange Server mailbox databases). Due to the MS Exchange Server 2013 single item restore limitation, the finest granularity for the MS Exchange Server 2013 is a mailbox folder. For details, see Granularity backup level for Microsoft Exchange Server. As of version 4.4.3, SEP sesam Exchange Recovery Pro supports granular recovery from any Exchange backup. Depending on your SEP sesam version, see one of the following configuration guides for details: Exchange configuration guide for SEP sesam Version 4.4.3.x or Exchange configuration guide for SEP sesam Version 4.4.2.x.
Graphical User Interface (GUI)
SEP sesam GUI provides easy access to configuration and management of SEP sesam and its environment. GUI is platform independent and based on Java. SEP sesam recently introduced additional web interface – SEP sesam dashboard which constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment, see also SEP sesam dashboard. GUI’s options are available according to the type of user. The master GUI is used to administer multiple SEP sesam Server environments from a single location. The GUI description and customization are available at SEP sesam GUI and Customizing GUI. For details on the required Java version, see Java Compatibility Matrix.
guest operating system
An operating system that is installed and runs on a virtual machine.

H

high watermark (HWM)
The upper value for the used disk space on the data store. When this value is reached, a data store purge process is started for all EOL-free save sets. The oldest free save sets are deleted first. Purging is done until the low watermarkis reached.
hot backup (H)
An online backup of VMs and databases: IBM DB2, Informix, Ingres, Microsoft SQL Server, MySQL, Oracle, PostgreSQL. See also cold backup.
HSM-aware solution
A data management software which is aware of the Hierachical Storage Manager (HSM) system. SEP sesam provides HSM-aware backup for Windows from version 4.4.2 onwards. HSM migrates inactive data to lower-cost nearline storage and leaves only stub files in the original location on the primary storage. SEP sesam for Windows recognizes the reparse tags in stub files and performs a backup without retrieving their contents. The backed up stub files can be restored as any other data as long as the restore host has the HSM software installed and can correctly interpret restored reparse points. For details, see HSM-aware Backup for Windows.
hybrid backup solution
SEP sesam can back up all physical and virtual environments and provides data security with local backups as well as backups in the cloud.

I

INCR (I)
An incremental backup level in which all data specified by the backup task is backed up (e.g. files). An incremental backup records all data, which was created or changed after the last FULL, DIFF or INCR save set had been created. See also backup level.
Initial seed
A process of backing up save sets data and metadata stored on a SEP sesam Si3 deduplication store and seeding this data to another Si3 deduplication store, typically to use it to set up new Si3 deduplication store for replication. The backed up data and its metadata are seeded when the Import Si3 store option is used. Seeding the deduplication store serves 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 Seeding Si3 Deduplication Store.
instant VM recovery
A process by which a VMware machine can be started instantly from the backup source, without restoring the data. Instant VM recovery uses vMotion capabilities for live migration of running virtual machines from one physical server to another with no downtime. As of version 4.4.3, SEP sesam provides simple and flexible instant recovery for VMware based on almost any type of VMware backup, including differential and incremental. Using the dedicated GUI option VM single file and instant recovery during backup is no longer required. To learn what applies to instant recovery, which backup type supports it and how it relates to the disk size usage, see SF & IR support matrix. For details on instant VM recovery, see VMware Instant Recovery. See also single item restore.
interfaces
Configurable programs, intended for system administrators. The following interfaces are available: pre (sbc_pre), post (sbc_post), alarm (sm_alarm), disaster (sm_disaster) notify (sm_notify). They can be programmed using any text editor. Before you start using an interface, it has to be activated. Once the interface is activated, it is triggered by certain system events. Interface templates are stored in <SESAM_ROOT>/skel/templates. The templates are activated when they are copied to <SESAM_ROOT>/bin/sesam directory. Interfaces can also be activated in GUI: in the menu bar, click Configuration -> Interfaces. Then click the interface you want to activate, check the interface script, which is opened in a new window, and click Save to activate the interface. The interface is saved to the <SESAM_ROOT>/bin/sesam directory.

J

job
Also called task. An operation that has been scheduled for execution by the SEPuler. Types of jobs are backup, migration, restore, replication and media related actions.
job state
An overview of all executed jobs, sorted by job types. Job status is selected in the Main Selection window -> Job State. Job State -> Results provides details on all jobs, such as job ID, event type (backup, command, migration, restore, etc.), job status (successful or not), object (what was processed), task (its name, job's duration (start and end time), and other details. Job State -> Backups provides detailed information on all backup jobs, including the task name, date of the last full backup, backup type, data size, throughput, assigned media pool, etc. Job State -> Restore displays detailed information on performed restores together with relevant restore information. Job State -> Migrations and Replications displays the properties for each processed migration and replication. Job State -> Media Actions provides an overview of performed media-related actions, such as initialization, readability check, purging, etc. Each status view can be customized by using filter and selection options. For job statistics overview, see SEP sesam dashboard. See also last backup state.

K

key
See encryption.

L

label
An internal identification assigned to a backup volume by backup, which starts with a media pool name and a 5-digit number.
last backup state
Provides an overview of the last backup operations and their status. Last backup state is selected in the Main Selection window -> Monitoring -> Last Backup State. It is useful for tracking the backup jobs that have never been backed up. See also SEP sesam dashboard.
license
Permission to use a SEP sesam solution for a defined period of time. SEP sesam provides various licenses and editions that you can combine according to your needs. The following SEP building blocks are available: SEP sesam Server, SEP GUI, SEP sesam Client, SEP data mover and SEP sesam Remote Device Server, autoloader support, storage pool, database and groupware online modules, SEP services (upgrade, support,...). SEP sesam software and extensions are available at SEP sesam Download Center. See also SEP sesam environment. For details on available licences, see Licensing.
loader
Also called tape library. A device that consists of drive(s), a magazine with slots for media and a robotic mechanism that moves media between the slots and drives. There is no dependency in SEP sesam to use specific manufacturers devices or device types. A list of supported hardware is available at Supported Storage Hardware.
location
A parameter used for logical grouping of the SEP sesam clients. Each client is always created within (and assigned to) a location, which can be defined as a group of clients and further specified as sub-locations. Such grouping enables large organizations in different locations to be managed and represented as a group with separate units (tree-like structure) that are managed centrally. New location can be added in the Main Selection window -> Components -> Topology -> New Location. See also topology.
locked media
See write-protected media.
locked until
Save set and media related EOL parameter. See EOL.
logging
An overview of recorded actions and events for each backup day. Logging view is selected in the Main Selection window -> Logging. It provides the backup status (State) overview in chronological order, records a continuous protocol for each backup day (Day Log), and displays only error messages of the entire day log separately (Error Log). Log files can be printed or sent by email. They are stored in the <SESAM ROOT>/var/prot directory.
logging level
An option that specifies the level of details of the SEP sesam events. To activate logging on clients, use the -v {log_level} under the Expert options in the backup or restore task properties.
low watermark (LWM)
The lower value for the used disk space on the data store. It defines how much storage space is available for save sets with expired EOL. If LWM is set to 0, all EOL-free save sets are removed from the data store. See also high watermark.
LTO
Linear tape open (LTO) is a magnetic tape storage technology that was developed jointly by HP, IBM and Certance (now Quantum Corporation) to provide an alternative standard to proprietary magnetic tape formats. LTO is an open format, which allows for compatible offerings from multiple vendors. The preferred tape format is LTO Ultrium. It is widely used with small and large computer systems for backup and archiving.
LTO encryption
LTO encryption for LTO tape drives is one of the SEP sesam encryption types (also available are Si3 and LTO encryption). It is hardware based encryption for LTO generation 4 and higher. During the LTO encryption process the data files are taken from the server and pass through the SCSI interface to the tape drive. The tape drive then encrypts and compresses the data before it writes it (or decrypts it if reading data) to or from the tape cartridge. SEP sesam supports the LTO encryption of tape drives on a media pool level. For details, see LTO Encryption. See also encryption.

M

machine
Any computer, including file or compute servers.
master GUI
Used as a central management interface for several SEP sesam Servers. The master GUI provides additional options and adjustments that enable the master administrator to access the user interfaces of the other SEP sesam Servers. All local GUIs of the distributed SEP sesam Servers run in parallel and can still be used autonomously. The master GUI description is available at Master GUI. See also Graphical User Interface.
medium (pl. media)
Any medium type (magnetic tape or disk) used for storing backed up data.
media pool
The collection of backup volumes, which are recognized and managed by backup and migration tasks, and identified by the media pool name.
migration
The process which creates an identical copy of the save set data to a newly created save set. Migration can be configured as a follow-up event.
migration task
Used to select a save set and a target media pool for migration.
mount save set
A restore feature available from version 4.4.2. See XPRFS.

N

NDMP
Network Data Management Protocol (NDMP) is a common protocol for backing up and restoring data on storage devices that do not support installation of a backup agent. The NDMP architecture separates the network attached Data Management Application (DMA), data servers and tape servers participating in archival or restore operations. NDMP insures interoperability between NAS file servers and SEP sesam, and is used as an interface that enables SEP sesam to copy data from NAS appliances to SEP sesam Server or Remote Device Server and restore it back to NAS. SEP sesam supports version 4 of the NDMP protocol. See also SEP sesam NDMP. For details on SEP sesam NDMP integration, see NDMP backup.
NDMP host
The host computer system that executes the NDMP Server application. Data is backed up from the NDMP host to backup device on a remote NDMP host. See also SNDMP. For details on SEP sesam NDMP integration, see NDMP backup.
NEWDAY
A predefined SEP sesam daily event, accessible under schedules: Main Selection window -> Scheduling -> Schedules. It resets the event calendar, which is managed by SEPuler. A NEWDAY event is used by SEP sesam to reorder its database and enable undisturbed activity of the SEP sesam processes. It is used to cancel all pending jobs from the previous day and to define a new backup day. For example, if a NEWDAY event is set at 08:00, the backup day is defined from 8:00 AM of the current day to 8:00 AM of the next day. This way the data, which is changed today (day 1), but will only be backed up after midnight (the next day — day 2), is treated according to the actual date change rather than its official time, which would cause the creation of two backups for the same data (one save set for day 1 and another for day 2). The execution time of the NEWDAY event can be modified according to your needs. Note that complete deactivation of a NEWDAY event will cause SEP sesam to stop working properly, since the NEWDAY event also performs other roles related to the SEP sesam processes: it aborts all suspended backup tasks, purges and reorganizes the SEP sesam database, and restarts the SMS and STPD processes. For details, see The SEPuler - an event calendar.
notification
Different types of messages, sent from the SEP sesam Server to all open GUIs. It is also possible to be notified and get alerts in the form of RSS feeds. Notifications inform the user about license violations, non-configured interfaces and include other important information, such as release announcements and error alerts. Notifications can be accessed from the upper right corner of the SEP sesam by clicking the item Notification center. See also notification center and RSS feeds.
notify (sm_notify)
One of the SEP sesam configurable interfaces, intended for system administrators. Notify is executed on the SEP sesam Server. It can be used for reporting on successfully finished events, such as backup, restore, migration, media initialization, and start/finish of a NEWDAY event. Before you start using any of the configurable interfaces, it has to be activated. See interfaces.
notification center
Used to dynamically send messages from the SEP sesam Server to all running GUIs. The notification center is displayed by selecting the Window option in the menu bar -> Show Notification Center. Different types of messages are sent to notify a user of important events and announcements, such as information on latest patch, license violations, non-configured interfaces, and all messages send via RSS feeds. See also RSS feeds. For more details on notifications, see Notification Center.

O

open source license
A license that allows software to be freely used, modified, and/or shared under defined terms and conditions. See also open source module.
open source module
SEP sesam core components, SEP sesam Storage Server and SEP sesam Backup Client (SBC) code, are available under General Public License terms and conditions, allowing users to perform backup and restore of their data.
operator
A person with the operator role that monitors the SEP sesam Server backup status. See user types.
overwrite
The directive to overwrite data during restore, if the same data, e.g. a file, already exists on the target client.

P

package
A SEP sesam collection of installation files for different SEP sesam modules, which can be downloaded from the SEP sesam package repository. See also SEP sesam environment.
parallel backups
Also called Sesam Multiplex Stream. Simultaneously backing up multiple data sources onto one drive. Sesam multiplex streaming is an optimized tape backup which uses parallel backup streams for multiple clients. It allows up to 124 continuous backup data streams for a single drive. Each of 124 channels can serve one backup source. For details, see Parallel Backups. See also Sesam Multiplex Stream Server.
post (sbc_post)
One of the SEP sesam configurable interfaces, intended for system administrators. Post is executed on the SEP sesam Client (note that SEP sesam Server is always a backup client too) and performs additional actions (such as restarting a database, sending emails) after a backup or restore is finished according to the user specified commands. To use a post interface, you have to activate it first and create your own commands. See interfaces.
pre (sbc_pre)
One of the SEP sesam configurable interfaces, intended for system administrators. Pre is executed on the SEP sesam Client (note that SEP sesam Server is always a backup client too) and performs additional actions (such as exporting a database, sending messages) before a backup or restore is started according to the user specified commands. To use a pre interface, you have to activate it first and create your own commands. See interfaces.

Q

queued job
A job that is submitted in the resource queue of SM_QM_MAIN, but not yet started.
queue manager (qm)
A SEP sesam Server service that manages the resources and balances backup and restore jobs.

R

readability check
A process that checks the backup data readability. During the check the data on medium is read in blocks, and the structure of tape is checked and recorded. It also checks whether all determined backup sets on the tape are recorded in the database and vice versa. Readability check is configured by a special media event. For details, see Creating a Media Event.
recovery
See disaster recovery and instant VM recovery.
Remote Device Server (RDS)
See SEP sesam Remote Device Server.
replication
See SEP Si3 replication.
restore
A process that browses for different versions of save sets, and copies data from save sets to a client. Data restore granularity depends on the selected data type. The following restore types are available: complete restore, generation restore, selective restore. For VMware vSphere, single item restore is available. See also disaster recovery and XPRFS.
restore task
Used to configure a restore of data from save sets to a client. A restore task always contains browsing and selecting the desired save sets by time and task/filename, selecting restore type and restore target, for example file system folder. You can configure a restore task using a restore wizard: in the menu bar, click Activities -> Restore.
retention periods
The time period for which the SEP sesam retains SEP sesam logs, readability check logs, calendar sheet entries and restore tasks. Once the retention period expires, the data is removed from the database and is no longer available. You can modify retention periods for each item separately: in the menu bar, click Configuration -> Defaults -> Retention Periods.
retention time
Retention time is set for media pool and is applied to all media in the respective media pool. It specifies the time period for which the media are protected after data is written to the medium, thus preserving the save sets and keeping them available for restore. The retention time period starts with the date a save set is written to the media and lasts for the period defined by media pool's EOL (in days). Once the retention time expires, the media are writable again. The retention time is defined when configuring a new media pool: Main Selection window ->Components -> Media Pools -> New Media Pool, or when editing the selected media pool Properties. You can also extend or shorten the expiration date of a specific save set or of all backup-related data by adjusting EOL. See also EOL. In addition, you can use software tape protection to write-protect tape media. See also write-protected media.
RSS feeds
Used to inform about new releases and features (version-specific). Subscription is available online at SEP sesam Notification Center: notification/sepsoftware.com. Current versions of web browsers, such as Firefox or Internet Explorer, allow to directly import and read SEP sesam RSS events. Alternatively, it is possible to subscribe to the SEP sesam RSS feeds with your preferred RSS feed reader. Selecting one of the links opens the RSS feed in the default web browser of the GUI client. See also notification center and notification.

S

save set
A set of data, such as files and directories, copied onto backup medium by backup or migration. The time period for which a save set is preserved is defined by the retention time. You can verify save sets after the backup is finished by configuring a follow-up event.
save set EOL
See EOL.
save set ID
An internal unique identification assigned to a save set.
schedule
Used for setting events to occur at a specific time. You can set up any kind of task to occur at a specific time, such as backup, migration or restore, thus automating the task execution. When setting up a task, among other parameters a start time, time interval and event priority have to be specified. Schedules always contain one predefined task: a NEWDAY schedule. You can explore and edit the existing schedules or set up new ones: Main Selection window ->Scheduling -> Schedules. As of SEP sesam v. 4.4.3, a new option User defined allows you to create a custom calendar. For more information on schedules and calendars, see About Scheduling. See also SEPuler.
selective restore
A process by which only the selected parts of data on the save set, such as individual files and directories, are restored. The other restore types are complete restore and generation restore.
SEP EasyArchive (SEA)
As of SEP sesam 4.4.3, this module is no longer supported. A policy-based integrated archival solution, which converts NTFS partitions into WORM drives. Data is archived for a specified amount of time using the predetermined data store. Archived data can be easily accessed by authorized users, it can be encrypted and deduplicated. Data can be stored on disk, tape or off-loaded to a cloud store. SEP EasyArchive requires a SEA license. See also SEP sesam extensions.
SEP FDS VA
As of SEP sesam 4.4.3, this module is no longer supported. SEP File Deduplication System Virtual Appliance is an offline block-level deduplication solution, powered by FalconStor®. It provides a space-efficient repository for the SEP sesam data stores. SEP FDS VA works as a SEP sesam Remote Device Server. It includes 1 TB of repository capacity (requires one repository capacity license), but is expandable up to 5 TB. For details, see SEP FDS VA Deduplication Appliance. See also SEP Si3 target deduplication and SEP sesam extensions.
SEP sesam Client (SBC)
A system that has a SEP sesam Client package installed, is added to the SEP sesam environment as a client and is included for data protection in the backup plans. Clients may be workstations, PCs, virtual machines or file servers with gigabytes of data. The abbreviation SBC (sesam backup client) is used in a more technical sense for programs, which are executing backup, migration and restore tasks. SBC collects and consolidates the backup data on the client system, and delivers it to STPD. The SBC module can be controlled directly without other SEP modules by using SEP sesam SBC_CLI. See also SEP sesam environment.
SEP sesam dashboard
A web dashboard is an online monitoring tool that constantly tracks SEP sesam operations and their state and provides key metrics of the SEP sesam environment. It provides information on backups and restores per server, client or application over time; daily, weekly, monthly or custom statistics on event; overview of total size of backed up and restored data and on data store utilization. The web reports can be filtered by events, clients and state and used for an overview of up-coming events. For details, see SEP sesam Dashboard.
SEP sesam Data Management Application (SDMA)
A NDMP session master that is responsible for initiating and managing backup and restore operations of NDMP compliant systems. SDMA serves as a remote NDMP client, which establishes and manages connection and communication between the source and the destination NDMP data services. It uses NDMP control connection to issue commands to the servers and NDMP data connection for the data stream, thus ensuring fast and efficient communication between the remote services. See also SEP sesam NDMP.
SEP sesam data mover (SDM)
A functional role allowing access to a third-party software API. Depending on a third-party software, a data mover role can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or a client. The following data mover types are available: SEP sesam data mover for VMware vSphere (SDM-VV), for Citrix XenServer (SDM-CX), for Novell Services (SDM-NS), and for NetApp (SDM-NA). For details, see What is a SEP sesam data mover.
SEP sesam environment
A complete SEP sesam environment consists of different modules, which can be combined according to your needs to implement optimized backup. Modules interact with one another through SEP APIs, also used for interaction with another software. Each module is installed separately. Essential modules of each SEP sesam environment are: SEP sesam Server, SEP sesam GUI, SEP sesam Remote Device Server, SEP sesam Client(s), and optionally other modules represented as the SEP sesam extensions. The SEP sesam environment is managed centrally by the SEP sesam GUI.
SEP sesam extensions
Additional modules and functionality that provide consistent backup of databases (Oracle, MS SQL, IBM DB2, Informix, SAP R/3, etc.), applications (like SAP), groupware systems, and virtualization environments. For list of all supported extensions, see Extensions. For details on supported extensions, see SEP sesam OS and Database Support Matrix.
SEP sesam NDMP (SBC_NDMP)
A system that has a SEP sesam NDMP backup package installed on a data mover to provide NDMP remote configuration where the data from NDMP host is backed up and transferred over a TCP/IP connection to SEP sesam Server's connected storage, e.g., disk storage or virtual tape library. SBC_NDMP consist of SEP sesam Data Management Application – SDMA, which is responsible for initiating and managing backup and restore operations of NDMP compliant systems, and SEP sesam NDMP host – SNDMP, which provides the interface to the SEP sesam storage. See also NDMP. For details on SEP sesam NDMP integration, see NDMP Backup.
SEP sesam Remote Device Server (RDS)
RDS is a storage management component that receives data during backup and writes it to the appropriate store (either to the data store or to the attached tape device). During a restore it locates the save sets and sends the data to a client. RDS consists of four components: Sesam Transfer Protocol Server (STPD), Sesam Multiplex Stream Server (SMS), and SEP sesam Client (SBC) and a remote access. The control of the tasks is maintained by the SEP sesam Server. When relating to open source modules, RDS is also called SEP sesam Storage Server.
SEP sesam Server
The server system with installed SEP sesam Server software, containing the SEP sesam database together with indexes, and providing backup and other data protection related services for one or more clients on a network. SEP sesam Server is always a SEP sesam Client and usually also a RDS. Server module can be installed on any server or workstation (Linux, Windows, etc.). For details, see SEP sesam OS and Database Support Matrix. See also SEP sesam environment.
SEP sesam Storage Server
See SEP sesam Remote Device Server.
SEP Si3 deduplication store
Special type of data store, required for both Si3 deduplication methods, target-based (Si3T) and source-based (Si3S) deduplication. As of 4.4.3 Tigon, it is possible to use initial seed for setting up new Si3 deduplication store for replication; additionally, deduplication store provides Si3 encryption. For details, see Configuring an Si3 Deduplication Store.
SEP Si3 replication
A solution that consistently replicates data between the SEP sesam Server and SEP sesam Remote Device Server. Replication means that only changed data blocks are sent over a network and backed up to the target server according to defined schedule. It is used together with Si3 deduplication. Original deduplication store can be seeded to provide the basis for new deduplication store for replication. A replication task can be configured under Tasks: Main selection -> Tasks -> Si3 replications -> New replication task. Replication can be configured as a follow-up event. For details, see Replication.
SEP Si3 source-side deduplication (Si3S)
Introduced in SEP sesam 4.4.3, this inline block-level data deduplication solution deduplicates data before it is sent across the network and backed up. SEP sesam calculates hashes of data to be backed up on the client and then transfers only changed or unknown blocks of the target Si3 dedup store to the RDS. Source-side deduplication requires a configured Si3 deduplication store, for which a special license is needed. For more details, see Source Side Dedup and Configuring an Si3 Deduplication Store. See also SEP Si3 target deduplication.
SEP Si3 target deduplication
An inline block-level data deduplication solution that writes data directly from the SEP sesam Server or SEP sesam Remote Device Server to the backup media. It can be used together with replication to provide backup redundacy for disaster recovery and reduce the data transferred over the network. SEP Si3 target deduplication is easily configured and ready to use by selecting Si3 deduplication data store type: Main Selection -> Components -> Data Stores -> New Data Store-> Store Types ->SEP Si3 Deduplication Store. Si3 target deduplication requires a configured Si3 deduplication store, for which a special license is needed. For details, see Configuring an Si3 Deduplication Store. See also SEP Si3 source-side deduplication.
SEPuler
A process that controls scheduling of the SEP sesam backup and restore tasks. It is constantly checking for backup, restore and other predefined tasks to be executed. When such a task is found, a SEPuler initiates the execution of the event. Once the event is started, SEPuler determines the next execution event for a cyclical backup/restore task and rewrites the event to the event calendar. Every configured task is automatically recorded by SEPuler. A schedule is used for any number of events, and a particular task (backup, restore, etc.) can have events in several schedules. To prevent possible tasks conflicts and efficiently manage tasks in execution queue, SEP sesam uses the event priorities. The event calendar provides overview of all, scheduled and the expired events: Main Selection window -> Scheduling -> Calendar Sheet. For details, see The SEPuler - an event calendar. See also calendar sheet and schedule.
Sesam day
See backup day.
Sesam Multiplex Stream (SMS) Server
A service that receives the backup data from STPD and writes the data to the backup media. During a restore it reads the data from the backup media and sends it to STPD.
SNDMP
A SEP sesam NDMP host that provides an interface to the SEP sesam storage. During backup, it writes a data stream to the SEP sesam Server or SEP sesam Remote Device Server. During restore, it reads content from data storage and converts it into a data stream in an NDMP data connection, which is managed by SDMA. SNDMP is able to use SEP sesam backup architecture – RDS, SEP sesam devices, Si3 deduplication stores – to store and retrieve NDMP host backup data. See also SEP sesam NDMP.
Sesam Transfer Protocol Server (STPD)
A service that requests the backup data from the SMS Server and manages the data flow between the SEP sesam Server and a client. STPD delivers the backup data to SMS Server. During a restore STPD receives the data from SMS Server and sends it to the SEP sesam Client, which then restores the data to the target system.
single file restore
See XPRFS and single item restore (VMware specific).
single item restore (VMware specific)
A process by which only a single file is restored from a virtual machine, without having to restore the complete save set. A single item can be restored from a vSphere backup either by a attaching VMDK to a virtual machine (this is a recommended option) or by mounting VMDK to a device server. As of version 4.4.3, SEP sesam provides simple and flexible single file restore for VMware based on almost any type of VMware backup, including differential and incremental. Using the dedicated GUI option VM single file and instant recovery during backup is no longer required. To learn what applies to single file restore, which backup type supports it and how it relates to the disk size usage, see SF & IR support matrix. For details on restore procedure, see VMware Single File Restore. See also instant VM recovery.
Si3 encryption
Si3 encryption for Si3 deduplication store store is one of the SEP sesam encryption types (also available are software-based and LTO encryption). SEP sesam provides encryption for Si3 deduplication to help ensure compliance with data protection legislation. Si3 encryption is set by creating the deduplication security password file. The administrator can set an arbitrary encryption key, which is only known to the SEP sesam Server. If the encryption key is not available, the Si3 encrypted data cannot be read. For details, see Encrypting Si3 Deduplication Store. See also encryption.
software-based encryption
Software-based encryption for save sets is one of the SEP sesam encryption types (also available are LTO and Si3 encryption). It is configured on a backup task level: Main Selection -> Tasks -> By clients -> select a client and a task -> double-click to open the task properties -> select Encryption & Compression tab. Supported software-based encryption algorithms are the Advanced Encryption Standard (AES) 256-bit encryption and the Blowfish encryption. For details, see Software-based encryption. See also encryption.
source
The data source specified in backup or migration tasks.
super-user
A UNIX user with root privileges or a Windows user with administrator rights.
system administrator
The person responsible for installing, configuring, and maintaining the backup solution.
system state backup
Backup of all Windows system state components as a unit by using Microsoft Volume Shadow Copy Service (VSS). In previous SEP sesam versions, the system state backup was available under the name System_recovery. As of 4.4.3, system state backup option is renamed to System_state without change in functionality. For details on system state backup, see Backing up System State.

T

task
Execution of a SEP sesam backup, migration, replication, restore or command task.
task group
A group of tasks used for scheduling.
target
A specified location for backup/migration of restored data, for example a different media pool (migration) or a folder (restore) on a client.
topology
Represents the SEP sesam backup environment including the hardware, computers, backup devices, etc. See also SEP sesam locations, clients and servers.

U

user-defined dates
A schedule option, used to set up a custom calendar. It allows you to create a calendar which is customized according to your country or company specific requirements. You can define specific dates in the schedule properties: Main Selection window -> Scheduling -> Schedules -> User defined tab. For details, see Creating a custom calendar.
user's permissions
The permissions or access rights granted according to user types. They define which users can perform specific SEP sesam operations. Authentication module is used to grant and restrict access to SEP sesam Server. For details, see Authentication.
user types
SEP sesam user types are admin, operator and restore. The admin is the only user role with full control over the SEP sesam. The operator monitors the SEP sesam Server backup status. The restore user is only allowed to start restores. The displayed GUI components depend on the user type. See also Graphical User Interface, user view and authentication.
user view
Available for v. ≤ 4.4.3. Used for adjusting the GUI display according to the user type: in the menu bar, click Configuration -> User view. By switching the view from admin to operator, certain SEP sesam GUI elements (Components, Tasks and Scheduling) are disabled.

V

vendor independent solution
A disclosure of the SEP sesam backup format provides independence from software vendors by providing the users with untroubled access to company data without any other license requirements. See also open source module.
VFSL
Virtual file system layer (VFSL) is a feature that allows you to explore (view, browse, copy or restore) individual files and folders. It is similar to XPRFS, see XPRFS for further details.
virtual tape library (VTL)
A software appliance that emulates a traditional tape library and provides additional data storage component for backup solution.
virtualization support
SEP sesam provides backup and restore for virtual platforms, including VMware, Citrix XenServer, XEN and Hyper-V.
VM
A virtual machine.
VMDK
A virtual disk file that stores the contents of the VM's hard disk drive.
VSS
Volume Shadow Copy Service is a Windows service that allows taking snapshots of computer files or volumes, even when they are in use. SEP sesam uses only the VSS components, which are provided by Microsoft.

W

watermark
A parameter used for data store configuration. See high watermark and low watermark.
write-protected media
A special option Write Protection is used for setting additional software protection for individual tape medium. You can write-protect particular tapes by setting this option ON manually: Main Selection window -> Components -> Media -> column Write Protection (On/Off). This option overrides retention time of the media pool as well as any individually adjusted EOL and sets permanent protection for save sets on tape. Write-protected tape media cannot be recycled until their protection is ON. You can switch it off manually at any time. When a tape is no longer write-protected, the retention time period of the media pool applies. See also EOL and retention time.

X

XBSA
X/Open Backup Services API is used by the SEP sesam backup module to connect to Sesam Transfer Protocol Server (STPD) to send or retrieve data from Sesam Multiplex Stream Server (SMS).
XPRFS
Cross-platform recovery file system layer (XPRFS) is an advanced restore feature that allows for mount and restore onto different operating systems and hardware platforms (Windows – MTF <–> Linux/Unix – cpio). It can be used to mount any non-compressed save set stored to Path or Si3 data store, thus enabling single file restore. It is recommended for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups to achieve faster restore time and performance. For details, see XPRFS. See also VFSL.