4 4 3 Beefalo:Grouping of SEP sesam Components: Difference between revisions

From SEPsesam
(Marked this version for translation)
(Added note for GUI Beefalo redesign.)
Line 1: Line 1:
<noinclude>
<noinclude>
<div class="noprint"><languages />
<div class="noprint"><languages />
<translate><!--T:42--> {{Template:Navigator_Beefalo/en|User_Manual#principle|Principle of SEP sesam|Media Strategy|Media Strategy}}</div><br /></translate>
<translate><!--T:42--> {{Template:Navigator_Beefalo/en|User_Manual#principle|Principle of SEP sesam|Media Strategy|Media Strategy}}</div></translate>
<translate><!--T:41-->
<translate>
<br />
<br />


==={{anchor|components}}Grouping of SEP sesam Components=== <!--T:16-->
==={{anchor|components}}Grouping of SEP sesam Components=== <!--T:16-->


{{:Template:GUI Beefalo Redesign/en}}
<!--T:5-->
<!--T:5-->
The following is an example of an embedded SEP sesam command within a network using various storage devices.
The following is an example of an embedded SEP sesam command within a network using various storage devices.

Revision as of 15:34, 22 March 2019

Other languages:
<<<Back
Principle of SEP sesam
User Manual
Next>>>
Media Strategy


Grouping of SEP sesam Components

Information sign.png Note
In order to improve usability, SEP sesam GUI has been redesigned to be more user-friendly without significantly changing the interface logic. SEP sesam documentation update (such as screenshots) to reflect these changes is being done in a phased manner, therefore the screenshots may still show the GUI from previous versions.

The following is an example of an embedded SEP sesam command within a network using various storage devices.

GUI components 4.4.png

Most of the objects described above can be arranged hierarchically and organized into groups.

Location

A Location is used to describe one or more clients/servers that may be backed up to SEP sesam Server. Each client must be assigned to a specific location for clarity. This is especially important when SEP sesam is used within a WAN-application. Locations can be hierarchically organized, i.e., multiple sub-locations can be summarized under one Location.

Drive groups

Often several drives are used on one SEP sesam Server system. If the drives are of one type, it is preferable to bind them into a Drive Group and to direct the backup to the group. In this way, a backup is performed automatically on a drive that is currently free. In case of a drive failure, each backup is automatically executed only on the available or operable drives. This is particularly true in cases of large autoloaders with multiple drives.

Task group

Pooled tasks within a task group can be activated with a single, scheduled event. Backup tasks can be streamed simultaneously using SEP sesam multi-streaming technology.

Media pools

To administer media relating to the different types of backup data, backup sources (e.g., file backup, DB backup) or drive types, media must be inserted into media pools. SEP sesam requires the configuration of media pools.