Archive:Tasks By Clients 4.2

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.

Tasks by Clients

The status of a backup task is shown as a colored, rectangular Icon in the right, lower corner:

1. Icon without additional rectangle: The backup has not started, or the last backup log has been erased from the tape.
2. Icon with a green rectangle: Last backup task status 'successful without warnings' or 'successful with warnings'.
3. Icon with red rectangle: Last backup task 'unsuccessful/failed'.
4. Icon with purple rectangle: Backup task stopped.

By clicking Properties you can see the information of a selected task and also make changes to it. Alternatively you can double-click the backup task to open it.

Right mouse menu

Clicking a backup task in the tree with the right mouse shows a 'Context Menu' with the following optons:

• Results (only for Backup Tasks) Show the last backup for this Task, see Properties of a finished backup),
• Immediate Start, see here
• Properties, Shows the properties of the related Backup Task,
• Copy (only with Backup Task),
• Delete, see here

Select New backup task

Task Name

User selected identification of a backup task (use numbers, letters and underscores (_) only)

Backup Type

Type of backup (Path-Backup Standard)

Path-Backup - Files, Directories (pre-set)

Registry ( WNT )

System state ( Win2000 )

Lotus Notes

MS Exchange Server

Informix

MS SQL Server

ORACLE

ORACLE7

SAP/R3

Client

Select a computer from which the backup is to be executed

Additional TCP/IP names related to a special network route can be specified (Client interface )

Source

Disk, directory, files, which should be backed up

Multisourcing - additional sources are separated by commas

Note

When using a Netware NSS Filesystems on Linux OES the NSS Volumes are normally found below the Linux path /media/nss. You can enter multiple paths as 'Source' (Multi-Source) by separating them with a comma.

Exclude List

Excludes certain files from the backup

Comment

Additional information

Unix:

over file system limits

When this option is not selected only the data of a file system will be backed up.

Example: By selecting / as a backup source /usr will not be backed up, if /usr is on its own partition.  
Currently, this setting is only applicable to UNIX clients.

if over NFS mounted files

even if the option over file system limits is selected, NFS Mounts will not be backed up. If a backup is desired you must set this option.

Windows:

with SEP sesam Bare Metal Recover (SBMR). sometimes referred to as Bare System Recovery

setting this option field provides three further choices for SEP with SBMR. Further information regarding the configuration of SEP sesam disaster recovery can be found in SEP sesam BSR 2.1.

The selections in the upper right of the window next to the Input Fields Source and Exclude List open the Client Browser, so that the desired files and directories can be combined with a mouse click.

Apply New

'Apply New' allows the user to select further tasks, in regard to currently selected jobs.

The tab "'Options 1"' enables to select from pre-defined Pre/Post-Options for backups and restores.

For a backup/restore a selection can be made in Change Profile from pre-defined profiles and if necessary a modification can be made by clicking the checkbox.

Options 1

Register Option 1 allows the choice of performing a pre-defined Pre/Post operation for backup and restore. Using this Register 'Pre/Post' actions for backup and/or recovery/restore globally can be set on or off. There are four possible choices.

Backup:

Execute pre

Commands written in the Pre- interface will be initiated

Ignore pre error

Forces the backup job to start in the event the Pre- commands were not executed properly.

Execute post

Commands written the Post- interface will be performed

Ignore backup error

Forces the Post- command to complete even if there were errors in the backup job, (e.g. this will restore a paused database even though the backup task failed).

Restore:

Execute pre

Commands written in the Pre- interface will be initiated

Start restore in spite of pre error

Forces a restore task to complete even though the Pre- command script was not properly executed.

Execute post

Commands written the Post- interface will be performed

Start post in spite of post error

Forces the completion of a restore task even though the Post- command script failed to completely execute, (e.g. this will restore a paused database even though the backup task failed)

Additional Call Arguments (Expert Options)

Save Options

Dependent on selected backup type and O/S platorm

Example: -v1 to set the verbose level in Protocol log

Restore Options

same as backup options, but only in the event of a 'Restore'

Options 2

Option 2 allows the selection of Encryption and Compression.

Cryptography

Encryption

none, bf64 or aes256

Info

Information regarding the setting/selection of a encryption key

Define new keyword

This button is activated when either (bf64 or aes256) is selected. A mouse click (if permissions are in place) combines the next two input fields

New keyword

Enter new keyword

Repeat new keyword

enter the new keyword manually, do not cut and paste!

Important

The password/keyword must be at least one (1) character and maximum 27 characters in length. It cannot have any special characters or spaces.

Compression (only available for Windows)

Compression

yes or no

Novell SMS

This tab is only shown on linux clients that can work as a datamover for Novell OES clients. Since SEP sesam version 3.6 it is possible to grant every task a different logon to the eDirectory.

Exclude list

With the exclude list certain directories and files can be excluded from a backup. The selection is made with regular expressions except for NetWare file systems where file the patterns '*' and '?' are used.

Important

In Windows und Unix regular expressions are used, in NetWare file patterns are used. If you wish to suppress a specific directory you should enter the complete path name. Multiple Excludes are delimited with commas. Examples may be found in the attachment..

Backup Types

SEP sesam differentiates between path backups and special backup types.

For path backups you can use the following entries:

• Backup of the Windows System_State is accomplished with the entry system_state as the only source of a path backup.
• Backup of the Linux partition schema is accomplished with the entry disk_info as the only source for the path backup.
• Windows SBMR/BSR backups also take place by selecting a path backup with corresponding activation of Backup -> SBMR/Bare Systems Recovery

Many special backup types, for example, hot backups for databases, are supported by SEP sesam. Many of the backup jobs will be initiated from within the database. In this case the jobs cannot be started from the SEPuler. These backups require command events.

For all hot backups for supported databases required the relevant online module license. The support of new special backup types is constantly under development and is continually extended to include new products. A complete description of supported applications and the requirements for them can be found in the product documentation.

Client Browser

The client browser is an O/S independent file search engine. In the client tree structure you will see not only files and directories, but also databases, pipes, sockets, character or block devices as long as they are relevant to the backup environment. The added functionality is accessed with a right mouse click. Additionally, the overview for the resulting character string helps to prevent the overflow of lists or exclude lists.

Note

The entire character string for the selected path, starting with SEP sesam version 3.4 cannot exceed 1,000 characters. If this limit is exceeded you must switch to a manually edited backup list. Information regarding the creation of such a text file as backup source can be found in the SEP sesam FAQ.

Menu

Appears when the right mouse button is pressed.

Expand

The tree for this location is dynamically expanded and opened.

Show Legend

Shows the abbreviation list in the lower window.

Restore Previous List

Deletes the complete input string.

Accept

Enters the chosen selection (Folder, Files) to the selected Source.

Legend

Note

When browsing a NetWare NSS in the current file system you may only select one source per task. Using a Linux path /media/nss/Full.. it may appear that you can enter multiple selections but, in fact, only the initial path will be backed up.

Delete Task

You select this tree to delete a task. Click the right mouse button and select 'delete'. Answer the following security question with 'Yes'.

New Restore Task

To create a new restore task see Restore. If you select the restore from this location certain parameters will be pre-set. A task name will also be automatically assigned.

New Migration Task

A migration is the process of copying already backed up data from one media pool (e.g. disk) to a different media pool (e.g. tape). The previously backed up files are organized in the form of savesets. These are copied identically from the source media pool to the target media pool. This way a duplication of savesets is possible. Typically these are realized in the sequence Disk-To-Disk-To-Tape (D2D2T).

As long as both media are available after the migration (in the source- or target- media pool) the saveset is duplicated. After the saveset is deleted from the source-media pool it is considered migrated. Optionally, both datasets can be accessed with the restore wizard. If only the migrated saveset exists it will be required in case of a restore.

The migration tasks are managed in a seperate menu item. In order to make SEP sesam more flexible regarding various requirements the tradition of the SEP sesam-Principle of only defining the source for tasks is broken with. Now source and target have to be defined in the new migration dialog. This enables you to immediately start a configured migration task from the GUI or attach it to a Migration Event over a schedule to start it automatically at a certein point in time.

Additionally a number of filter options were added(by task, task group or backup client, only to name a few). It is now also possible to migrate backups from a particular medium to a different pool.

Here is a descrition of all the fields and the functions assigned to them:

Name

a name for the migration task like for example 'EasyDisk1-to-Xtra_FDI' (max. 50 characters)

Parameters

• Media pool
  Specification of the source media pool
  • Pool
    Media pool name (e.g. 'EasyDisk1') from which the backups are to be copied (migrated). (Mandatory field)
  • starting on medium
    Standard = "*" for all media. With this the savesets of a particular medium of the media pool can be migrated. Depending on media size a backup can range over several media. Here only backups that begin on this medium are migrated!
  • Drive
    Drive number of the drive that is used to read the data (Mandatory field)
  • Saveset
    Standard = "*" for all savesets. With this it is possible to only migrate a particular backup. The selection is made according to the saveset-ID.
• Target
  Specification of the target
  • Pool
    Media pool name (e.g. 'Xtra') to which the backups are to be copied (migrated). (Mandatory field)
  • Drive
    Drive number of the drive that is used for writing the data. (Mandatory field)
  • Interface
    optional specification of the network interface through which the data transfer is executed.
• Date
  Here the timeframe of the backups that are to be migrated is defined.
  • Sesam day
    allows for the the definition of an absolute timeframe for the selection of the backups that are to be migrated. The entered date always referrs to the Sesam day.
  • relative Backup day
    from/to as a relative specification of the number of passed days. As an example, the relative timeframe from -6 to 0 copies all datasets from the last 6 Sesam days including the current Sesam day.

Filter

Using the filter options the number of backups to migrate can be limited.

• Backup status
  This allows to choose to only migrate certain backups with certain statuses (successful, with warnings or partially restorable). Default is migrating all successful backups and backups with warnings.
• Backup type
  Choice according to CFDI-Type (Copy, Full, Diff Inc): C, F, D, I and G. The CFDI-Type 'G' means generation-migration. This means that, in addition to the incremental backups of the past days, all connected backups from the past up until and including the last associated full backup are included in the migration. Among other thing, this makes sure that all relevant backups for a possible disaster recovery are available on the created media set for removal scenarios.
• Object
  • Task
    Default = "*" for all tasks in the defined timeframe. Here, a particular task can be chosen for migration.
  • Task group
    Default = "*" for all taskt in the defined timeframe. If a task group is selected only the tasks within the defined timeframe of this task group are migrated.
  • Client
    Default = "*" for all backup clients in the defined timeframe. If a backup client is chosen only the backups from this client are migrated.
• Number of copies
  Default = 0 (Zero) means that backups can be migrated as often as you want. Entering a number > 0 means that a backup can only be migrated that many times.

Notes

text field with max. 255 characters for additional input.

Buttons

Start

After activating immediate start of the migration task

create copy and save

If the migration task was given a different name in the field Name all changed options can be saved under a new name

Save

Saves the current changes

Delete

Migration task is deleted

Cancel

Editing of the migration task is closed, the changes are discarded