- SEP sesam Jaglion
- SEP volume licensing recommended
- An active Wasabi account
This section describes how to configure and use a Wasabi S3 bucket as a target for backup data from the backup software SEP sesam. Using S3 as a backup target in SEP sesam always implicates the usage of the SEP Si3 NG deduplication functionality.
As the S3 bucket is represented in the SEP sesam UIs the same way as any other deduplication store (disk storage) it can be used for any kind of scenarios:
- As a primary backup target
- As a replication target from local to the cloud
- As a target for source side deduplication
- As a source for data migration to other targets e.g. tape
- As a replication source to another S3 target (local object storage or multi cloud strategy)
SEP sesam enables you to back up your data directly to S3 cloud storage using the Si3 NG deduplication store.
6. The name in Create new drive group is already created. You can change it by simply entering a new name.
7. The predefined number of channels is already available in the channels drop-down list. The number of available channels depends on your SEP sesam Server package.
8. From the Device server drop-down list, select the device server for your data store.
9. In the Path field, enter the location or use the Browse button to select a directory on the local disk (as for local storage). This directory is only used to store metadata and temporary files for intermediate storage until the data is uploaded to S3. Ensure that there is sufficient disk-space available for this local storage, e.g., for 50 TiB in S3 or more, make sure it has 20 GiB free space. Click OK.
If you use the Browse button, the New Data Store information window appears with predefined recommended values for the size of your Si3 NG deduplication store, based on the size of the previously selected local disk (Path).
Important: Change these values manually under the Size properties, depending on how much storage space you want to use on S3.
- Capacity: Set the size (in GB/GiB) of the storage for backups.
- High watermark: The HWM defines the upper value for the used storage space. When this value is reached, the status of a datastore changes from OKto Warning, but backups continue to be performed. Make sure that you provide enough storage space for your backed up data.
Click OK. You can also change the size of your Si3 NG deduplication store later under Size properties.
- Name: Enter a name for a media pool.
- Description: Optionally, add a description of the pool.
- Drive group: From the drop-down list of all available drive groups, select the relevant drive group to which a media pool will be attached.
- Retention time [days]: Specify the retention time for the media pool. The retention period begins with the date a saveset is written to the media (at the end time of the first backup) and thus defines the expiry date of the saveset - EOL. When the protection (EOL) expires, SEP sesam can use the media for backups again.
You can repeat the procedure and create more media pools for Si3 NG according to your needs.
- Create a backup task to back up to S3 as described in Creating a backup task.
- Configure a schedule as described in Creating a Schedule.
Once you have configured a task and schedule, create a backup event as follows.
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.
13. From Main Selection -> Scheduling -> Schedules, right-click the schedule you created earlier and click New Backup Event.
14. In the New Backup Event dialog box, provide the following details:
- Under the Sequence control, set 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.
You can also enable the Blocking date. This option should be used together with the high priority for special events. When this option is enabled, events of the same type but with a lower priority are blocked, so that the backup is executed even if other backups are scheduled for the same time.
- Under Object, select the task (or task group) you configured earlier and with which you want to link this event.
- Under Parameter, specify the Backup level.
- From the Media pool drop-down list, select the media pool you created for the Si3 NG deduplication store. The data is backed up to this pool. You can also activate the option SEP Si3 source-side deduplication.
- Optionally, specify the drive number of the drive to be used to write the data. Typically, you use this option if you have configured additional drives and want to assign a specific drive exclusively for backup.
- In the Follow up field, you can configure events (e.g., migration) that are triggered on the SEP sesam Server as soon as the first event (e.g., backup) is completed.
Note: You can set a follow-up migration task by selecting the previously configured migration task
from the Migration task drop-down list.
You can view the status of your backup jobs in the GUI (Monitoring -> Last Backup State or Job State -> Backups) or SEP sesam Web UI. The backup status overview provides detailed information about 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.
To learn more about Monitoring, please click here.
Data purging is the process of permanently deleting obsolete (EOL-free) savesets from regular data stores. It works in the same way in the S3 cloud. The purge is automatically triggered and performed until all EOL-free savesets are deleted.
Strategies for data purging are based on the nature of your business, as well as regulatory, legal and other requirements, and implemented with a defined data retention period. This is the period of time for which backup data is protected after it is written to the media, so that the savesets are preserved and available for restore. It is based on the media pool retention time you set when you created a media pool. SEP sesam provides automatic EOL (retention) management to ensure recoverability of the entire backup chain and protect against data loss, based on the backup chain dependencies.
When protection (EOL) expires, purging is done automatically and SEP sesam can use the media for backups again.
Events that trigger the data store purge are:
- Manual start of the purge in the GUI
15. You can manually adjust the EOL of your data or expire a saveset or backup
16. You can start the data store purge process in the GUI: Main Selection window -> Components-> Data Stores content pane -> Purge. Running the purge manually deletes the obsolete (EOL-free) savesets.
17. Another way to free up storage space is to remove orphaned savesets from the data stores by using the Clean up option: Main Selection window -> Components -> Data Stores content pane -> Clean up. This is useful if a data store seems to be inaccessible, its space is occupied, or SEP sesam space check shows non-sesam data