Standard Backup Procedure

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2018. 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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Grolar. For previous documentation version(s), check Documentation archive.


Overview

The SEP sesam backup is a process in which file system and/or application data from SEP sesam clients are copied and stored to backup media. The backup procedure described below applies to creating filesystem backups. For applications, databases and virtualisation-specific data, the backup procedure might involve additional tasks or include other options. As special methods are used to back up such data, make sure to use the backup procedure specific to the data you want to back up.

Prerequisites

  • Each client system that you want to back up requires SEP sesam Client software to be installed. Note that the SEP sesam Server is always also a SEP sesam Client. For details on installation, see SEP sesam Quick Install Guide.
  • A client must be added to your backup environment.
  • Storage hardware must be configured and media must be prepared.
  • You must have admin user rights for performing a backup.

A standard backup procedure involves the following steps:

  1. Creating a backup task by selecting the data to be backed up
  2. Creating a backup schedule by specifying when you want to back up your data
  3. Creating a backup event by selecting where to back up your data to and how

Step 1: Creating a backup task

  1. From Main Selection -> Tasks -> By clients, select your client and click New backup task. The New backup task window opens.
  2. Use the browse button to specify the Source and select what you want to back up. If you want to back up individual files, you can either browse for directories and files that you want to include in the backup or enter their names followed by a comma (C:/Program Files/SEPsesam/var/db,C:\Users\AA\Documents\references). Typically, by selecting the source the task type and task name are set automatically. A few special task types are rare exceptions and thus require a manual selection of the relevant type and specifying the task name.
  3. Optionally, specify the filenames or patterns which you do not want to back up in the Exclude list. For details on various exclude options, see Creating Exclude List.
    If you want to add a comment, enter it in the Comment field.
  4. Optionally, edit the assigned Task name. You can give your task a meaningful or descriptive name (max. 15 letters) that clearly identifies it, for example diagnostix_all for a backup of your client named diagnostix.
  5. Optionally, click the Options tab to enable the pre/post backup commands.
  6. Information sign.png Note
    To use a configurable pre/post interface, you have to activate it first and create your own commands. Interfaces can be activated in GUI: in the menu bar, click Configuration -> Interfaces -> select the interface you want to activate and the client. The interface script window opens, allowing you to configure the desired action. Once done, click Save to activate the interface. The interface is saved to the <SESAM_ROOT>/bin/sesam directory. For more details, see Configuration: Interfaces.
    Click the Encryption & Compression tab if you want to set encryption or compress data. Use other corresponding tabs to consolidate individual tasks under a specific task group or assign a task to the schedule.
  7. Click OK to create the task.
  8. New backup task browse.png


SEP Tip.png Tip
Optionally, you can assign individual tasks to a task group and then trigger the start of all tasks belonging to that group with a single event. For details, see Adding a Task to the Task Group.

Step 2: Creating a schedule

SEP sesam schedules represent a framework for automating task execution. Different events, such as backup, migration, replication, restore, etc., can be linked to a schedule and configured to occur at a specified time.

A schedule defines the recurrence of an event and may be executed in minutes, hours, days, months or years. It can be set up to start periodically or to be executed once only. A schedule can be used for any number of events and the events of a particular task (backup, restore, migration, etc.) can can be configured in several schedules. All schedules and related jobs are configured and run in the SEP sesam Server's time zone.

Schedules always contain one predefined task: a NEWDAY schedule, which is linked to a NEWDAY event. SEP sesam uses the NEWDAY event to reorder its database, enable uninterrupted activity of the SEP sesam processes and to define a new backup day. Do not deactivate a NEWDAY event or delete a NEWDAY schedule, because this will cause SEP sesam to stop working properly! For details, see NEWDAY event.

The options for creating a SEP sesam schedule differ slightly depending on your SEP sesam version. Version 4.4.3 provides a few additional options such as user-defined dates (custom calendar). For details on its use, see Creating Custom Calendar.

> Creating a schedule with v. 4.4.3

> Creating a schedule with v. 4.4.2

SEP sesam v. 4.4.3

  1. From Main Selection -> Scheduling -> Schedules, click New schedule. The Schedule window appears.
  2. By default, the Execution is already enabled. Use this option to activate or disable the schedule. If you deselect the execution option, all events that are linked to this schedule will be deactivated. You can deactivate a schedule if you want to exclude scheduled jobs to run on specific days, such as holidays. For more details, see Creating Custom Calendar.
  3. In the Name field, enter the name for the schedule.
  4. Specify the time range and start time for the schedule in the Start field. Click the arrows in the date field to display a calendar. By default, the current date is already entered. In the next field, specify the start time, e.g., 18.30. All events related to this schedule will be started at the time defined by this parameter. Keep in mind that the actual start time depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it may have to wait until jobs with higher priorities are completed. For jobs with the same priority, the FIFO rule (first in first out) applies.
  5. If you want your schedule to be valid for a limited period of time only, e.g., until the end of the year, check the Expiration date option and enter the date of its suspension. The schedule will be deleted after the Expiration date criterium is met. By default, this option is disabled and the schedule will be repeated in perpetuity.
  6. The table provides a selection of different time parameters to configure the time intervals for scheduled jobs. Jobs can occur once or recur daily or yearly. For example, you can schedule a full backup to take place every Friday at 18:00. From the tabs on the left, select one of the following:
    • once - no repetition, single run
    • daily - repetition in days, hours or minutes
    • weekly - repetition in weeks or weekdays
    • monthly - repetition on absolute or relative dates: 1st/2nd... or Mon/Tue...
    • yearly - repetition on absolute or relative dates
    • user-defined - option for setting up a custom calendar. Available on SEP sesam v. 4.4.3 or higher. See Creating Custom Calendar for details.
  7. Under Advanced settings you can further refine your schedule.
    • Optionally, use the Start time frame if you want to define the maximum allowed startup time for your event. Specify the startup time in days and/or hours. If the event cannot be executed within this specified time frame, it will not be executed at all. If this option is not enabled, the allowed start time of the task is not limited and a job can be started at any time when the resource is available.
    • You can also specify a time frame for repeating the event. Check the Repeat task box and choose how often (in hours and minutes) the task should be repeated. Use the For a duration of parameter if you want to specify the duration of the repeated event (days and/or hours).
    • Optionally, you can specify the time frame after which the scheduled event will be cancelled by checking the box in front of the Stop task if runs longer than option and specifying the amount of time (in days and/or hours) following the event's scheduled start time after which the event will be cancelled.
    Schedule-user defined 10.png


  8. Click OK to save the schedule.

SEP sesam v. 4.4.2

  1. From Main Selection -> Scheduling -> Schedules, click New schedule. The Schedule window appears.
  2. By default, Execution is already enabled. Use this option to activate or disable the schedule. If you deselect the execution option (No), the schedule will still be displayed as shaded in the list of schedules but all events linked to this schedule will be deactivated.
  3. In the Name field, enter the name for the schedule.
  4. The Cycle table provides a selection of different time parameters to configure the time intervals for scheduled jobs. Jobs can occur once or recur daily or yearly. For example, you can schedule a full backup to take place every Friday at 18:00. From the tabs on the left, select one of the following:
    • once - no repetition, single run
    • daily - repetition in days, hours or minutes
    • weekly - repetition in weeks or weekdays
    • monthly - repetition on absolute or relative dates: 1st/2nd... or Mon/Tue...
    • yearly - repetition on absolute or relative dates
  5. Under the Period of validity, specify the time range for the schedule. Click the arrows in the date field to display a calendar.
    By default, the current date is already entered in the Begin field. You can specify any date as a start time for your periodical event. The schedule will only be activated after the specified date and there can be no execution prior to this date. If you want your schedule to be valid for a limited period of time only, e.g., half a year, check the End field and enter the date of its suspension. By default, this option is disabled and the schedule will be repeated in perpetuity.
  6. Under the Start time frame, select the start time for your schedule – all events related to this schedule will be started at the time defined by this parameter. Keep in mind that the actual start time depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it may have to wait until jobs with higher priorities are completed. For jobs with the same priority, the FIFO rule (first in first out) applies. You can also limit the start time by specifying the Duration. This option specifies the amount of time in days and/or hours for which an event can be in the queue. If the event cannot be executed within the duration time frame, it will not be executed at all.
  7. New schedule bck weekly.png

  8. Click OK to save the schedule.

Step 3: Creating a backup event

By creating a backup event, you select the backup level, set event priority and specify where to back up your data to. You can create an event for a specific task or for a task group. The latter enables you to trigger all the tasks in the task group with a single event.

  1. From Main Selection -> Scheduling -> Schedules, right-click the schedule for which you want to create a new event then click New backup event.
  2. Under Sequence control, set up the Priority of your backup event. SEPuler always executes the schedules with the highest priority first. The default priority level is 1, which is the lowest priority (the highest priority is 99). The only exception are schedules with priority 0, which override all other priorities and are always executed. For details, see Setting Event Priorities. You can also enable Blocking date. This option should be used together with high priority for special events. If checked, events of the same type but of a lower priority will be blocked, ensuring that the backup will be processed even if other backups are scheduled for the same time.
  3. Under Parameter, specify the Backup level:
    A FULL backup always copies all data specified by the backup task, regardless of whether it has been changed or not. A save set created as FULL is the basic save set for subsequent DIFF or INCR save sets. While the backup time of a full backup can be significant, restore is fast and simple since only one backup save set is required. Information about the backup status is stored in the SEP sesam database. Note that the archive bits are not deleted on Windows systems. If you want to force-reset of the archive bits, you can enter the command -o clear_archive in the backup options.
    A DIFF (differential) backup saves only data which was created or changed after the last FULL save set had been created (of the same task). A differential backup is faster than a full backup, however, to restore the whole data source, first the save set of the full backup has to be restored followed by restore of the DIFF save set. For this, SEP sesam provides generation restore that enables browsing for and selecting for restore all generations of backed up files since the last full backup.
    An INCR (incremental) backup saves only data which was created or changed after the last backup (FULL, DIFF or INCR) of the same task. This is the fastest backup method and requires the least storage space. Restoring from incremental backups is the slowest, because it requires all related save sets to be copied back – the save set of the last full backup as well as all INC backups. You should consider the advantages of time and resources when planning your backup strategy. A combination of FULL backups stored to tape drives, and DIFF or INC backups stored to virtual disk media is a common method.
    A COPY backup is a full backup that has no influence on following differential (DIFF) or incremental (INCR) backups. For the treatment of archive bits, see FULL backup above. COPY backup is usually used for additional full backups, e.g., monthly backups, or backups for archiving, i.e. removal from storage.
    Information sign.png Note
    In case no initial FULL backup exists, differential (DIFF) or incremental (INCR) backups are automatically performed as FULL backups.
    For DIFF and INC backups, you can also set the Enforce FULL option. This option ensures that a FULL backup is run within the specified interval. For example, setting the number to 7 will enforce a full backup every seven days instead of an incremental or differential backup if the planned full backup fails. This ensures that a full backup is always performed within the specified time interval, in our example, once a week. However, once you have decided on your backup schedule, you should consider the advantages and disadvantages of the enforced full backup frequency, as it is slower than other backup levels and has the highest storage space requirements.
  4. From the Media pool drop-down list, select the target media pool to which the data will be backed up. If you want to enable source-side deduplication, you have to select the media pool which is combined with an Si3 deduplication store backend.
    • Optionally, specify the drive number of the drive that will be used to write the data. Typically, you use this if you have configured additional drives and you want to assign a dedicated drive exclusively for backup. For details, see option Create second drive (introduced in SEP sesam 4.4.3 Tigon) in Configuring a Data Store.
    • You can also define the Interface: from the drop-down list, select another configured TCP/IP-name of the client. You can use this option to direct the data flow over a particular network connection to enable smooth execution of backups without blocking other network activities.
  5. Optionally, enable source-side deduplication (introduced in v. 4.4.3). This check box is only available if you have a configured Si3 deduplication store and you have previously selected the Si3-related media pool.
  6. In the Follow-up Event field (introduced in v. 4.4.3) you can configure events that are triggered on the SEP sesam Server once the initial event has completed. You can set up a migration, a save set verify and other actions to be triggered immediately after a backup or other event is completed. For details, see Follow-up events.
  7. Under Object, select the task to which you want to link this event. In our example, you would link the newly created event to the task bck_seagull_all_full.
Backup event full.jpg


You can view the status of your backup jobs by selecting Last backup state in the Main selection window. The backup status overview provides detailed information on the last run of backup jobs, including the task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.

SEP Tip.png Tip
As of version 4.4.3 Grolar, you can use Migration Task option in task event properties to chose a follow up migration task.

Known issues

If you have problems with backup, check the Troubleshooting Guide.

See also

Backup 4.4Adding a Task to the Task GroupCreating Exclude ListFollow-up eventsHSM-aware Backup for WindowsStandard Restore Procedure