Partner Session SEP

1. • Textmasterformate durch Klicken
bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Requirements to backup solutions
in modern IT environments
Hubert Schweinesbein
hs@sep.de

2. Agenda

What is a „modern“ IT environment – collect requirements

„Buzz Words“ and more

Compile a SEP sesam infrastructure – example

Backup in virtual and distributed environments

Example – Replication to a private Cloud

3. The Company
German vendor of Backup and Disaster Recovery Software.
Headquarter in Weyarn, near Munich.
German development – german support!
Subsidaries in Germany and USA
World Wide Sales via Partners
4000 Customers in > 50 countries
Hoppenstedt Top Financial Rating
– only 3,3% of all German companies got a a No. 1 rating.

4. 20-years of Backup
Experience
1992:
First Backup
Solution for VMS,
UNIX
1996:
Patented backup
processes
1999:
sesam2000 for
Linux, Unix & Win NT
2004:
sales exclusively
through distribution
partners
2008:
start of
international
business
2012:
Satisfied
customers in
+50 countries

5. SEP sesam Backup for all
Database – hot backup extensions
Operating System / Filesystem
OS/2 VMSFree
BSD
Virtualisation
BareMachine
Recovery
Update/Training/Support
Application backup

6. Actual IT environment?
Your input is needed?

7. Session title
Big Data
Cloud Computing
Cost

8. Actual IT

Different Databases

Huge amount of Data

Virtualization

Databases

„Buzz Words“ and more

VMware

HyperV

MS Exchange

Linux

Open Enterprise Server

Groupwise

Directory Server

9. Backup–What to look for

Does the product fully support my platforms
– Operating systems
– Database

Does the product backup many clients to one drive simultaneously

Can the product automatically create multiple simultaneous backups
from one client?

How will the product help me meet extremely aggressive
requirements?
– LAN free backup
– Remote office backup
– Disk-to-Disk-to-Tape-(2Tape-2Tape-...)
O'REILLY - Backup & Recovery
Inexpensive Backup Solutions for Open Systems
W. Curtis Preston

10. Backup–What to look for

Does the product support virtual infrastructure
– VMware, Citrix Xen, Hyper V
– Red Hat virtualization, KVM, Xen

Does the product have storage management features?
– Could it handle the newest Technology?
– Could it migrate data from “old” to “new” technology?

How easy is the product to administer?

How automated is the product

What does the product cost?
O'REILLY - Backup & Recovery
Inexpensive Backup Solutions for Open Systems
W. Curtis Preston

11. Session title
SEP & Big Data
SMART Architecture
Multiple Stream
Multilocation Backup
Deduplication

12. Session title
SEP & Cloud
It's about Agility - Flexibility
Hybrid Backup
Widest DB & OS support
Dedup & Replication

13. • Textmasterformate durch Klicken
bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
SEP sesam in a virtual world!

14. Backup - fundamentals
System
Datab
ase
Data /
File
Critical

Systemstate

Registry

HAL(Hardware
Abstraction Layer)

Partition
information

Bootloader

...

15. Backup in a Virtual
Environment
System
Datab
ase
Data /
File
Critical
Hypervisor

16. Backup in a virtual
environment – with API
Hypervisor (Citrix Xen, VMware, Hyper V)
Guest1 ... GuestN
BackupAPI
Data
base
Binari
es /
File
Hot Backup via Backup Agent
Snapshot via Backup API

17. • Textmasterformate durch Klicken
bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Backup in distributed environments

18. Distributed backups

Single Data Center – no distributed environment – basic environment
– Backup in the data center – Backup media connected to the sesam Server
– All Servers are backed up to the Backup media connected to the sesam
Server

Single SEP sesam management Server for the complete environment –
with subsidaries
– Backup in subsidaries with sesam Remote Device Server
– Backup media are connected to Remote Servers – not only to the sesam
server itself

SEP sesam Master GUI
Manage different sesam server within one GUI
– Consolidated view on many sesam servers
– Servers itself are independent

19. Backup Scenarios
Single SEP sesam management Server for the complete environment
Backup in subsidaries with sesam Remote Device Server
– Managed from the central backup server
– Keep the backup data local – local backup devices
– Logfiles / Management information stored central
Flow of Backup /
Restore Data
Flow of Control /
Log Data
SEP Remote
Device Server
Additional Servrer
to backup - SEP Clients
Server 1
Server 2
Server 3

20. Backup Scenarios
SEP sesam Master GUI - Consolidated view on many sesam servers
– Environments with more sesam servers
– Logfiles / Management information stored on each server
– Master GUI provides a single GUI to manage all independent sesam servers
– No information in the GUI
SEP Remote
Device Server
Backup Client
Backup Client
SEP Master GUI
Backup Client
Backup Client

21. Three Backup
Servers
managed within
one
SEP sesam GUI
→ so called
Master GUI
SEP sesam Master GUI

22. Two Backup Servers
managed within one
SEP sesam GUI
→ so called Master GUI
Systems connected to the
relevant backup servers, the
backup server are
independent. Only a joint
view to the Database on
each server, consolidated in
the GUI.
SEP sesam Master GUI

23. Column shows the backup
server where the job belongs
to. All Servers are displayed in
the same view
SEP sesam Master GUI
status window
All Backup Servers displayed in
„this Master GUI view“

25. Session title
Red Hat Storage & SEP Sesam

26. Backup is not important
All backup is done to ensure a fast and
reliable restore!
The restore and disaster recovery
requirements define the backup strategy
– not the other way around!