2. 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
> 3500 Customers in > 45 countries
Hoppenstedt Top Financial Rating
– only 3,3% of all German companies got a a No. 1 rating.
3. The History
Define Linux
established, Strategy
Systemintegration Spin off logistic SW - International expansion
HW development SEP Logistik AG 2008
Development of Establish
Development SEP AG
logistics SW sesam2000
Backup for
NT/Unix/Linux
Develop Backup and data protection
Software – VMS (92)
SEP sesam 2000
Software only
Dataprotection and
logistics
patented
processes
Logisticsoftware
Relag
1980 1990 2000 2008
4. SEP sesam Backup for all
Update / Training / Support
Applications backup
Bare Machine
Virtualisation
Recovery
Database – hot backup extensions
OS/2 Free VMS
BSD
Operating System / Filesystem
5. Backup - fundamentals
Datab Data /
ase File
System
Systemstate
Registry
Critical
HAL(Hardware
Abstraction Layer)
Partition
information
Bootloader
...
5
6. Restore – fundamentals :-)
Datab Data /
ase File
Systemstate
Registry
HAL(Hardware
System
Abstraction Layer)
Critical
Partition
information
Bootloader
...
All Backup is only done for the ability to proceed a fast and consistent restore!!
6
7. Backup in a Virtual
Environment
Datab Data /
ase File
System
Critical
Hypervisor
7
8. Backup in a virtual
environment – with API
Hot Backup via Backup Agent
Binari
Datab
es /
ase
File
Guest1 ... GuestN
Backup API
Hypervisor (Citrix Xen, VMware, Hyper V)
Snapshot via Backup API
8
9. Backup - Strategies
in Virtual Environments
• Differentiate
– dynamic Data – like Database and Files
– unchanged files – like Application binaries
– Systeminformation
• Don't forget the Host itself
9
10. Backup - Strategies
in Virtual Environments
Snapshot backup
•
Image copy of the whole virtual Disk
– open Database --> corrupt
– open Files → ??
– restore only of the whole image – single file restore not possible
•
Applicable for System backup
•
Applicable for fixed data like
– Infrastructure and Application server
– DHCP, DNS, Print – but not always for a file server!!
11. Backup - Strategies
in Virtual Environments
Snapshot backup - the next
•
Recommendation
– Define a dedicated virtual disk for each snapshot area
==> 2 LVM partitions per guest
• System and Data
•
Differentiate
VMware, Citrix XenServer, HyperV and the rest
provides VCB / VADP Interface Snapshot stops the guest
provides VSS Interface provides Citrix XenServer API
12. Different Hypervisors
• VMware Citrix XenServer
– VCB (old) / VADP Interface – Backup API available
– Vcenter always required
Windows Guest Backup via VSS
→ Consistent VSS Backup of MS SQL /
– Uniterrupted Snapshot possible
MS Exchange
Consistence of system information and data → Restore the complete Snapshot – no
Incremental backup, single file restore single DB or Mail
Windows Guest Backup via integrated VSS – Uniterrupted Snapshot possible - only
→ Consistent VSS Backup of MS SQL / MS Exchange complete Snapshot – no single file restore
→ Restore the complete Snapshot – no single DB or Mail
– No incremental backup
• Hyper V
– Backup API available (VSS) Xen Source / KVM
Uniterrupted Snapshot possible - only complete Snapshot – no – Use a Script to generate a Snapshot via
single file restore; No incremental backup Linux LVM – stops the guest – see SEP
Windows Guest Backup via VSS wiki.
→ Consistent VSS Backup of MS SQL / MS Exchange
→ Restore the complete Snapshot – no single DB or Mail
13. Requirements summary
• Applicable for different Hypervisors
• Backup for all Operatingsystems – virtual and real
• Online Modules for Database Backup
• Don't forget the real world – use the same backup system for
virtual and physical Servers
• ==> SEP
we can !!!
