Source:SEP sesam Configuration – First Steps: Difference between revisions
(Update in progress.) |
(Rewritten.) |
||
Line 10: | Line 10: | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" |<translate><!--T:4--> | | rowspan="2" style="padding:0px 10px 0px;" |<translate><!--T:4--> | ||
[[File:SEP_next.png|45px|link=Special:MyLanguage/ | [[File:SEP_next.png|45px|link=Special:MyLanguage/Standard_Backup_Procedure]]</translate> | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:5--> | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:5--> | ||
See also: [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]]</translate> | See also: [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]] – [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]]</translate> | ||
|} | |} | ||
Line 45: | Line 45: | ||
The following screenshot shows the backup environment, which consists of several locations. | The following screenshot shows the backup environment, which consists of several locations. | ||
[[Image:Locations_Beefalo_V2.jpg| | [[Image:Locations_Beefalo_V2.jpg|760px|link=]]</translate> | ||
<br clear=all> | <br clear=all> | ||
Line 54: | Line 54: | ||
<translate><!--T:25--> | <translate><!--T:25--> | ||
[[Image:Topology_new_client_Beefalo_V2.jpg| | [[Image:Topology_new_client_Beefalo_V2.jpg|760px|link=]]</translate> | ||
<br clear=all> | <br clear=all> | ||
Line 60: | Line 60: | ||
For client connection issues, see [[Special:MyLanguage/FAQ#client_full_access|How to verify that the SEP sesam server has full access to a specific client]]. | For client connection issues, see [[Special:MyLanguage/FAQ#client_full_access|How to verify that the SEP sesam server has full access to a specific client]]. | ||
===Step 3 – Backup | ===Step 3 – Backup hardware: Where should the data be stored?=== <!--T:27--> | ||
<!--T:28--> | <!--T:28--> | ||
During the installation process, SEP sesam checks the SCSI-bus for connected backup hardware and enters its data in the SEP sesam database. | During the installation process, SEP sesam checks the SCSI-bus for connected backup hardware and enters its data in the SEP sesam database. | ||
SEP sesam data store is a device type used for writing the savesets directly on one or several configured storage locations – into the file system. SEP sesam uses a data store instead of a conventional media pool to define storage repository. The data is still primarily backed up to a media pool, however, a data store is used underneath to save data to dynamically managed data areas, including disk backups. | |||
SEP sesam can contain multiple data stores of different types (e.g., ''Path'', ''SEP Si3 deduplication store'', etc.) and sizes based on the type of data being backed up, backup technique, and on your storage location (a local disk, virtualized storage device, storage appliances, etc.). | |||
You can configure your data stores under '''Main Selection''' -> '''Components''' -> '''Data Stores''' -> '''New Data Store'''. For details, see [[Special:MyLanguage/Configuring_a_Data_Store|Configuring a Data Store]]. | |||
<!--T: | ===Step 4 – Tasks: What should be backed up?=== <!--T:30--> | ||
A backup task defines which savesets are backed up and which data should be excluded from backup. To create a backup task, in the '''Main Selection''' -> '''Tasks''' -> '''By Clients''', right-click the client and select '''New Backup Task'''. In case of the Windows clients, you have to make sure that the option ''VSS'' is enabled during the backup task creation. For more information, see [[Special:MyLanguage/Creating_a_Backup_Task|Creating a Backup Task]]. | |||
In the | |||
[[Image:Configuration_new_bck_task_Beefalo_V2.jpg|760px|link=]]</translate> | |||
<br clear=all> | |||
<translate>Additionally, you can assign individual backup tasks to a task group and then trigger the start of all tasks belonging to that group with a single event. It is recommended that you create a task group for each task type, for example, VMs, application, etc. You can group the backup tasks under '''Main Selection''' -> '''Tasks''' -> '''By Groups''' -> '''New Task Group'''. For details, see [[Special:MyLanguage/Adding_a_Task_to_the_Task_Group|Adding a Task to the Task Group]].</translate> | |||
<translate><!--T: | <translate><!--T:42--> | ||
[[Image: | [[Image:Configuration_task_group_Beefalo_V2.jpg|760px|link=]]</translate> | ||
<br clear=all> | <br clear=all> | ||
<translate> | <translate>If you want to start the backup task or task group immediately, right-click the task/task group and click '''Immediate Start''', see [[Special:MyLanguage/4_4_3_Beefalo:Activities#immediate_start_backup|Immediate Start: Backup]]. Otherwise you have to schedule your backup task/task group. | ||
===Step 5 – Schedules: When should the data be backed up?=== <!--T:43--></translate> | |||
<translate> | <translate> | ||
If you want to create a periodic backup, you have to schedule your backup task(s). 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 only once. You can create a new schedule under '''Main Selection''' -> '''Scheduling''' -> '''Schedules''' -> '''New Schedule'''. For more details, see [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]]. | |||
The following schedules are recommended:</translate> | |||
* <translate><!--T:45--> | * <translate><!--T:45--> | ||
Line 129: | Line 112: | ||
<translate><!--T:51--> | <translate><!--T:51--> | ||
[[Image: | [[Image:Configuration_schedules_Beefalo_V2.jpg|750px|link=]]</translate> | ||
<br clear=all> | <br clear=all> | ||
<translate> | <translate>For a one-time execution of the schedule, right-click on the schedule and select '''Immediate Start'''. Otherwise you have to link a backup event to it. | ||
For a one-time execution of the schedule, right-click on the schedule and select '''Immediate Start'''. | |||
===Step 6 – Backup event: How should the backup start?=== <!--T:55--> | ===Step 6 – Backup event: How should the backup start?=== <!--T:55--> | ||
<!--T:56--> | <!--T:56--> | ||
After you have created a schedule, you have to link a backup event to it to configure a periodic backup. In the '''Main Selection''' -> '''Scheduling''' -> '''Schedules''', right-click the schedule and select '''New Backup Event'''. | |||
You have to create a new backup event for each schedule and insert it into the SEP sesam calendar, which will then be executed by the [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar|SEPuler]] at the appointed time. For details on how to create a backup event, see [[Special:MyLanguage/Creating_a_Backup_Event|Creating a Backup Event]]. | |||
<!--T:58--> | <!--T:58--> | ||
[[Image: | [[Image:Configuration_bck_event_Beefalo_V2.jpg|780px|link=]]</translate> | ||
<br clear=all> | <br clear=all> | ||
<translate><!--T:59--> | <translate><!--T:59--> | ||
The system is now completely configured and will execute the new backup jobs at the appointed time. After the backup | The system is now completely configured and will execute the new backup jobs at the appointed time. After the backup has been executed, you can check your backup jobs from the '''Main Selection''' -> '''Scheduling''' -> '''Calendar Sheet''' or '''Main Selection''' -> '''Job State''' -> '''Backups'''. | ||
{{Note|As of [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], you can check the details of your backups online by using new Web UI. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Web_UI|SEP sesam Web UI]].}} | |||
<div class="noprint"> | <div class="noprint"> | ||
==See also== <!--T:60--> | ==See also== <!--T:60--> | ||
[[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]]</div></translate> | [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]] – [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]]</div></translate> |
Revision as of 11:28, 13 May 2020
Overview
Once you decided which computers you want to protect in your environment and have installed relevant SEP sesam component(s) on these computers, you can set up your backup environment. Make sure that you have an appropriate permissions (admin) to access the respective systems.
Step 1 – Location
You must first determine which computers you want to back up with SEP sesam and then configure all target computers (clients) in the SEP sesam GUI. Each client must be created within (and assigned to) a location, which can be defined as a group of clients and further specified as sub-locations. Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree-like structure).
You can use locations to group your clients according to their OS, data type, different geographical location, etc. The name of locations can be freely assigned and is used for orientation purposes. By default, the location is set to LOCAL. You can create a new location under Main selection -> Components -> Topology -> New Location. For details, see Configuring Location.
The following screenshot shows the backup environment, which consists of several locations.
Step 2 – Clients
Afterwards, you have to add you clients to your location or sub-location by right-clicking it (e.g., Windows) and selecting New Client. Clients may be workstations, PCs, virtual machines or file servers with gigabytes of data. For details, see Configuring Clients.
For client connection issues, see How to verify that the SEP sesam server has full access to a specific client.
Step 3 – Backup hardware: Where should the data be stored?
During the installation process, SEP sesam checks the SCSI-bus for connected backup hardware and enters its data in the SEP sesam database.
SEP sesam data store is a device type used for writing the savesets directly on one or several configured storage locations – into the file system. SEP sesam uses a data store instead of a conventional media pool to define storage repository. The data is still primarily backed up to a media pool, however, a data store is used underneath to save data to dynamically managed data areas, including disk backups.
SEP sesam can contain multiple data stores of different types (e.g., Path, SEP Si3 deduplication store, etc.) and sizes based on the type of data being backed up, backup technique, and on your storage location (a local disk, virtualized storage device, storage appliances, etc.).
You can configure your data stores under Main Selection -> Components -> Data Stores -> New Data Store. For details, see Configuring a Data Store.
Step 4 – Tasks: What should be backed up?
A backup task defines which savesets are backed up and which data should be excluded from backup. To create a backup task, in the Main Selection -> Tasks -> By Clients, right-click the client and select New Backup Task. In case of the Windows clients, you have to make sure that the option VSS is enabled during the backup task creation. For more information, see Creating a Backup Task.
Additionally, you can assign individual backup tasks to a task group and then trigger the start of all tasks belonging to that group with a single event. It is recommended that you create a task group for each task type, for example, VMs, application, etc. You can group the backup tasks under Main Selection -> Tasks -> By Groups -> New Task Group. For details, see Adding a Task to the Task Group.
If you want to start the backup task or task group immediately, right-click the task/task group and click Immediate Start, see Immediate Start: Backup. Otherwise you have to schedule your backup task/task group.
Step 5 – Schedules: When should the data be backed up?
If you want to create a periodic backup, you have to schedule your backup task(s). 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 only once. You can create a new schedule under Main Selection -> Scheduling -> Schedules -> New Schedule. For more details, see Creating a Schedule.
The following schedules are recommended:
- One schedule (Diff, Mo.-Fr.) for all data (regardless of the operating system), starting at 8:00 pm
- One schedule (Full, weekly) for all data (regardless of the operating system), starting at 10:00 am
- One schedule (Full, daily) for the system, starting at 9:00 pm
- One schedule (Full, daily) for the SEP sesam self backup, starting at 07:00 am
- One schedule (Full, daily) for all databases, starting at 10:00 pm
- One schedule (Full, daily) for all virtual machines, starting at 11:00 pm
For a one-time execution of the schedule, right-click on the schedule and select Immediate Start. Otherwise you have to link a backup event to it.
Step 6 – Backup event: How should the backup start?
After you have created a schedule, you have to link a backup event to it to configure a periodic backup. In the Main Selection -> Scheduling -> Schedules, right-click the schedule and select New Backup Event.
You have to create a new backup event for each schedule and insert it into the SEP sesam calendar, which will then be executed by the SEPuler at the appointed time. For details on how to create a backup event, see Creating a Backup Event.
The system is now completely configured and will execute the new backup jobs at the appointed time. After the backup has been executed, you can check your backup jobs from the Main Selection -> Scheduling -> Calendar Sheet or Main Selection -> Job State -> Backups.
Note | |
As of 4.4.3 Beefalo V2, you can check the details of your backups online by using new Web UI. For details, see SEP sesam Web UI. |