SEP sesam Glossary: Difference between revisions

From SEPsesam
(Added link.)
(Corrected link for UI mode.)
(23 intermediate revisions by the same user not shown)
Line 22: Line 22:
|<translate>
|<translate>
<!--T:166-->
<!--T:166-->
{{anchor|access mode}}'''access mode'''||Defines the communication method and access type between the [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]] and the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]]. The following access modes are available:  ''CTRL'', ''SM_SSH'' (SEP sesam SSH based control communication), ''PROXY'' (available vendor-specific protocols are: vSphere (vCenter Server), Citrix XenServer, NetApp and Novell SMS for NetWare 5.1/6.0/6.5), ''SSH'' (Secure Shell), and ''RSH'' (Remote Shell). As of [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']], the default access mode is ''SM_SSH''. Access mode is defined in the ''Client Properties'' dialog. For details, see [[Special:MyLanguage/Step_2:_Clients_4.4|client properties]].</translate>
{{anchor|access mode}}'''access mode'''||Defines the communication method and access type between the [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]] and the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]]. The following access modes are available:  ''CTRL'', ''SM_SSH'' (SEP sesam SSH based control communication), ''PROXY'' (available vendor-specific protocols are: vSphere (vCenter Server), Citrix XenServer, NetApp and Novell SMS for NetWare 5.1/6.0/6.5), ''SSH'' (Secure Shell), and ''RSH'' (Remote Shell). As of [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']], the default access mode is ''SM_SSH''. Access mode is defined in the ''Client Properties'' dialog. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Step_2:_Clients|client properties]].</translate>
|-
|-
|<translate>
|<translate>
Line 38: Line 38:
|<translate>
|<translate>
<!--T:170-->
<!--T:170-->
{{anchor|alarm}}'''alarm (sm_alarm)'''||One of the SEP sesam configurable interfaces intended for system administrators. Alarm is executed on the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|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 [[Special:MyLanguage/SEP_sesam_Glossary#interfaces|interfaces]].</translate>
{{anchor|alarm}}'''alarm (sm_alarm)'''||One of the SEP sesam configurable interfaces intended for system administrators. Alarm is executed on the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]] to warn the system administrator when a fatal error occurs or in case of a license violation. It can only be used if it has been activated before. See [[Special:MyLanguage/SEP_sesam_Glossary#interfaces|interfaces]].</translate>
|-
|-
|<translate>
|<translate>
Line 97: Line 97:
|-
|-
|<translate><!--T:339-->
|<translate><!--T:339-->
{{anchor|software_based}}{{anchor|backup-task}}'''backup-task encryption'''||Backup-task encryption for [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] is one of the SEP sesam encryption types (also available are [[Special:MyLanguage/SEP_sesam_Glossary#LTO_encryption|LTO]] and [[Special:MyLanguage/SEP_sesam_Glossary#Si3_encryption|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 backup-task encryption algorithms are the Advanced Encryption Standard (AES) 256-bit encryption and the Blowfish encryption. For details, see [[Special:MyLanguage/The_Backup_4.4#encryption|Backup-task encryption]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#encryption|encryption]].</translate>
{{anchor|software_based}}{{anchor|backup-task}}'''backup-task encryption'''||Backup-task encryption for [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] is one of the SEP sesam encryption types (also available are [[Special:MyLanguage/SEP_sesam_Glossary#LTO_encryption|LTO]] and [[Special:MyLanguage/SEP_sesam_Glossary#Si3_encryption|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 backup-task encryption algorithms are the Advanced Encryption Standard (AES) 256-bit encryption and the Blowfish encryption. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Backup#encryption|Backup-task encryption]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#encryption|encryption]].</translate>
|-
|-
|<translate><!--T:186-->
|<translate><!--T:186-->
Line 126: Line 126:
|-
|-
|<translate><!--T:194-->
|<translate><!--T:194-->
{{anchor|clean_up}}'''clean up'''||A process of cleaning up orphaned [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] from the [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data stores]] manually, thus releasing the space that might be occupied by orphaned savesets. You can clean up data store in the ''Data Stores'' content pane menu: Main Selection window -> ''Components'' -> ''Data Stores'' content pane -> option ''Clean up''. For more details, see [[Special:MyLanguage/The_DataStore_4.4#clean_up|Clean up orphaned savesets]].</translate>
{{anchor|clean_up}}'''clean up'''||A process of cleaning up orphaned [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] from the [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data stores]] manually, thus releasing the space that might be occupied by orphaned savesets. You can clean up data store in the ''Data Stores'' content pane menu: Main Selection window -> ''Components'' -> ''Data Stores'' content pane -> option ''Clean up''. For more details, see [[Special:MyLanguage/4_4_3_Beefalo:Data_Store#clean_up|Clean up orphaned savesets]].</translate>
|-
|-
|<translate><!--T:195-->
|<translate><!--T:195-->
Line 156: Line 156:
|-
|-
|<translate><!--T:204-->
|<translate><!--T:204-->
{{anchor|custom calendar}}'''custom calendar'''||Can be specified by using a schedule option ''User defined''. The custom calendar can be used to prevent scheduled tasks such as backup, migration or replication (see [[Special:MyLanguage/The_SEPuler_-_an_event_calendar_4.4#blocking_events|blocking date]]) or to perform special tasks. For example, scheduled backups can be blocked on certain days, such as public holidays. Should such an event overwrite another, [[Special:MyLanguage/SEP_sesam_Glossary#event priority|event priority]] must be defined higher. You can create a custom calendar in the schedule properties: Main Selection window ->''Scheduling'' -> ''Schedules'' -> ''User defined'' tab. For details, see [[Special:MyLanguage/Creating Custom Calendar|Creating a custom calendar]]. You are able to [[Special:MyLanguage/Modifying a Calendar|modify]], [[Special:MyLanguage/Importing a Calendar|import]], [[Special:MyLanguage/Exporting a Calendar|export]] and [[Special:MyLanguage/Deleting a Calendar|delete]] a calendar.</translate>
{{anchor|custom_calendar}}'''custom calendar'''||Can be specified by using a schedule option ''User defined''. The custom calendar can be used to prevent scheduled tasks such as backup, migration or replication (see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#blocking_events|blocking date]]) or to perform special tasks. For example, scheduled backups can be blocked on certain days, such as public holidays. Should such an event overwrite another, [[Special:MyLanguage/SEP_sesam_Glossary#event priority|event priority]] must be defined higher. You can create a custom calendar in the schedule properties: Main Selection window ->''Scheduling'' -> ''Schedules'' -> ''User defined'' tab. For details, see [[Special:MyLanguage/Creating_a_Custom_Calendar|Creating a Custom Calendar]].</translate>
|-
|-
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:205-->
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:205-->
Line 175: Line 175:
|-
|-
|<translate><!--T:211-->
|<translate><!--T:211-->
{{anchor|data_store}}'''data store'''||A device type used for writing the [[Special:MyLanguage/SEP_sesam_Glossary#save_set|savesets]] directly on one or several configured storage locations — into the file system. Data store configuration consists of specifying [[Special:MyLanguage/SEP_sesam_Glossary#data store capacity|data store capacity]] and watermarks: [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]] and [[Special:MyLanguage/SEP_sesam_Glossary#LWM|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 [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP Si3 deduplication store]]. As of SEP sesam version 4.4.3, [[Special:MyLanguage/SEP_sesam_Glossary#SEA|SEP EasyArchive]] data store and [[Special:MyLanguage/SEP_sesam_Glossary#SEP_FDS|FDS deduplication store]] are no longer supported. Data store is [[Special:MyLanguage/SEP_sesam_Glossary#purge|purged]] automatically based on [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]]. It is also possible to purge the data store or [[Special:MyLanguage/SEP_sesam_Glossary#clean_up|clean up]] orphaned savesets manually. For more details, see [[Special:MyLanguage/The_DataStore_4.4|Data Store]].</translate>
{{anchor|data_store}}'''data store'''||A device type used for writing the [[Special:MyLanguage/SEP_sesam_Glossary#save_set|savesets]] directly on one or several configured storage locations — into the file system. Data store configuration consists of specifying [[Special:MyLanguage/SEP_sesam_Glossary#data store capacity|data store capacity]] and [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]] (note that low watermark is obsolete). 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 [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP Si3 deduplication store]]. As of SEP sesam version 4.4.3, [[Special:MyLanguage/SEP_sesam_Glossary#SEA|SEP EasyArchive]] data store and [[Special:MyLanguage/SEP_sesam_Glossary#SEP_FDS|FDS deduplication store]] are no longer supported. Data store is [[Special:MyLanguage/SEP_sesam_Glossary#purge|purged]] automatically based on [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]]. It is also possible to purge the data store or [[Special:MyLanguage/SEP_sesam_Glossary#clean_up|clean up]] orphaned savesets manually. For more details, see [[Special:MyLanguage/4_4_3_Beefalo:Data_Store|Data Store]].</translate>
|-
|-
|<translate><!--T:212-->
|<translate><!--T:212-->
{{anchor|data store capacity}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]] and [[Special:MyLanguage/SEP_sesam_Glossary#LWM|LWM]]</translate>
{{anchor|data_store_capacity}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]].</translate>
|-
|-
|<translate><!--T:213-->
|<translate><!--T:213-->
Line 190: Line 190:
|-
|-
|<translate><!--T:216-->
|<translate><!--T:216-->
{{anchor|disaster}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]]. For details, see [[Special:MyLanguage/Configuration_4.4#disaster|Configuration: Disaster Interface]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#interfaces|interfaces]].</translate>
{{anchor|disaster}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]]. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Configuration#disaster|Configuration: Disaster Interface]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#interfaces|interfaces]].</translate>
|-
|-
|<translate><!--T:217-->
|<translate><!--T:217-->
Line 203: Line 203:
|-
|-
|<translate><!--T:220-->
|<translate><!--T:220-->
{{anchor|encryption}}'''encryption'''||SEP sesam provides data encryption types on different levels: [[Special:MyLanguage/SEP_sesam_Glossary#backup-task|backup-task encryption]] for savesets (set in the backup task), [[Special:MyLanguage/SEP_sesam_Glossary#Si3_encryption|Si3 encryption]] for Si3 deduplication store (set in the Si3 deduplication store properties), and hardware-based [[Special:MyLanguage/SEP_sesam_Glossary#LTO_encryption|LTO encryption]] for LTO tape drives (generation 4 and higher), which is done on a media pool level. For every encryption you must create and store an encryption key. For details, see [[Special:MyLanguage/The_Backup_4.4#encryption|Backup-Task Encryption]], [[Special:MyLanguage/LTO_Encryption|LTO Encryption]] and, [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]].</translate>
{{anchor|encryption}}'''encryption'''||SEP sesam provides data encryption types on different levels: [[Special:MyLanguage/SEP_sesam_Glossary#backup-task|backup-task encryption]] for savesets (set in the backup task), [[Special:MyLanguage/SEP_sesam_Glossary#Si3_encryption|Si3 encryption]] for Si3 deduplication store (set in the Si3 deduplication store properties), and hardware-based [[Special:MyLanguage/SEP_sesam_Glossary#LTO_encryption|LTO encryption]] for LTO tape drives (generation 4 and higher), which is done on a media pool level. For every encryption you must create and store an encryption key. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Backup#encryption|Backup-Task Encryption]], [[Special:MyLanguage/LTO_Encryption|LTO Encryption]] and, [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]].</translate>
|-
|-
|<translate><!--T:221-->
|<translate><!--T:221-->
Line 209: Line 209:
|-
|-
|<translate><!--T:222-->
|<translate><!--T:222-->
{{anchor|EOL}}'''EOL'''||End of Lifetime (EOL) is a media pool related parameter, based on the media pool [[Special:MyLanguage/SEP_sesam_Glossary#retention_time|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. As of v. 4.4.3 [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']], modified EOL is recorded in main log. Note that SEP sesam provides dependency-based retention strategy performed by automated EOL adjustment; this behavior depends on the SEP sesam version (e.g., the last successful backup or migration is not retained in version [[Special:MyLanguage/SEP sesam Release Versions|4.4.3.42 Tigon]], but it is retained by default in [[Special:MyLanguage/SEP sesam Release Versions|4.4.3.47 Tigon V2]]). For details, see [[Special:MyLanguage/Managing_EOL#last_successful_bck|Managing EOL]].<br />
{{anchor|EOL}}'''EOL'''||End of Lifetime (EOL) specifies the time until which the backed up data on media remains protected and thus defines the expiration date of the backup data. The EOL of a saveset is defined by the date the data is written to the media and the [[Special:MyLanguage/SEP_sesam_Glossary#retention_time|retention time]] (in days) of the media pool to which the media belongs. Once the EOL of all savesets stored on media has expired, the media can be rewritten. Note that SEP sesam provides dependency-based retention strategy performed by automated EOL adjustment. This means that EOL is automatically adjusted for savesets that, for example, belong to the same backup chain, in order to enable to enable complete restore of data. As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], it is possible to customize retention policy by inserting or modifying [[Special:MyLanguage/SEP_sesam_Glossary#EOL_key|EOL-related keys]]. EOL behaviour may be release-dependent. For details, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].<br />
The EOL property can be managed for four object types:
The EOL property can be managed for three object types:  
:;Media pool EOL: Media pool EOL specifies the retention time (in days) for savesets written to the respective pool. The ''saveset EOL'' is calculated when the data is written to the medium: it starts with the date a saveset is created and lasts for the period defined by media pool's retention time. For example, a media pool retention time is 30 days, and the data is backed up to the medium on the 1<sup>st</sup> of January, therefore the ''saveset EOL'' is 31<sup>st</sup> of January.
:;Saveset EOL: This is the expiration date for each individual saveset (for savesets that are stored on tape, see also [[Special:MyLanguage/SEP_sesam_Glossary#tape_EOL|tape media EOL]]). The ''saveset EOL'' is calculated from the time the data is written to the medium using the following formula: ''expiration = creation date + the retention time of the media pool''. For example, a media pool retention time is 30 days and the data is backed up to the medium on the 1<sup>st</sup> of January, therefore the ''saveset EOL'' is 31<sup>st</sup> of January. ''Saveset EOL'' can be adjusted for each individual saveset. If a saveset is part of a backup chain, its EOL follows the rules of dependency-based retention, as described in [[Special:MyLanguage/Managing_EOL#dependency-based retention|Managing EOL]]. The '''''Saveset EOL''''' parameter can be checked and modified under all media-related views, e.g., in the ''Media'', ''Media Pools'' and ''Data Stores'' properties (''Savesets'' tab -> ''Saveset EOL''), or whenever a task with the savesets is displayed. For details on automated and manual EOL adjustment, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].  
:;Saveset EOL: This is the expiry date for each individual saveset (for savesets that are stored on tape, see also [[Special:MyLanguage/SEP_sesam_Glossary#tape_EOL|tape media EOL]]). ''Saveset EOL'' can be adjusted (extended or reduced) for each individual saveset. If a saveset is a part of a backup chain, its EOL follows the rules of dependency-based retention, as described in [[Special:MyLanguage/Managing_EOL#dependency-based retention|Managing EOL]]. The '''''Saveset EOL''''' parameter can be checked and modified under several properties views, for example, by changing the ''Locked until'' option in the media properties, or by modifying ''Saveset EOL'' (e.g., ''Components'' -> ''Data Store'' -> ''Properties'' -> tab ''Savesets'' -> ''Saveset EOL'' or ''Job State'' -> ''Backups'' -> ''Properties''). For details on automated and manual EOL adjustment, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].
:;Backup EOL:This is the expiration date for all data that belong to the same backup, including migrated and replicated savesets. It is based on the longest EOL of all savesets that belong to the same backup and follows the rules of dependency-based retention, as described in [[Special:MyLanguage/Managing_EOL#dependency-based retention|Managing EOL]]. The ''''' Backup EOL''''' parameter can be modified under all media-related views, e.g., in the ''Media'', ''Media Pools'' and ''Data Stores'' properties (''Savesets'' tab -> ''Backup EOL''), or  whenever a task with the savesets is displayed.
:;Backup EOL:This is the expiry date for all data that belongs to the same backup, including migrated and replicated savesets. It is based on the longest EOL of all savesets that belong to the same backup and follows the rules of dependency-based retention, as described in [[Special:MyLanguage/Managing_EOL#dependency-based retention|Managing EOL]]. The ''''' Backup EOL''''' parameter can be modified under ''Components'' -> ''Data Store'' -> ''Properties'' -> tab ''Savesets'' -> ''Backup EOL''. EOL behaviour may be release-dependent. For details, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].
:;{{anchor|tape_EOL}}Tape media EOL: When a saveset is stored on tape, every stored saveset has its own ''saveset EOL''. The expiration date of the tape, which is the tape media EOL, is defined by the maximum expiration date (the longest EOL) identified on the tape. Only when all of the savesets on tape have their retention time expired and the tape is not locked ([[Special:MyLanguage/SEP_sesam_Glossary#write-protected|write-protected]]), the entire tape is eligible for re-use. Tape media EOL can also be manually extended or reduced. For more details, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].
:;{{anchor|tape_EOL}}Tape media EOL: When a saveset is stored on tape, every stored saveset has its own ''saveset EOL'', but this does not represent the actual expiration date of the tape. Its expiration date corresponds to the maximum retention time (the longest EOL) identified on tape. Only when all of the savesets on tape have their retention time expired and the tape is not locked ([[Special:MyLanguage/SEP_sesam_Glossary#write-protected|write-protected]]), the entire tape is eligible for re-use. Tape media EOL can also be manually extended or reduced. For more details, see [[Special:MyLanguage/Managing_EOL|Managing EOL]].  


<!--T:223-->
<!--T:223-->
:EOL refers only to backups. SEP sesam logs, readability check logs, calendar sheet entries and restore tasks have separate retention parameters, see [[Special:MyLanguage/SEP_sesam_Glossary#retention_periods|retention periods]]. For more details on EOL and media strategy, see [[Special:MyLanguage/Managing_EOL|Managing EOL]] and [[Special:MyLanguage/Media_Strategy_4.4#protection|Retention time and EOL]].</translate>
:EOL refers only to backups and related migrated and replicated savesets. SEP sesam logs, readability check logs, calendar sheet entries and restore tasks have separate retention parameters, see [[Special:MyLanguage/SEP_sesam_Glossary#retention_periods|retention periods]].</translate>
|-
|<translate>
<!--T:375-->
{{anchor|EOL_key}}'''EOL-related keys'''||Depending on SEP sesam version, EOL-related parameters may be used to change the default [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL policy]] (backup retention behaviour) by modifying EOL-related keys in the global settings in GUI. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Managing_EOL#keys|Customizing retention policy]].</translate>
|-
|-
|<translate><!--T:224-->
|<translate><!--T:224-->
Line 300: Line 303:
|-
|-
|<translate><!--T:248-->
|<translate><!--T:248-->
{{anchor|interfaces}}'''interfaces'''||Configurable programs, intended for system administrators. The following interfaces are available: [[Special:MyLanguage/SEP_sesam_Glossary#pre|pre]] (sbc_pre), [[Special:MyLanguage/SEP_sesam_Glossary#post|post]] (sbc_post), [[Special:MyLanguage/SEP_sesam_Glossary#alarm|alarm]] (sm_alarm), [[Special:MyLanguage/SEP_sesam_Glossary#disaster|disaster]] (sm_disaster) [[Special:MyLanguage/SEP_sesam_Glossary#notify|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 <tt><SESAM_ROOT>/skel/templates</tt>. The templates are activated when they are copied to <tt><SESAM_ROOT>/bin/sesam</tt> 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 <tt><SESAM_ROOT>/bin/sesam</tt> directory. For details, see [[Special:MyLanguage/Configuration_4.4#interfaces|SEP sesam Interfaces]].</translate>
{{anchor|interfaces}}'''interfaces'''||Configurable programs, intended for system administrators. The following interfaces are available: [[Special:MyLanguage/SEP_sesam_Glossary#pre|pre]] (sbc_pre), [[Special:MyLanguage/SEP_sesam_Glossary#post|post]] (sbc_post), [[Special:MyLanguage/SEP_sesam_Glossary#alarm|alarm]] (sm_alarm), [[Special:MyLanguage/SEP_sesam_Glossary#disaster|disaster]] (sm_disaster) [[Special:MyLanguage/SEP_sesam_Glossary#notify|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 <tt><SESAM_ROOT>/skel/templates</tt>. The templates are activated when they are copied to <tt><SESAM_ROOT>/bin/sesam</tt> 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 <tt><SESAM_ROOT>/bin/sesam</tt> directory. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Configuration#interfaces|SEP sesam Interfaces]].</translate>
|-
|-
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:249-->
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:249-->
Line 350: Line 353:
{{anchor|logging level}}'''logging level'''||An option that controls the level of details of the of the backup and restore protocol. To change the logging level, use the <code>-v {log_level}</code> under the ''Additional call arguments (Expert options)'' in the backup or restore task properties. See also [[Special:MyLanguage/Setting_Log_Level|Setting Log Level]].</translate>
{{anchor|logging level}}'''logging level'''||An option that controls the level of details of the of the backup and restore protocol. To change the logging level, use the <code>-v {log_level}</code> under the ''Additional call arguments (Expert options)'' in the backup or restore task properties. See also [[Special:MyLanguage/Setting_Log_Level|Setting Log Level]].</translate>
|-
|-
|<translate><!--T:264-->
|<span style="color:grey;"><translate><!--T:264-->
{{anchor|LWM}}'''low watermark (LWM)'''||The lower value for the used disk space on the ''Path'' [[Special:MyLanguage/SEP_sesam_Glossary#data store|data store]] and ''NetApp Snap Store''. If set, it defines how much storage space is available for [[Special:MyLanguage/SEP_sesam_Glossary#save_set|savesets]] with expired [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]]. If LWM is set to 0, the EOL-free savesets are removed from the data store at the next purge. See also [[Special:MyLanguage/SEP_sesam_Glossary#HWM|high watermark]].</translate>
{{anchor|LWM}}'''low watermark (LWM)'''</translate></span>||<span style="color:grey;"><translate><!--T:374--> Obsolete as of v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']]. In previous SEP sesam versions LWM represented the lower value for the used disk space on the ''Path'', ''Si3'' and ''NetApp Snap'' stores. If set, it has defined how much storage space is available for [[Special:MyLanguage/SEP_sesam_Glossary#save_set|savesets]] with expired [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]]. If LWM was set to 0, the EOL-free savesets are removed from the data store at the next purge. See also [[Special:MyLanguage/SEP_sesam_Glossary#HWM|high watermark]].</translate></span>
|-
|-
|<translate><!--T:265-->
|<translate><!--T:265-->
Line 395: Line 398:
|-
|-
|<translate><!--T:278-->
|<translate><!--T:278-->
{{anchor|NEWDAY}}'''NEWDAY'''||A predefined SEP sesam daily event, accessible under [[Special:MyLanguage/SEP_sesam_Glossary#schedule|schedules]]: Main Selection window -> ''Scheduling'' -> ''Schedules''. It resets the event calendar, which is managed by [[Special:MyLanguage/SEP_sesam_Glossary#SEPuler|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 define a new [[Special:MyLanguage/SEP_sesam_Glossary#backup day|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 [[Special:MyLanguage/SEP_sesam_Glossary#saveset|saveset]] for day 1 and another for day 2). The execution time of the NEWDAY event can be modified according to your needs. Depending on SEP sesam version, the NEWDAY behavior may be different when it comes to cancelling active tasks by default; see [[Special:MyLanguage/NEWDAY_Event#Tigon|NEWDAY in ''≥ Tigon'']] and [[Special:MyLanguage/NEWDAY_Event#previous|NEWDAY in v. ''≤ 4.4.3'']]. 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 (≤ SEP sesam v. 4.4.3), purges and reorganizes the SEP sesam database, and restarts the [[Special:MyLanguage/SEP_sesam_Glossary#SMS|SMS]] and [[Special:MyLanguage/SEP_sesam_Glossary#STPD|STPD]] processes.</translate>
{{anchor|NEWDAY}}'''NEWDAY'''||A predefined SEP sesam daily event, accessible under [[Special:MyLanguage/SEP_sesam_Glossary#schedule|schedules]]: Main Selection window -> ''Scheduling'' -> ''Schedules''. It resets the event calendar, which is managed by [[Special:MyLanguage/SEP_sesam_Glossary#SEPuler|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 define a new [[Special:MyLanguage/SEP_sesam_Glossary#backup day|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 [[Special:MyLanguage/SEP_sesam_Glossary#saveset|saveset]] for day 1 and another for day 2). The execution time of the NEWDAY event can be modified according to your needs. Depending on SEP sesam version, the NEWDAY behavior may be different when it comes to cancelling active tasks by default; see [[Special:MyLanguage/4_4_3_Beefalo:Newday_Event|''Newday in v. 4.4.3 Beefalo'']] or [[Special:MyLanguage/4_4_3:NEWDAY_Event#previous|''Newday in older versions ≤ 4.4.3'']]. Note that complete deactivation of a NEWDAY event will cause SEP sesam to stop working properly. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Newday_Event|Newday Event]].</translate>
|-
|-
|<translate><!--T:279-->
|<translate><!--T:279-->
Line 404: Line 407:
|-
|-
|<translate><!--T:281-->
|<translate><!--T:281-->
{{anchor|notification_center}}'''notification center'''||Used to dynamically send messages from the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|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 [[Special:MyLanguage/SEP_sesam_Glossary#RSS_feed|RSS feeds]]. For more details on notifications, see [[Special:MyLanguage/Notification_Center_4.4en|Notification Center]].</translate>
{{anchor|notification_center}}'''notification center'''||Used to dynamically send messages from the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|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 [[Special:MyLanguage/SEP_sesam_Glossary#RSS_feed|RSS feeds]]. For more details on notifications, see [[Special:MyLanguage/4_4_3_Beefalo:Notification_Center|Notification Center]].</translate>
|-
|-
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:282-->
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:282-->
Line 430: Line 433:
|-
|-
|<translate><!--T:289-->
|<translate><!--T:289-->
{{anchor|parallel_backups}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#SBC|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 [[Special:MyLanguage/The_Backup_4.4#parallel|Parallel Backups]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#SMS|Sesam Multiplex Stream Server]].</translate>
{{anchor|parallel_backups}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#SBC|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 [[Special:MyLanguage/4_4_3_Beefalo:Backup#parallel|Parallel Backups]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#SMS|Sesam Multiplex Stream Server]].</translate>
|-
|-
|<translate><!--T:290-->
|<translate><!--T:290-->
Line 439: Line 442:
|-
|-
|<translate><!--T:292-->
|<translate><!--T:292-->
{{anchor|purge}}'''purge'''||The process of deleting obsolete ([[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL-free]]) savesets from regular Path [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] or NetApp Snap Store. It is based on [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]] and is triggered automatically. Purging is done until the [[Special:MyLanguage/SEP_sesam_Glossary#LWM|LWM]] is reached. It is also possible to start purging manually in the GUI: Main Selection window -> ''Components'' -> ''Data Stores'' content pane -> option ''Purge''. For details, see [[Special:MyLanguage/The_DataStore_4.4#watermarks|Watermarks and purge]].</translate>
{{anchor|purge}}'''purge'''||The process of deleting obsolete ([[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL-free]]) savesets from regular ''Path'', ''Si3'' or ''NetApp Snap'' store. It is based on [[Special:MyLanguage/SEP_sesam_Glossary#HWM|HWM]] and is triggered automatically. Purging is done until all [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL-free]] savesets are deleted. It is also possible to start purging manually in the GUI: Main Selection window -> ''Components'' -> ''Data Stores'' content pane -> option ''Purge''. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Data_Store#watermark|HWM, purge and Si3 repair area]].</translate>
|-
|-
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:293-->
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:293-->
Line 468: Line 471:
|-
|-
|<translate><!--T:301-->
|<translate><!--T:301-->
{{anchor|restore}}'''restore'''||A process that browses for different versions of [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]], and copies data from savesets to a [[Special:MyLanguage/SEP_sesam_Glossary#SBC|client]]. Data restore granularity depends on the selected data type. The following restore types are available: [[Special:MyLanguage/SEP_sesam_Glossary#complete restore|complete restore]], [[Special:MyLanguage/SEP_sesam_Glossary#generation restore|generation restore]], [[Special:MyLanguage/SEP_sesam_Glossary#selective restore|selective restore]]. For VMware vSphere, [[Special:MyLanguage/SEP_sesam_Glossary#single item restore|single item restore]] is available. See also [[Special:MyLanguage/SEP_sesam_Glossary#disaster recovery|disaster recovery]] and [[Special:MyLanguage/SEP_sesam_Glossary#XPRFS|XPRFS]].</translate>
{{anchor|restore}}'''restore'''||A process that browses for different versions of [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] and copies data from savesets to a [[Special:MyLanguage/SEP_sesam_Glossary#SBC|client]]. SEP sesam provides two restore interfaces: ''GUI restore wizard'' and web-based ''Restore Assistant''. Restore granularity depends on the selected data type. The following restore types are available: [[Special:MyLanguage/SEP_sesam_Glossary#complete restore|complete restore]], [[Special:MyLanguage/SEP_sesam_Glossary#generation restore|generation restore]], [[Special:MyLanguage/SEP_sesam_Glossary#selective restore|selective restore]]. For details, see [[Special:MyLanguage/Standard_Restore_Procedure|Standard (GUI) Restore Procedure]] and [[Special:MyLanguage/Restore_Assistant|Restore Assistant]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#disaster recovery|disaster recovery]] and [[Special:MyLanguage/SEP_sesam_Glossary#XPRFS|XPRFS]].</translate>
|-
|<translate><!--T:379--> {{anchor|restore_assistant}}'''Restore Assistant'''</translate>||<translate><!--T:380--> The intuitive web restore interface that allows you to restore your data from anywhere with the appropriate permissions. Compared to [[Special:MyLanguage/Standard_Restore_Procedure|''GUI restore wizard'']], it provides a few additional advanced restore options, but does not support all [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task types]]. You can perform online restores of data from ''regular path'' backups, ''NDMP and NSS file system path'' backups, ''emails from Kopano'' backups, and ''virtual machines'' (VMs) to which you have been granted access. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Restore_Assistant|Restore Assistant]].</translate>
|-
|-
|<translate><!--T:302-->
|<translate><!--T:302-->
{{anchor|restore_task}}'''restore task'''||Used to configure a restore of data from [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] to a client. A restore task always contains browsing and selecting the desired savesets by time and task/filename, selecting [[Special:MyLanguage/SEP_sesam_Glossary#restore|restore type]] and restore [[Special:MyLanguage/SEP_sesam_Glossary#target|target]], for example file system folder. You can configure a restore task using a restore wizard: in the menu bar, click ''Activities'' -> ''Restore''.</translate>
{{anchor|restore_task}}'''restore task'''||Used to configure a restore of data from [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] to a client. A restore task always contains browsing and selecting the desired savesets by time and task/filename, selecting [[Special:MyLanguage/SEP_sesam_Glossary#restore|restore type]] and restore [[Special:MyLanguage/SEP_sesam_Glossary#target|target]], for example, file system folder. You can configure a restore task in the [[Special:MyLanguage/Standard_Restore_Procedure|''GUI restore wizard'']] or use the web [[Special:MyLanguage/Restore_Assistant|''Restore Assistant'']].</translate>
|-
|-
|<translate><!--T:303-->
|<translate><!--T:303-->
Line 477: Line 482:
|-
|-
|<translate><!--T:304-->
|<translate><!--T:304-->
{{anchor|retention_time}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] and keeping them available for [[Special:MyLanguage/SEP_sesam_Glossary#restore|restore]]. The retention time period starts with the date a saveset is written to the media and lasts for the period defined by media pool's [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] (in days). Once the retention time expires, the media are writable again. The retention time is defined when configuring a new [[Special:MyLanguage/SEP_sesam_Glossary#media pool|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 saveset or of all backup-related data by adjusting EOL. See also [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]]. In addition, you can use software tape protection to write-protect tape media. See also [[Special:MyLanguage/SEP_sesam_Glossary#write-protected|write-protected media]].</translate>
{{anchor|retention_time}}'''retention time'''||The retention time (in days) is set for media pool and is applied to all media in the media pool. It specifies the time period for which the backup data is protected after it was written to the medium, thus preserving the [[Special:MyLanguage/SEP_sesam_Glossary#saveset|savesets]] and keeping them available for [[Special:MyLanguage/SEP_sesam_Glossary#restore|restore]]. The retention time period starts with the date a saveset is written to the medium and defines the expiration date ([[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]]) after which the saveset may be deleted. Once the retention time for all savesets stored on media has expired, the media can be rewritten.  
The retention time is defined when configuring a new [[Special:MyLanguage/SEP_sesam_Glossary#media pool|media pool]]: Main Selection window ->''Components'' -> ''Media Pools'' -> ''New Media Pool'', or when editing the selected media pool ''Properties''. You can extend or shorten the expiration date of a single saveset or of all backup-related data (all savesets that belong to the same backup) by adjusting their [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]]. In addition, you can use software tape protection to write-protect tape media. See also [[Special:MyLanguage/SEP_sesam_Glossary#write-protected|write-protected media]].</translate>
|-
|-
|<translate><!--T:305-->
|<translate><!--T:305-->
Line 502: Line 508:
|-
|-
|<translate><!--T:312-->
|<translate><!--T:312-->
{{anchor|SEA}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#data store|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 [[Special:MyLanguage/SEP_sesam_Glossary#license|license]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam extensions|SEP sesam extensions]].</translate>
{{anchor|SEA}}'''SEP EasyArchive (SEA)'''||''As of SEP sesam 4.4.3, this module is no longer supported.''</translate><br />
<span style="color:grey;"><translate><!--T:377--> 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 [[Special:MyLanguage/SEP_sesam_Glossary#data store|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 [[Special:MyLanguage/SEP_sesam_Glossary#license|license]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam extensions|SEP sesam extensions]].</translate></span>
|-
|-
|<translate><!--T:313-->
|<translate><!--T:313-->
{{anchor|SEP_FDS}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#data store|data stores]]. SEP FDS VA works as a [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server]]. It includes 1 TB of repository capacity (requires one repository capacity [[Special:MyLanguage/SEP_sesam_Glossary#license|license]]), but is expandable up to 5 TB. For details, see [[Special:MyLanguage/FDSVA_Dedup_Appliance_EN|SEP FDS VA Deduplication Appliance]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#SEP Si3|SEP Si3 target deduplication]] and [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam extensions|SEP sesam extensions]].</translate>
{{anchor|SEP_FDS}}'''SEP FDS VA'''||''As of SEP sesam 4.4.3, this module is no longer supported.'' </translate><br />
<span style="color:grey;"><translate><!--T:378--> 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 [[Special:MyLanguage/SEP_sesam_Glossary#data store|data stores]]. SEP FDS VA works as a [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server]]. It includes 1 TB of repository capacity (requires one repository capacity [[Special:MyLanguage/SEP_sesam_Glossary#license|license]]), but is expandable up to 5 TB. For details, see [[Special:MyLanguage/FDSVA_Dedup_Appliance_EN|SEP FDS VA Deduplication Appliance]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#SEP Si3|SEP Si3 target deduplication]] and [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam extensions|SEP sesam extensions]].</translate>
|-
|-
|<translate><!--T:314-->
|<translate><!--T:314-->
Line 511: Line 519:
|-
|-
|<translate><!--T:315-->
|<translate><!--T:315-->
{{anchor|dashboard}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_environment|SEP sesam environment]]. It provides information on backups and restores per server, client or application over time; daily, weekly, monthly or custom statistics on [[Special:MyLanguage/SEP_sesam_Glossary#event|event]]; overview of total size of backed up and restored data and on [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] utilization. The web reports can be filtered by events, clients and state and used for an [[Special:MyLanguage/SEP_sesam_Glossary#SEPuler|overview of up-coming events]]. For details, see [[Special:MyLanguage/SEP_sesam_Dashboard|SEP sesam Dashboard]].</translate>
{{anchor|dashboard}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_environment|SEP sesam environment]]. In [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], SEP sesam Dashboard has been extended to offer additional functionality in [[SEP_sesam_Glossary#SEP_sesam_web_UI|Web UI]], including a more detailed overview of jobs, utilization and performance, and improved monitoring of the SEP sesam environment with various reports, metrics and log files. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Web_UI|SEP sesam Web UI]].
</translate>
|-
|-
|<translate><!--T:316-->
|<translate><!--T:316-->
Line 537: Line 546:
|<translate><!--T:323-->
|<translate><!--T:323-->
{{anchor|SEP_sesam_Storage_Server}}'''SEP sesam Storage Server'''||See [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server]].</translate>
{{anchor|SEP_sesam_Storage_Server}}'''SEP sesam Storage Server'''||See [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server]].</translate>
|-
|<translate><!--T:376--> {{anchor|SEP_sesam_web_UI}}'''SEP sesam Web UI'''||The SEP sesam Web UI is a modern web client with several components, including [[Special:MyLanguage/SEP_sesam_Glossary#dashboard|SEP sesam web dashboard]] and online Restore Assistant. It enables you to check the status of jobs, monitor SEP sesam operations, access SEP sesam logs and reports, and restore your data online. For details, see  [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Web_UI|SEP sesam Web UI]].</translate>
|-
|-
|<translate><!--T:324-->
|<translate><!--T:324-->
Line 542: Line 553:
|-
|-
|<translate><!--T:325-->
|<translate><!--T:325-->
{{anchor|replication}}'''SEP Si3 replication'''||A solution that consistently replicates data between the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]] and [[Special:MyLanguage/SEP_sesam_Glossary#RDS|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 [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 deduplication]]. Original deduplication store can be [[Special:MyLanguage/SEP_sesam_Glossary#initial_seed|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 [[Special:MyLanguage/SEP_sesam_Glossary#follow|follow-up event]]. For details, see [[Special:MyLanguage/Replication|Replication]].</translate>
{{anchor|replication}}'''SEP Si3 replication'''||The SEP Si3 replication consistently replicates data between the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]] and [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server]], or between two RDSs. You can also use ''HPE Catalyst stores'' and ''HPE Cloud Bank Storage'', or ''S3 cloud storage'' as replication target. Replication means that only changed data blocks are sent over a network and backed up to the target according to defined schedule. Typically, it is used together with [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 deduplication]]. Original deduplication store can be [[Special:MyLanguage/SEP_sesam_Glossary#initial_seed|seeded]] to provide the basis for new deduplication store for replication. A replication task can be configured under Tasks: Main selection -> ''Tasks'' -> ''Replication Tasks'' (previously ''Si3 replications'') -> ''New Replication Task''. Replication can be configured as a [[Special:MyLanguage/SEP_sesam_Glossary#follow|follow-up event]]. For details, see [[Special:MyLanguage/4_4_3_Beefalo:About_Replication|About Replication]].</translate>
|-
|-
|<translate><!--T:326-->
|<translate><!--T:326-->
Line 551: Line 562:
|-
|-
|<translate><!--T:328-->
|<translate><!--T:328-->
{{anchor|SEPuler}}'''SEPuler'''||A process that controls scheduling of the SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#backup task|backup]] and [[Special:MyLanguage/SEP_sesam_Glossary#restore task|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 [[Special:MyLanguage/SEP_sesam_Glossary#event|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 [[Special:MyLanguage/SEP_sesam_Glossary#schedule|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 [[Special:MyLanguage/SEP_sesam_Glossary#event priority|event priorities]]. The event calendar provides overview of all, scheduled and the expired events: Main Selection window -> ''Scheduling'' -> ''Calendar Sheet''. For details, see [[Special:MyLanguage/The_SEPuler_-_an_event_calendar_4.4|The SEPuler - an event calendar]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#calendar sheet|calendar sheet]] and [[Special:MyLanguage/SEP_sesam_Glossary#schedule|schedule]].</translate>
{{anchor|SEPuler}}'''SEPuler'''||A process that controls scheduling of the SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#backup task|backup]] and [[Special:MyLanguage/SEP_sesam_Glossary#restore task|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 [[Special:MyLanguage/SEP_sesam_Glossary#event|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 [[Special:MyLanguage/SEP_sesam_Glossary#schedule|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 [[Special:MyLanguage/SEP_sesam_Glossary#event priority|event priorities]]. The event calendar provides overview of all, scheduled and the expired events: Main Selection window -> ''Scheduling'' -> ''Calendar Sheet''. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar|SEPuler - an event calendar]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#calendar_sheet|calendar sheet]] and [[Special:MyLanguage/SEP_sesam_Glossary#schedule|schedule]].</translate>
|-
|-
|<translate><!--T:329-->
|<translate><!--T:329-->
Line 569: Line 580:
|-
|-
|<translate><!--T:334-->
|<translate><!--T:334-->
{{anchor|Si3_encryption}}'''Si3 encryption'''||Si3 encryption for [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 deduplication store]] is one of the SEP sesam encryption types (also available are [[Special:MyLanguage/SEP_sesam_Glossary#backup-task|backup-task]] and [[Special:MyLanguage/SEP_sesam_Glossary#LTO_encryption|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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]]. If the encryption key is not available, the Si3 encrypted data cannot be read. For details, see [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#encryption|encryption]].</translate>
{{anchor|Si3_encryption}}'''Si3 encryption'''||Si3 encryption for [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 deduplication store]] is one of the SEP sesam encryption types (also available are [[Special:MyLanguage/SEP_sesam_Glossary#backup-task|backup-task]] and [[Special:MyLanguage/SEP_sesam_Glossary#LTO_encryption|LTO]] encryption). SEP sesam provides encryption for Si3 deduplication store to help ensure compliance with data protection legislation. Si3 encryption is enabled by specifying and confirming the encryption password. If the encryption key is not available, the Si3 encrypted data cannot be read. For details, see [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]]. See also [[Special:MyLanguage/SEP_sesam_Glossary#encryption|encryption]].</translate>
|-
|-
|<translate><!--T:335-->
|<translate><!--T:335-->
Line 620: Line 631:
|<translate>
|<translate>
<!--T:372-->
<!--T:372-->
{{anchor|UI_mode}}'''UI mode'''||Available for v. [[Special:MyLanguage/SEP_sesam_Release_Versions|≥ 4.4.3 ''Grolar'']]. Used for adjusting the GUI display according to the UI mode: ''Basic'', ''Advanced'' or ''Expert''. In the menu bar, click ''Configuration'' -> ''Defaults'' -> ''Extras''. By switching the mode from ''Basic'' to ''Expert'' some additional options are available. For details, see [[Special:MyLanguage/Configuration_4.4#Grolar|UI Mode]].</translate>
{{anchor|UI_mode}}'''UI mode'''||Available for v. [[Special:MyLanguage/SEP_sesam_Release_Versions|≥ 4.4.3 ''Grolar'']]. Used for adjusting the GUI display according to the UI mode: ''Basic'', ''Advanced'' or ''Expert''. In the menu bar, click ''Configuration'' -> ''Defaults'' -> ''Extras''. By switching the mode from ''Basic'' to ''Expert'' some additional options are available. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Configuration#defaults|UI Mode]].</translate>
|-
|-
|<translate><!--T:351-->
|<translate><!--T:351-->
Line 668: Line 679:
|-
|-
|<translate><!--T:364-->
|<translate><!--T:364-->
{{anchor|watermark}}'''watermark'''||A parameter used for [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] configuration. See [[Special:MyLanguage/SEP_sesam_Glossary#HWM|high watermark]] and [[Special:MyLanguage/SEP_sesam_Glossary#LWM|low watermark]].</translate>
{{anchor|watermark}}'''watermark'''||A parameter used for [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] configuration. See [[Special:MyLanguage/SEP_sesam_Glossary#HWM|high watermark]] (note that low watermark is obsolete).</translate>
|-
|-
|<translate><!--T:365-->
|<translate><!--T:365-->
{{anchor|write-protected}}'''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 [[Special:MyLanguage/SEP_sesam_Glossary#retention_time|retention time]] of the media pool as well as any individually adjusted [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] and sets permanent protection for savesets 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 [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] and [[Special:MyLanguage/SEP_sesam_Glossary#retention_time|retention time]].</translate>
{{anchor|write-protected}}'''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 the [[Special:MyLanguage/SEP_sesam_Glossary#retention_time|retention time]] of the media pool as well as any individually adjusted [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] and sets permanent protection for savesets 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 [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] and [[Special:MyLanguage/SEP_sesam_Glossary#retention_time|retention time]].</translate>
|-
|-
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:366-->
| align="center" colspan="2" style="background:#FFCC01; color:#002F55" <translate><!--T:366-->

Revision as of 13:07, 6 March 2020

Other languages:

Copyright © SEP AG 1999-2024. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

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.

Terms Description

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, SM_SSH (SEP sesam SSH based control communication), PROXY (available vendor-specific protocols are: vSphere (vCenter Server), Citrix XenServer, NetApp and Novell SMS for NetWare 5.1/6.0/6.5), SSH (Secure Shell), and RSH (Remote Shell). As of Grolar, the default access mode is SM_SSH. 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 the conditions for a particular user or group to access and performs an operation on a specific object (e.g., client, location, backup, etc.). As of SEP sesam version 4.4.3 Grolar, you can configure ACLs for locations and clients, if you have the admin rights. For details, see Using Access Control Lists.
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 or in case of a license violation. 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.
archive adjustment A process by which a comparison between media in the loader and the SEP sesam media archive database is made. It performs database synchronization with the selected loader by updating the database with the most current inventory information from the scanned device. It is mandatory whenever the content of a loader has changed. You can run the archive adjustment in GUI: Main Selection window -> Components -> Loader content pane -> option Archive Adjustment. It is also possible to run it as a scheduled media event. For details, see Setting up Archive Adjustment.
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 a process used to grant and restrict access to SEP sesam Server. It is the first step of authorization process by verifying user credentials (user name and password). For details, see About Authentication and Authorization. See also authorization.
authorization Authorization is used by SEP sesam to validate if an authenticated user has appropriate permissions for accessing a specific resource or operation within SEP sesam Server. It can now be synchronized with directory services, such as Active Directory or LDAP for consistent user management. For details, see About Authentication and Authorization.
autoloader See loader.

B

backup The process of copying and storing file system and/or application data.
backup client See SEP sesam Client.
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 EOL See EOL.
backup level Allows specifying the level of data that is copied from source to destination. Used to define backup strategies with several levels (for example, according to the generation principle). It is defined when configuring a new backup event in the Main Selection window -> Scheduling -> New Backup Event, tab Parameter, option Backup Level (note that the naming was changed from Backup type to Backup level in Grolar). Available backup levels 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-task encryption Backup-task encryption for savesets 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 backup-task encryption algorithms are the Advanced Encryption Standard (AES) 256-bit encryption and the Blowfish encryption. For details, see Backup-task encryption. See also encryption.
backup type See task type. Note that that the naming was changed from Backup type to Task type in Grolar.
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 views are displayed at the upper right side corner. All events are recorded by SEPuler.
Changed Block Tracking (CBT) An incremental backup technology for VMware and Citrix XenServer (v. ≥ 7.3) that identifies changes on block level and backs up only disk blocks of a VM’s virtual disk that have changed since the last backup; in case of VMware it also backs up the blocks that are in use (on VMFS partitions). SEP sesam uses CBT to perform block level incremental (INCR) and differential (DIFF) backups of VMDKs (VMware) or VDIs (Citrix XenServer) after a full (FULL) backup has been successfully executed. SEP sesam enables CBT automatically by default to optimize backups of VMs. For details, see Changed Block Tracking (CBT).
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.
clean up A process of cleaning up orphaned savesets from the data stores manually, thus releasing the space that might be occupied by orphaned savesets. You can clean up data store in the Data Stores content pane menu: Main Selection window -> Components -> Data Stores content pane -> option Clean up. For more details, see Clean up orphaned savesets.
client See SEP sesam Client.
cold backup (C) An offline backup of VMs and databases. See also hot backup.
command line The program (under Windows cmd.exe, under UNIX shell console), where commands can be entered.
Command Line Interface (CLI) The command-line interface to execute SEP sesam commands in UNIX and Windows environments. SEP sesam CLI supports all of the commands that are available in the SEP sesam GUI and much more; 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 saveset 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 tree view of the components of the SEP sesam environment. The following components are available: 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 savesets. 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 savesets are not referred by any differential (DIFF) or incremental (INCR) savesets.
custom calendar Can be specified by using a schedule option User defined. The custom calendar can be used to prevent scheduled tasks such as backup, migration or replication (see blocking date) or to perform special tasks. For example, scheduled backups can be blocked on certain days, such as public holidays. Should such an event overwrite another, event priority must be defined higher. 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.

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. SEP sesam daemons are 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 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 savesets directly on one or several configured storage locations — into the file system. Data store configuration consists of specifying data store capacity and HWM (note that low watermark is obsolete). 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. Data store is purged automatically based on HWM. It is also possible to purge the data store or clean up orphaned savesets manually. 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.
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 saveset 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 savesets 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. For details on each DR solution, see Bare Metal Recovery Linux, SEP sesam BSR Pro for Windows, and SEP sesam Disaster Recovery.
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: backup-task encryption for savesets (set in the backup task), Si3 encryption for Si3 deduplication store (set in the Si3 deduplication store properties), and hardware-based LTO encryption for LTO tape drives (generation 4 and higher), which is done on a media pool level. For every encryption you must create and store an encryption key. For details, see Backup-Task Encryption, LTO Encryption and, Encrypting Si3 Deduplication Store.
environment See SEP sesam environment.
EOL End of Lifetime (EOL) specifies the time until which the backed up data on media remains protected and thus defines the expiration date of the backup data. The EOL of a saveset is defined by the date the data is written to the media and the retention time (in days) of the media pool to which the media belongs. Once the EOL of all savesets stored on media has expired, the media can be rewritten. Note that SEP sesam provides dependency-based retention strategy performed by automated EOL adjustment. This means that EOL is automatically adjusted for savesets that, for example, belong to the same backup chain, in order to enable to enable complete restore of data. As of v. 4.4.3 Beefalo V2, it is possible to customize retention policy by inserting or modifying EOL-related keys. EOL behaviour may be release-dependent. For details, see Managing EOL.

The EOL property can be managed for three object types:

Saveset EOL
This is the expiration date for each individual saveset (for savesets that are stored on tape, see also tape media EOL). The saveset EOL is calculated from the time the data is written to the medium using the following formula: expiration = creation date + the retention time of the media pool. 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 saveset EOL is 31st of January. Saveset EOL can be adjusted for each individual saveset. If a saveset is part of a backup chain, its EOL follows the rules of dependency-based retention, as described in Managing EOL. The Saveset EOL parameter can be checked and modified under all media-related views, e.g., in the Media, Media Pools and Data Stores properties (Savesets tab -> Saveset EOL), or whenever a task with the savesets is displayed. For details on automated and manual EOL adjustment, see Managing EOL.
Backup EOL
This is the expiration date for all data that belong to the same backup, including migrated and replicated savesets. It is based on the longest EOL of all savesets that belong to the same backup and follows the rules of dependency-based retention, as described in Managing EOL. The Backup EOL parameter can be modified under all media-related views, e.g., in the Media, Media Pools and Data Stores properties (Savesets tab -> Backup EOL), or whenever a task with the savesets is displayed.
Tape media EOL
When a saveset is stored on tape, every stored saveset has its own saveset EOL. The expiration date of the tape, which is the tape media EOL, is defined by the maximum expiration date (the longest EOL) identified on the tape. Only when all of the savesets on tape have their retention time expired and the tape is not locked (write-protected), the entire tape is eligible for re-use. Tape media EOL can also be manually extended or reduced. For more details, see Managing EOL.
EOL refers only to backups and related migrated and replicated savesets. SEP sesam logs, readability check logs, calendar sheet entries and restore tasks have separate retention parameters, see retention periods.
EOL-related keys Depending on SEP sesam version, EOL-related parameters may be used to change the default EOL policy (backup retention behaviour) by modifying EOL-related keys in the global settings in GUI. For details, see Customizing retention policy.
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 events with higher priority first. The only exception are the events 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

failed job Every backup, restore, migration, replication, or media action job which fails for various reasons, e.g., file-size issues, insufficient permissions, etc. An overview of all jobs and their status is shown in the Job State. When a job fails, the cause of the failure should be determined. In case of a failed backup, SEP sesam will automatically delete any failed backup after 3 days. It is possible to keep failed backup savesets for a longer time by manually extending their backup EOL. For details, see Manually extending EOL.
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, saveset 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 saveset created as FULL is the basic saveset for subsequent DIFF or INCR savesets. 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 saveset 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 setting the granularity level of items to be backed up and used as 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) and 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. If the HWM value is set, a data store purge process is started for all EOL-free savesets when it is reached. The oldest free savesets are deleted first. In previous versions of SEP sesam (≤ 4.4.3.42 Tigon), if HWM was set and exceeded, backups could no longer be started while running backups were allowed to finish. Purging is done until the low watermark is reached (if set). This behaviour has changed with SEP sesam v. ≥ 4.4.3.48 Tigon V2; if HWM is set, exceeding it will only issue an information message but will no longer prevent backups to be started.
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 Data management software which is aware of the Hierarchical 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 saveset had been created. See also backup level.
Initial seed A process of backing up savesets 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 savesets 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. For details, see SEP sesam Interfaces.

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 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 manufacturer's 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 Saveset 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 controls the level of details of the of the backup and restore protocol. To change the logging level, use the -v {log_level} under the Additional call arguments (Expert options) in the backup or restore task properties. See also Setting Log Level.
low watermark (LWM) Obsolete as of v. 4.4.3 Beefalo. In previous SEP sesam versions LWM represented the lower value for the used disk space on the Path, Si3 and NetApp Snap stores. If set, it has defined how much storage space is available for savesets with expired EOL. If LWM was set to 0, the EOL-free savesets are removed from the data store at the next purge. 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 backup-task encryption for savesets). 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. 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.
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 saveset data to a newly created saveset. Migration can be configured as a follow-up event.
migration task Used to select a saveset and a target media pool for migration.
mount saveset 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 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 saveset for day 1 and another for day 2). The execution time of the NEWDAY event can be modified according to your needs. Depending on SEP sesam version, the NEWDAY behavior may be different when it comes to cancelling active tasks by default; see Newday in v. ≥ 4.4.3 Beefalo or Newday in older versions ≤ 4.4.3. Note that complete deactivation of a NEWDAY event will cause SEP sesam to stop working properly. For details, see Newday Event.
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 GNU 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.
purge The process of deleting obsolete (EOL-free) savesets from regular Path, Si3 or NetApp Snap store. It is based on HWM and is triggered automatically. Purging is done until all EOL-free savesets are deleted. It is also possible to start purging manually in the GUI: Main Selection window -> Components -> Data Stores content pane -> option Purge. For details, see HWM, purge and Si3 repair area.

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 savesets and copies data from savesets to a client. SEP sesam provides two restore interfaces: GUI restore wizard and web-based Restore Assistant. Restore granularity depends on the selected data type. The following restore types are available: complete restore, generation restore, selective restore. For details, see Standard (GUI) Restore Procedure and Restore Assistant. See also disaster recovery and XPRFS.
Restore Assistant The intuitive web restore interface that allows you to restore your data from anywhere with the appropriate permissions. Compared to GUI restore wizard, it provides a few additional advanced restore options, but does not support all task types. You can perform online restores of data from regular path backups, NDMP and NSS file system path backups, emails from Kopano backups, and virtual machines (VMs) to which you have been granted access. For details, see Restore Assistant.
restore task Used to configure a restore of data from savesets to a client. A restore task always contains browsing and selecting the desired savesets by time and task/filename, selecting restore type and restore target, for example, file system folder. You can configure a restore task in the GUI restore wizard or use the web Restore Assistant.
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 The retention time (in days) is set for media pool and is applied to all media in the media pool. It specifies the time period for which the backup data is protected after it was written to the medium, thus preserving the savesets and keeping them available for restore. The retention time period starts with the date a saveset is written to the medium and defines the expiration date (EOL) after which the saveset may be deleted. Once the retention time for all savesets stored on media has expired, the media can be rewritten.

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 extend or shorten the expiration date of a single saveset or of all backup-related data (all savesets that belong to the same backup) by adjusting their 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

saveset A set of data, such as files and directories, copied onto backup medium by backup or migration. The time period for which a saveset is preserved is defined by the retention time. You can verify savesets after the backup is finished by configuring a follow-up event.
saveset EOL See EOL.
saveset ID An internal unique identification assigned to a saveset.
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 saveset, 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. In 4.4.3 Beefalo V2, SEP sesam Dashboard has been extended to offer additional functionality in Web UI, including a more detailed overview of jobs, utilization and performance, and improved monitoring of the SEP sesam environment with various reports, metrics and log files. For details, see SEP sesam Web UI.
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 savesets 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 sesam Web UI The SEP sesam Web UI is a modern web client with several components, including SEP sesam web dashboard and online Restore Assistant. It enables you to check the status of jobs, monitor SEP sesam operations, access SEP sesam logs and reports, and restore your data online. For details, see SEP sesam Web UI.
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 Si3 Deduplication Store.
SEP Si3 replication The SEP Si3 replication consistently replicates data between the SEP sesam Server and SEP sesam Remote Device Server, or between two RDSs. You can also use HPE Catalyst stores and HPE Cloud Bank Storage, or S3 cloud storage as replication target. Replication means that only changed data blocks are sent over a network and backed up to the target according to defined schedule. Typically, 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 -> Replication Tasks (previously Si3 replications) -> New Replication Task. Replication can be configured as a follow-up event. For details, see About 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 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 redundancy 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 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 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.
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 saveset. 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 level 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 is one of the SEP sesam encryption types (also available are backup-task and LTO encryption). SEP sesam provides encryption for Si3 deduplication store to help ensure compliance with data protection legislation. Si3 encryption is enabled by specifying and confirming the encryption password. If the encryption key is not available, the Si3 encrypted data cannot be read. For details, see Encrypting Si3 Deduplication Store. See also encryption.
Si3 purge The process of deleting Si3 files (DDLs) automatically from Si3 repair area (deduplication storage space) after the specified amount of time (SEP sesam default: 4 days) or when the disk usage threshold is reached (specified in GIB).
Si3 repair area The Si3 repair area, available as of v. 4.4.3 Grolar if UI mode is selected as Expert (in the menu bar under Configuration -> Defaults), defines space for Si3 files (DDLs) that were identified by a garbage collection job and are no longer used. These files are still kept in the repair area to enable repair of Si3 in case of any problems (e.g., caused by a file system error or by a crash of an operating system). For details, see Configuring Si3 Deduplication Store.
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.
socket A slot for computer processors to mount a processor on a motherboard or slot. With SEP sesam, a backup environment is licensed for each socket in the virtualization servers displayed by the Hypervisor API. For details, see Licensing.
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

target A specified location for backup/migration of restored data, for example a different media pool (migration) or a folder (restore) on a client.
task Execution of a SEP sesam backup, migration, replication, restore or command task.
task group A group of tasks used for scheduling.
task type (previously called 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 task types are: Path backup, SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphere etc.
topology Represents the SEP sesam backup environment including the hardware, computers, backup devices, etc. See also SEP sesam locations, clients and servers.

U

UI mode Available for v. ≥ 4.4.3 Grolar. Used for adjusting the GUI display according to the UI mode: Basic, Advanced or Expert. In the menu bar, click Configuration -> Defaults -> Extras. By switching the mode from Basic to Expert some additional options are available. For details, see UI Mode.
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 About Authentication and Authorization
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 only in versions ≤ 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. The 4.4.3 Grolar release introduced a new authentication concept to grant and restrict access to SEP sesam Server, specific clients and locations; hence the displayed GUI components still depend on the user type, but the user view setting became unnecessary. However, a GUI display can now be adjusted according to the UI mode.

Ü

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, RHV, KVM 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 (note that low watermark is obsolete).
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 the retention time of the media pool as well as any individually adjusted EOL and sets permanent protection for savesets 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 saveset stored to Path or Si3 deduplication 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.

Z