|THE CONTENT OF THIS PAGE IS OUTDATED|
|SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.|
The following is an example of an embedded SEP sesam command within a network using various storage devices.
Most of the objects described above can be arranged hierarchically and organized into groups.
A Location is used to describe one or more clients/servers that may be backed up to the sesam server. Each client must be assigned to a specific location for clarity. This is especially true when sesam is used within a WAN-application. Locations can be hierarchically organized, i.e. multiple sub-locations can be summarized under one Location.
Often several drives are used on one 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 currently free drive. In the event 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.
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.
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. Sesam requires the configuration of media pools.