4 4 3 Beefalo:Backup: Difference between revisions

From SEPsesam
mNo edit summary
(Marked this version for translation)
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<noinclude><languages />
<translate>
<translate>
<!--T:1-->
<!--T:1-->
{{Template:Navigator Beefalo/en|The_SEPuler_-_an_event_calendar|The SEPuler - an event calendar|The_Restore|The Restore}}</translate></noinclude><br />
<div class="noprint"><noinclude><languages />
{{Template:Navigator Beefalo/en|SEPuler_-_an_event_calendar|SEPuler - an event calendar|Restore|Restore}}</noinclude></div></translate><br />


<translate>
==={{anchor|backup_overview}}<translate><!--T:2-->
==={{anchor|backup_overview}}Backup Overview=== <!--T:2-->
Backup Overview===


<!--T:3-->
<!--T:3-->
Backup is a process of copying and storing file system and/or application data specified by backup task to save sets onto backup media. SEP sesam supports heterogeneous computing environments and provides '''preset task types''' (note that the naming was changed from ''Backup type'' to ''Task type'' in [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']]), such as ''ordinary file system backup'' (type ''Path''), ''Exhange'', ''MySQL'', ''SAP HANA'' etc. as well as task types for ''virtual environments'' enabling image-level backups and single-file restore.
Backup is a process of copying and storing file system and/or application data specified by backup tasks to savesets onto backup media. SEP sesam supports heterogeneous computing environments and provides '''preset task types''', such as ''ordinary file system backup'' (type ''Path''), ''Exchange'', ''MySQL'', ''SAP HANA'', etc. as well as task types for ''virtual environments'' enabling image-level backups and single-file restore.


<!--T:4-->
<!--T:4-->
Backed up data on save sets is preserved according to their '''retention time'''. Data can be '''migrated''', '''deduplicated''' and '''replicated''' in order to provide fast and reliable restore.  
Backed up data on savesets is preserved according to their '''retention time'''. Data can be '''migrated''', '''deduplicated''' and '''replicated''' in order to provide fast and reliable restore.  


<!--T:5-->
<!--T:5-->
Note that standard backup does not prepare for disaster recovery. Such recovery requires special preparation and configuration with '''SEP sesam disaster recovery solutions''': [[Special:MyLanguage/Bare Metal Recovery Linux|Bare Metal Recovery Linux]], [[Special:MyLanguage/SEP sesam BSR 2.3|Bare Metal Recovery MS Windows]] and [[Special:MyLanguage/SEP_sesam_Server_Disaster_Recovery|SEP sesam self-recovery]].   
Note that standard backup does not prepare for disaster recovery. Such recovery requires special preparation and configuration with '''SEP sesam disaster recovery solutions''': [[Special:MyLanguage/Bare_Metal_Recovery_Linux|Bare Metal Recovery Linux]], [[Special:MyLanguage/SEP_sesam_BSR_Pro_for_Windows|BSR Pro for Windows]] and [[Special:MyLanguage/SEP_sesam_Server_Disaster_Recovery|SEP sesam self-recovery]].   


=====Automatic backups===== <!--T:6-->
=====Automatic backups===== <!--T:6-->


<!--T:7-->
<!--T:7-->
SEP sesam introduces a powerful scheduling service called [[Special:MyLanguage/4_4_3_Beefalo:The_SEPuler_-_an_event_calendar|SEPuler]]. It is constantly checking for backup, restore and other predefined tasks to be executed. When such a task is found, a SEPuler initiates the execution of the event. To prevent possible tasks conflicts and efficiently manage tasks in execution queue, SEP sesam uses the event priorities.
SEP sesam provides a powerful scheduling service called [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar|SEPuler]]. It is constantly checking for backup, restore and other predefined tasks to be executed. When such a task is found, SEPuler initiates the execution of the event. To prevent possible task conflicts and efficiently manage tasks in the execution queue, SEP sesam uses the event priorities.


<!--T:8-->
<!--T:8-->
You can schedule your backups to run automatically once you have configured your SEP sesam environment and created required backup tasks for the clients you wish to protect. SEP sesam provides a comprehensive and flexible schedules.  
Once you have configured your SEP sesam environment and created the required backup tasks for the clients you want to protect, you can schedule the automatic execution of your backups. SEP sesam provides a comprehensive and flexible schedules.  


<!--T:9-->
<!--T:9-->
You can create a number of schedules for any kind of events. For example, you can create a schedule ''daily'' for a number of events or configure more schedules (e.g., weekly full, daily incremental) for the same data protection. Besides the ''custom'' and ''daily'' schedule, ''weekly'', ''monthly'' and ''yearly'' are also available. Note that a schedule must have at least one event assigned to it.
You can create a number of schedules for all types of events. For example, you can create a schedule ''daily'' for a series of events or configure multiple schedules (e.g., weekly full, daily incremental) for the same data protection. In addition to the custom and daily schedules, weekly, monthly, and yearly schedules are also available. Note that a schedule must have at least one event assigned to it. For details, see [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]].  


<!--T:10-->
<!--T:10-->
[[image:Schedules_overview.png|450px|link=]]</translate>
[[image:Schedules_overview_Beefalo_V2.jpg|500px|link=]]</translate>
<br clear=all>
<br clear=all>


<!-- Here a link to a topic Standard Backup Procedure will be inserted once the procedure is described instead of inclusion of the following list. --><translate><!--T:11-->
<translate><!--T:11-->
'''Configuring automated backups consist of the following:'''
'''The configuration of automatic backups consists of the following:'''


<!--T:12-->
<!--T:12-->
Line 47: Line 47:


<!--T:16-->
<!--T:16-->
[[Special:MyLanguage/4_4_3_Beefalo:Step 5: Tasks - Select what you want to backup|Step 5: Configuring a backup task – select WHAT you want to back up]]: select the appropriate predefined task type (previously called backup type), according to which the data is backed up (default is ''Path'', others are SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphere etc.), specify the data you want to backup (''source'') and optionally set additional parameters and define pre/post scripts
[[Special:MyLanguage/4_4_3_Beefalo:Step 5: Tasks - Select what you want to back up|Step 5: Configuring a backup task – select WHAT you want to back up by selecting the source/task type]]


<!--T:17-->
<!--T:17-->
[[Special:MyLanguage/4_4_3_Beefalo:Step 6: Schedules|Step 6: Creating a schedule – select WHEN you want to back up]]: specify a start time and time interval
[[Special:MyLanguage/4_4_3_Beefalo:Step 6: Schedules|Step 6: Creating a schedule – select WHEN and at what interval you want to back up]]


<!--T:18-->
<!--T:18-->
[[Special:MyLanguage/4_4_3_Beefalo:Schedules#new_backup_event|Step 7: Creating a backup event – select HOW and WHERE to back up]]: specify [[Special:MyLanguage/4_4_3_Beefalo:The Backup#backup_level|backup level]] (FULL, DIFF, INC, COPY), event priority and define a target media pool
[[Special:MyLanguage/Creating_a_Backup_Event|Step 7: Creating a backup event – select HOW (backup level: FULL, DIFF, INC, COPY) and WHERE to backup]]
 
<!--T:63-->
For details, see also [[Special:MyLanguage/Standard Backup Procedure|Standard Backup Procedure]].</translate>


====={{anchor|backup_level}}Backup level (C, F, D, I)===== <!--T:19-->
====={{anchor|backup_level}}<translate><!--T:19-->
Backup level (C, F, D, I)=====  


<!--T:20-->
<!--T:20-->
When creating a [[Special:MyLanguage/4_4_3_Beefalo:Schedules#new_backup_event|backup event]] in the '''Main Selection''' -> '''Scheduling''' -> '''Schedules''' -> '''New backup event''', you also specify the backup level (note that the naming was changed from ''Backup type'' to ''Backup level'' in [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']].
When creating a [[Special:MyLanguage/Creating_a_Backup_Event|backup event]] in the '''Main Selection''' -> '''Scheduling''' -> '''Schedules''' -> '''New Backup Event''', you also have to specify the backup level.


<!--T:21-->
<!--T:21-->
[[image:backup_event-backup_level_type-part.png|link=]]</translate>
[[image:Backup_event-backup_level_Beefalo_V2.jpg|380px|link=]]</translate>
<br clear=all>
<br clear=all>
<translate>{{:Backup Level/en}}
<translate><!--T:61-->
{{:Backup Level/en}}</translate>


====={{anchor|parallel}}Parallel Backups===== <!--T:22-->
====={{anchor|parallel}}<translate><!--T:22-->
Parallel Backups=====


<!--T:52-->
<!--T:52-->
SEP sesam supports parallel i.e. simultaneous backup of multiple data sources onto one drive. This is called '''Sesam Multiplex Stream (SMS)'''.
SEP sesam supports parallel, i.e., simultaneous backup of multiple data sources onto one drive. This is called '''Sesam Multiplex Stream (SMS)'''.
 
<!--T:23-->
Modern tape drive manufacturers are dramatically increasing device performance and capacity. Few of today's backup software products are able to fully utilize the new functionality to its greatest advantage. The drive is often in a 'stopped' or waiting mode for data from the backup source.
 
<!--T:24-->
SEP sesam is one of the few backup software products that can be used for receiving data from other backup sources. '''Sesam Multiplex Stream''' now offers up to 124 channels for a single drive. Each of 124 channels can serve one backup source.


<!--T:25-->
<!--T:25-->
Data of the different streams are distributed into packets, each packet is supplied with an identification mark and copied to the backup media. The data of a certain stream is not contiguously positioned on the media, but interrupted by packets of other streams. The identification marker of the packets enables SMS to restore the initial stream during reading.
The data from the different streams is distributed into packets, each packet is given an identifier and copied to the backup media. The data of a particular stream is not contiguous on the media, but is interrupted by packets of other streams. The identifier of the packets allows SMS to restore the initial stream during reading.


<!--T:26-->
<!--T:26-->
Furthermore, SMS is able to split save sets across several media that still have some free space left (specified by media properties parameter ''EOM'' – End of Media).
In addition, SMS can split savesets across multiple media where free space is still available (indicated by [[Special:MyLanguage/SEP_sesam_Glossary#EOM|''EOM'']]).


<!--T:27-->
<!--T:27-->
The '''maximum number of parallel streams''' that can be used during backup to the backup drive is specified under the '''Drive properties''' by parameter ''Max. channels''. Note that '''the number of available data streams''' depends on the '''type of Server License''', e.g., ''ONE'' provides ''1'' backup stream, ''Standard'' provides ''5'' backup streams while ''Advanced'' provides ''unlimited'' number of streams (dependent on the system configuration and available throughput).  
The '''maximum number of parallel streams''' that can be used during backup to the backup drive is set in the '''Drive properties''' by the ''Max. channels'' parameter. The number of available streams depends on the type of server license. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Drives#new_drive|Drives]].</translate>


<!--T:28-->
====={{anchor|encryption}}<translate><!--T:29-->
For details, see [[Special:MyLanguage/4_4_3_Beefalo:Drives#new_drive|Drives]].
Encryption=====
 
SEP sesam provides data encryption on different levels: '''backup-task encryption for savesets''' (set in the backup task), '''Si3 encryption for Si3 deduplication store''' (set in Si3 deduplication store properties), and '''hardware-based LTO encryption for LTO tape drives''' (at the media pool level).</translate> <translate><!--T:53-->
====={{anchor|encryption}}Encryption===== <!--T:29-->
For details on the latter two, see [[Special:MyLanguage/LTO_Encryption|LTO Encryption]] and [[Special:MyLanguage/Encrypting_Si3_NG_Deduplication_Store|Encrypting Si3 NG Deduplication Store]]. See also [[Special:MyLanguage/4_4_3_Beefalo:Encryption_Support_Matrix|Encryption Support Matrix]].  
SEP sesam provides data encryption types on different levels: '''backup-task encryption for savesets''' (explained below, set in the backup task), '''Si3 encryption for Si3 deduplication store''' (set in the Si3 deduplication store properties), and '''hardware-based LTO encryption for LTO tape drives''' (done on a media pool level).</translate> <translate><!--T:53-->
For details on the latter two, see [[Special:MyLanguage/LTO_Encryption|LTO Encryption]] and [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]]. See also [[Special:MyLanguage/4_4_3_Beefalo:Encryption_Support_Matrix|Encryption Support Matrix]].  


<!--T:30-->
<!--T:30-->
SEP sesam encryption for save sets can be enabled in the '''backup task properties''' under the tab ''Encryption and compression'' for each backup task. Supported encryption algorithms are the ''Advanced Encryption Standard (AES)'' 256-bit encryption and the ''Blowfish'' encryption.</translate><translate> <!--T:54-->
SEP sesam backup-task encryption for savesets can be enabled ''when creating a backup task'' or in the ''backup task properties'' under the tab ''Encryption & Compression''. Supported encryption algorithms are ''Advanced Encryption Standard (AES)'' 256-bit encryption and ''Blowfish (bf64)'' encryption.</translate>
You can select the type of encryption by clicking the '''Encryption and compression''' tab in the ''backup task'' window (''Main Selection'' -> ''Tasks'' -> ''By clients'' -> select a client and a task, and double-click to open the properties window).


<!--T:31-->
<translate><!--T:31--> You must create an encryption key for the data to be encrypted, but you can decide whether the encryption key (password) is stored in the SEP sesam results database or not. </translate>
You must create an encryption key for the data to be encrypted, but you can decide whether the encryption key (password) will be stored into SEP sesam results database or not. If the '''encryption key''' is '''not stored by SEP sesam''', you will be prompted to enter it before the restore is started in the restore wizard.
*<translate><!--T:64--> If the '''encryption key''' is '''not stored by SEP sesam''', you will be prompted to enter it before starting the restore in the restore wizard.</translate>
 
*<translate><!--T:32-->
<!--T:32-->
If the '''encryption key is stored''' in the SEP sesam database, the key itself is also encrypted and automatically used for decryption during restore. The data is encrypted before it is transferred over the network and copied to a saveset.  
If the '''encryption key is stored''' in the SEP sesam database, the key itself is also encrypted and is used automatically for decryption during restore. Data is encrypted before it is transferred over the network and copied to a save set.
 
<!--T:33-->
You can determine which backup tasks are encrypted by checking the backup task properties, where you can also reset your password, or in the backup results table (''Main selection'' -> ''Job state'' -> ''Backups'' -> double-click the selected task to display its properties and look for the ''Encryption'' field).


<!--T:34-->
<!--T:34-->
If you change the encryption key, all backups started after the password has been changed will be encrypted with the new key. This new key will be stored with the backup and you will have to enter the password to restore your data.
If you change the encryption key, all backups started after the password is changed will be encrypted with the new key. This new key will be stored with the backup and you will have to enter the password to restore your data.


<!--T:35-->
<!--T:35-->
{{note|A password cannot be longer than 28 characters and may not use any special characters (underscore, hyphen, etc.) Spaces are also not permitted.}}
{{note|A password cannot be longer than 28 characters and cannot contain special characters (underscore, hyphen, etc.) Spaces are also not allowed.}}


<!--T:36-->
<!--T:36-->
''Setting encryption''<br />
''Setting encryption''<br />
[[image:New_backup_task_encryption.png|link=]]</translate>
[[image:New_backup_task_encryption_Beefalo_V2.jpg|700px|link=]]</translate>
<br clear=all>
<br clear=all>


<translate>===={{anchor|VSS_on_Windows}}Backup with VSS (Volume Shadow Copy Service) on Windows==== <!--T:37-->
<translate><!--T:33--> You can determine which backup tasks are encrypted by checking the backup task properties, tab ''Encryption and Compression'', where you can also reset your password. You can also check the GUI backup results table (''Main selection'' -> ''Job state'' -> ''Backups'' -> double-click the selected task to open its properties and look for the ''Encryption'' field under ''Info 2'') or check the backup task properties in ''Web UI'' (click the backup task under Monitoring -> ''Last backup state'' or ''Backups''), ''Settings'' row. See [[Special:MyLanguage/SEP sesam Web UI|SEP sesam Web UI]] for details.</translate>
 
===={{anchor|VSS_on_Windows}}<translate><!--T:37-->
Backup with VSS (Volume Shadow Copy Service) on Windows====  


<!--T:55-->
<!--T:55-->
Line 122: Line 118:


<!--T:38-->
<!--T:38-->
''From SEP sesam client version 4.0'', every '''file system – ''Path'' backup of a Windows client''' has the option to '''backup with VSS enabled by default'''. This option is available in the backup task properties and should only be used with the [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]] (previously called backup type) ''Path''. All other task types, for example ''System state'', use the required VSS writer by default.  
Backup with VSS is enabled by default for the file system task type ''Path''. All other task types, for example ''System State'', use the required VSS writer by default.  


<!--T:39-->
<!--T:39-->
For details on SEP sesam VSS, how to activate/deactivate VSS and exclude a VSS writer from backup manually, see [[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows|SEP sesam Volume Shadow Copy Service (VSS) for Windows]].
For details on SEP sesam VSS, how to activate/deactivate VSS and manually exclude a VSS writer from backup, see [[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows|SEP sesam Volume Shadow Copy Service (VSS) for Windows]].</translate>


===={{anchor|NDMP_backup}}NDMP backup==== <!--T:40-->
===={{anchor|NDMP_backup}}<translate><!--T:40-->
NDMP backup====


<!--T:56-->
<!--T:56-->
As of version 4.4.3., SEP sesam enables you to '''protect and manage your storage file servers''' by providing support for Network Data Management Protocol. NDMP is a common protocol for backing up and restoring data on storage devices that do not support installation of a backup agent.  
SEP sesam enables you to '''protect and manage your storage file servers''' by providing support for Network Data Management Protocol. NDMP is a common protocol for backing up and restoring data on storage devices that do not support the installation of a backup agent.  


<!--T:41-->
<!--T:41-->
It ensures interoperability between NAS file servers and SEP sesam, and is used as an interface that enables SEP sesam to backup various NAS appliances and copy this data to a SEP sesam Server or Remote Device Server. SEP sesam supports ''version 4 of the NDMP protocol''.  
It ensures interoperability between NAS file servers and SEP sesam, and is used as an interface that enables SEP sesam to back up various NAS appliances and copy this data to a SEP sesam Server or Remote Device Server. SEP sesam supports ''version 4 of the NDMP protocol''.  


<!--T:42-->
<!--T:42-->
For details, see [[Special:MyLanguage/4_4_3_Grolar:NDMP_Backup|NDMP Backup]]. For a list of supported NAS appliances, see the[[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#NDMP| support matrix]]. For details on backing up the NetApp NFS volumes via NFS, see [[Special:MyLanguage/Netapp_en|NetApp Volume Backup]].
For details, see [[Special:MyLanguage/NDMP_Backup|NDMP Backup]]. For a list of supported NAS appliances, see the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#NDMP|support matrix]]. For details on backing up NetApp NFS volumes via NFS, see [[Special:MyLanguage/NetApp_CIFS_Backup|NetApp Volume Backup]].</translate>


===={{anchor|HSM_aware_backup}}HSM-aware backup for Windows==== <!--T:43-->
===={{anchor|HSM_aware_backup}}<translate><!--T:43-->
HSM-aware backup for Windows====  


<!--T:57-->
<!--T:57-->
'''Hierarchical Storage Management''' (HSM) is a method for reducing the costs of data storage and facilitating data management tasks. Starting with SEP sesam version 4.4.2, '''HSM-aware backup for Windows''' comes as an integral part of the SEP sesam package.  
'''Hierarchical Storage Management''' (HSM) is a method for reducing the costs of data storage and facilitating data management tasks. '''HSM-aware backup for Windows''' is an integral part of the SEP sesam package.  


<!--T:44-->
<!--T:44-->
It provides efficient backup of data on Windows systems that is managed by HSM. SEP sesam as an HSM-aware solution '''recognises the reparse tags''' in stub files and does not trigger a recall of the original files, but '''performs a backup of the placeholder files''' without retrieving their contents. For more details, see [[Special:MyLanguage/HSM-aware Backup for Windows|HSM-aware Backup for Windows]].
It provides efficient backup of data on Windows systems that is managed by HSM. SEP sesam as an HSM-aware solution '''recognises the reparse tags''' in stub files and does not trigger a recall of the original files, but '''performs a backup of the placeholder files''' without retrieving their contents. For more details, see [[Special:MyLanguage/HSM-aware Backup for Windows|HSM-aware Backup for Windows]].</translate>


===={{anchor|NTFS_ADS}}Support for NTFS alternate data streams (ADS) for Windows==== <!--T:45-->
===={{anchor|NTFS_ADS}}<translate><!--T:45-->
Support for NTFS alternate data streams (ADS) for Windows====  


<!--T:58-->
<!--T:58-->
As of version 4.4.3, ADS are backed up by default when backing up an NTFS file system. They are automatically restored to any ADS-aware system. ADS are backed up by default, but can be excluded from backup by using a special option in the backup task properties.
ADS are backed up by default when backing up an NTFS file system. They are automatically restored to any ADS-aware system. ADS are backed up by default, but can be excluded from backup by using a special option in the backup task properties.


<!--T:46-->
<!--T:46-->
Alternate data streams are a unique data-hiding feature of NTFS file systems. A file in NTFS consists of the ''unnamed data stream'' where the data is actually contained, and of ''alternate data streams'' that can store additional metadata. Applications may use ADS for storing file attributes. For details, see [[Special:MyLanguage/Support_for_NTFS_alternate_data_streams_(ADS)_for_Windows|Support for NTFS alternate data streams (ADS) for Windows]].</translate>
Alternate data streams are a unique data-hiding feature of NTFS file systems. A file in NTFS consists of the ''unnamed data stream'' where the data is actually contained, and of ''alternate data streams'' that can store additional metadata. Applications may use ADS for storing file attributes. For details, see [[Special:MyLanguage/Support_for_NTFS_alternate_data_streams_(ADS)_for_Windows|Support for NTFS alternate data streams (ADS) for Windows]].</translate>
==={{anchor|sparse_support}}<translate><!--T:65-->
Support for Linux sparse files===
<!--T:66-->
SEP sesam provides support for Linux sparse files to prevent running out of disk space during restore. For details on how SEP sesam handles sparse files and what options are available, see [[Special:MyLanguage/Support_for_Sparse_Files|Support for Sparse Files]].</translate>
==={{anchor|LVM}}<translate><!--T:67-->
SEP sesam Logical Volume Manager (LVM) for Linux===
<!--T:68-->
SEP sesam uses LVM (Logical Volume Manager) snapshots to perform consistent backups of open files on Linux distributions. LVM snapshots allow a frozen copy of the file system to be backed up without taking the "live" volume offline during the backup.
<!--T:69-->
LVM snapshots only work with partitions created with LVM. For more details, see [[Special:MyLanguage/SEP_sesam_Logical_Volume_Manager_(LVM)_for_Linux|SEP sesam LVM for Linux]].</translate>


<div class="noprint"><noinclude>
<div class="noprint"><noinclude>
<translate>===See also=== <!--T:47-->
<translate><!--T:47-->
[[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]] – [[Special:MyLanguage/4_4_3_Grolar:NDMP_Backup|NDMP Backup]] </translate>–<translate> <!--T:59-->
===See also===
[[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]] – [[Special:MyLanguage/NDMP_Backup|NDMP Backup]] </translate>–<translate> <!--T:59-->
[[Special:MyLanguage/HSM-aware_Backup_for_Windows|HSM-aware Backup for Windows]] – [[Special:MyLanguage/Support_for_NTFS_alternate_data_streams_(ADS)_for_Windows|Support for NTFS alternate data streams (ADS) for Windows]] </translate>– <translate><!--T:60-->
[[Special:MyLanguage/HSM-aware_Backup_for_Windows|HSM-aware Backup for Windows]] – [[Special:MyLanguage/Support_for_NTFS_alternate_data_streams_(ADS)_for_Windows|Support for NTFS alternate data streams (ADS) for Windows]] </translate>– <translate><!--T:60-->
[[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows|SEP sesam Volume Shadow Copy Service (VSS) for Windows]] – [[Special:MyLanguage/4_4_3_Beefalo:Encryption_Support_Matrix|Encryption Support Matrix]]</translate></noinclude></div>
[[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows|SEP sesam Volume Shadow Copy Service (VSS) for Windows]] – [[Special:MyLanguage/Support_for_Sparse_Files|Support for Sparse Files]] – [[Special:MyLanguage/SEP_sesam_Logical_Volume_Manager_(LVM)_for_Linux|SEP sesam LVM for Linux]] – [[Special:MyLanguage/4_4_3_Beefalo:Encryption_Support_Matrix|Encryption Support Matrix]]</translate>
<translate><!--T:62--> {{Footer/en}}</translate></noinclude></div>

Latest revision as of 08:52, 22 May 2023

Other languages:
<<<Back
SEPuler - an event calendar		 ↑ User Manual ↑
 Next>>>
Restore


Backup Overview

Backup is a process of copying and storing file system and/or application data specified by backup tasks to savesets onto backup media. SEP sesam supports heterogeneous computing environments and provides preset task types, such as ordinary file system backup (type Path), Exchange, MySQL, SAP HANA, etc. as well as task types for virtual environments enabling image-level backups and single-file restore.

Backed up data on savesets is preserved according to their retention time. Data can be migrated, deduplicated and replicated in order to provide fast and reliable restore.

Note that standard backup does not prepare for disaster recovery. Such recovery requires special preparation and configuration with SEP sesam disaster recovery solutions: Bare Metal Recovery Linux, BSR Pro for Windows and SEP sesam self-recovery.

Automatic backups

SEP sesam provides a powerful scheduling service called SEPuler. It is constantly checking for backup, restore and other predefined tasks to be executed. When such a task is found, SEPuler initiates the execution of the event. To prevent possible task conflicts and efficiently manage tasks in the execution queue, SEP sesam uses the event priorities.

Once you have configured your SEP sesam environment and created the required backup tasks for the clients you want to protect, you can schedule the automatic execution of your backups. SEP sesam provides a comprehensive and flexible schedules.

You can create a number of schedules for all types of events. For example, you can create a schedule daily for a series of events or configure multiple schedules (e.g., weekly full, daily incremental) for the same data protection. In addition to the custom and daily schedules, weekly, monthly, and yearly schedules are also available. Note that a schedule must have at least one event assigned to it. For details, see Creating a Schedule.

Schedules overview Beefalo V2.jpg

The configuration of automatic backups consists of the following:

Step 1: Setting up your backup environment

Step 2: Configuring clients

Step 3: Configuring storage hardware – drives and loaders

Step 4: Preparing backup media

Step 5: Configuring a backup task – select WHAT you want to back up by selecting the source/task type

Step 6: Creating a schedule – select WHEN and at what interval you want to back up

Step 7: Creating a backup event – select HOW (backup level: FULL, DIFF, INC, COPY) and WHERE to backup

For details, see also Standard Backup Procedure.

Backup level (C, F, D, I)

When creating a backup event in the Main Selection -> Scheduling -> Schedules -> New Backup Event, you also have to specify the backup level.

Backup event-backup level Beefalo V2.jpg
Backup Level/en

Parallel Backups

SEP sesam supports parallel, i.e., simultaneous backup of multiple data sources onto one drive. This is called Sesam Multiplex Stream (SMS).

The data from the different streams is distributed into packets, each packet is given an identifier and copied to the backup media. The data of a particular stream is not contiguous on the media, but is interrupted by packets of other streams. The identifier of the packets allows SMS to restore the initial stream during reading.

In addition, SMS can split savesets across multiple media where free space is still available (indicated by EOM).

The maximum number of parallel streams that can be used during backup to the backup drive is set in the Drive properties by the Max. channels parameter. The number of available streams depends on the type of server license. For details, see Drives.

Encryption

SEP sesam provides data encryption on different levels: backup-task encryption for savesets (set in the backup task), Si3 encryption for Si3 deduplication store (set in Si3 deduplication store properties), and hardware-based LTO encryption for LTO tape drives (at the media pool level). For details on the latter two, see LTO Encryption and Encrypting Si3 NG Deduplication Store. See also Encryption Support Matrix.

SEP sesam backup-task encryption for savesets can be enabled when creating a backup task or in the backup task properties under the tab Encryption & Compression. Supported encryption algorithms are Advanced Encryption Standard (AES) 256-bit encryption and Blowfish (bf64) encryption.

You must create an encryption key for the data to be encrypted, but you can decide whether the encryption key (password) is stored in the SEP sesam results database or not.

  • If the encryption key is not stored by SEP sesam, you will be prompted to enter it before starting the restore in the restore wizard.
  • If the encryption key is stored in the SEP sesam database, the key itself is also encrypted and automatically used for decryption during restore. The data is encrypted before it is transferred over the network and copied to a saveset.

If you change the encryption key, all backups started after the password is changed will be encrypted with the new key. This new key will be stored with the backup and you will have to enter the password to restore your data.

Information sign.png Note
A password cannot be longer than 28 characters and cannot contain special characters (underscore, hyphen, etc.) Spaces are also not allowed.

Setting encryption
New backup task encryption Beefalo V2.jpg

You can determine which backup tasks are encrypted by checking the backup task properties, tab Encryption and Compression, where you can also reset your password. You can also check the GUI backup results table (Main selection -> Job state -> Backups -> double-click the selected task to open its properties and look for the Encryption field under Info 2) or check the backup task properties in Web UI (click the backup task under Monitoring -> Last backup state or Backups), Settings row. See SEP sesam Web UI for details.

Backup with VSS (Volume Shadow Copy Service) on Windows

Microsoft Volume Shadow Copy Service (VSS) is a Windows service for backing up running applications. VSS coordinates with other VSS-aware applications and services, and creates a shadow copy or snapshot of data for backup purposes. VSS uses a copy-on-write snapshot, allocating a small temporary storage space for it. Once the snapshot is completed, the temporary storage space is freed up again.

Backup with VSS is enabled by default for the file system task type Path. All other task types, for example System State, use the required VSS writer by default.

For details on SEP sesam VSS, how to activate/deactivate VSS and manually exclude a VSS writer from backup, see SEP sesam Volume Shadow Copy Service (VSS) for Windows.

NDMP backup

SEP sesam enables you to protect and manage your storage file servers by providing support for Network Data Management Protocol. NDMP is a common protocol for backing up and restoring data on storage devices that do not support the installation of a backup agent.

It ensures interoperability between NAS file servers and SEP sesam, and is used as an interface that enables SEP sesam to back up various NAS appliances and copy this data to a SEP sesam Server or Remote Device Server. SEP sesam supports version 4 of the NDMP protocol.

For details, see NDMP Backup. For a list of supported NAS appliances, see the support matrix. For details on backing up NetApp NFS volumes via NFS, see NetApp Volume Backup.

HSM-aware backup for Windows

Hierarchical Storage Management (HSM) is a method for reducing the costs of data storage and facilitating data management tasks. HSM-aware backup for Windows is an integral part of the SEP sesam package.

It provides efficient backup of data on Windows systems that is managed by HSM. SEP sesam as an HSM-aware solution recognises the reparse tags in stub files and does not trigger a recall of the original files, but performs a backup of the placeholder files without retrieving their contents. For more details, see HSM-aware Backup for Windows.

Support for NTFS alternate data streams (ADS) for Windows

ADS are backed up by default when backing up an NTFS file system. They are automatically restored to any ADS-aware system. ADS are backed up by default, but can be excluded from backup by using a special option in the backup task properties.

Alternate data streams are a unique data-hiding feature of NTFS file systems. A file in NTFS consists of the unnamed data stream where the data is actually contained, and of alternate data streams that can store additional metadata. Applications may use ADS for storing file attributes. For details, see Support for NTFS alternate data streams (ADS) for Windows.

Support for Linux sparse files

SEP sesam provides support for Linux sparse files to prevent running out of disk space during restore. For details on how SEP sesam handles sparse files and what options are available, see Support for Sparse Files.

SEP sesam Logical Volume Manager (LVM) for Linux

SEP sesam uses LVM (Logical Volume Manager) snapshots to perform consistent backups of open files on Linux distributions. LVM snapshots allow a frozen copy of the file system to be backed up without taking the "live" volume offline during the backup.

LVM snapshots only work with partitions created with LVM. For more details, see SEP sesam LVM for Linux.

See also

Standard Backup Procedure – NDMP Backup – HSM-aware Backup for Windows – Support for NTFS alternate data streams (ADS) for Windows – SEP sesam Volume Shadow Copy Service (VSS) for Windows – Support for Sparse Files – SEP sesam LVM for Linux – Encryption Support Matrix

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

Retrieved from "https://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:Backup&oldid=300503"