Archive:Schedules 3.6

From SEPsesam
Icon archived docs.png 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.
<<<Back
Scheduling
User Manual
Next>>>
Events


New Media Event

The button New Media Event opens the following window with the second tab. The first tab is equivalent to Schedules and is allready correct initialized.


MedienInitNew 36en.jpg


Since SEP sesam version 3.6 a media-event offers 3 media-actions:

init
A medium is re-initialized for backup. Ie, a new tape label is written and in case of redeployment the old information on the Sesam system will be deleted. A media-event sets off a spefic medium of a pool after activation through that the backups write their data. The content of that medium is ereased by the schedule (initialization). If the expected medium is not available during start of a backup (manipulations in the loader or similar), or the end of that medium is reached during data transfer (EOM), the SEP sesam generates an internal media event which provides another medium. If no media-event is configured in the scheduler, only the internal media-events take effect.
readability check
The readability check alllows to periodically check media for readability.
close tape
Here, an EOM (End Of Media) is produced, it is irrelevant whether the medium was filled or not. The medium is available again after reaching its EOL (End-Of-Liftime) and can be re-initialized.
Sequence control
Priority
see Setting Event Priorities
Blocking date
The schedule is effective only within the priorization-concept as a blocker for other media events for this pool in case of overlapping schedules, see Blocking Events