(C)SEP AG

Copyright 1999-2011 by SEP AG. 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.


Contents

Example per small Use Case

Operate test scenarios

To operate test scenarios in many cases you have to clear the SEP sesam environment after the test and re-run scripts. The following sequence offers you a workaround to do that.

  1. Right after a new installation of a SEP sesam Server has finished export the database
    sm_db export -f <smdb_file>
    Example: sm_db export -f /srv/sesamdb_myserver.sql
  2. If you like to recreate your work from the Sesam base configuration do the following:
    1. Clear the Sesam-DB by recreating the database
      sm_db import -f /opt/sesam/skel/db/<dbtype>/sesam_db.sql
      <dbtype> means the type of database your SEP sesam is using (sqlite for SQlite or pg for PostgreSQL).
    2. Import the <smdb_file> to get the basic status after installation of the SEP sesam Server
      sm_db import -f <smdb_file>
      Example: sm_db import -f /srv/sesamdb_myserver.sql
    3. Run your SEP sesam CLI script again

New SEP sesam Environment (backup environment example)

This chapter describes the requirements to create a new SEP sesam environment as showcase.

Network overview


Description

The new SEP sesam environment should accomplish the following requirements.

  • Remove the SEP sesam install defaults.
  • Register a Linux and a Windows backup client
  • On SEP sesam Server smsmrv should work a disk store with 2 mediapools for backup to disk.
  • The backup client xubl01 should act as SEP sesam Remote Device Server (RDS) with a mediapool for backup to disk.
  • Create the necessary jobs for restore of the SEP sesam Server and the Windows client.
  • Backup the Linux server configurations (/etc directory).
  • Combine different backup tasks into taskgroups.
  • Backup strategy
    • Linux server systems and configs from Monday to Friday as full backup.
    • The Windows server as full backup every weekend.
    • The Windows server files backup incremental from Monday to Friday.
    • On the last day of every month backup the Linux server systems to the RDS disk.
    • Migration the disk backups to a different mediapool ...
      • ... from Tuesday to Friday migrate all backups from mediapool vda to vdb from yesterday to today.
      • ... on Monday migrate all backups from mediapool vda to vdb from 3 days before up to today.
  • Start two command events
    • The 1st generate a list of the used media for backup and migration
    • The 2nd is for Notebook backup. It checks if the Notebook is connected into the network. If yes, then the backup will be started.
  • Change the sm_newday event from running at 08:00 a.m. every day to running at 06:00 p.m. from Monday to Friday.
  • Activate the SEP sesam Server notify, alarm and disaster interfaces by copying them from the templates to ./bin/sesam directory
  • Create an email account sesam for sending standard emails raised by the interface file events.
  • Create a SEP sesam metadata backup twice a day.
  • Provoke some test backups.
  • At the end execute a SEP sesam metadata backup. After that you can check if an email has been sent.

Script file

The following configuration can be executed line by line. All lines beginning with a hash sign are comments. Either you copy sm_cmd... commands line by line to a console of the SEP sesam Server and execute it or you can copy them to a script file to run it in one step and automatically (e.g. Create_Sesam_Env.sh below).

Request Call

Our sales team would be happy to assist you!

Download

SEP 30-day Trial

You must login or use current login to download the FREE trial.

Media Library

Browse and discover videos by SEP.