• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Relax and Recover rear-server Proposal 1.0
 

Relax and Recover rear-server Proposal 1.0

on

  • 3,203 views

Relax and Recover (http://rear.sourceforge.net) is an automated tool for Linux bare-metal disaster recovery. ...

Relax and Recover (http://rear.sourceforge.net) is an automated tool for Linux bare-metal disaster recovery.

This presentation by one of the authors explores ideas about build a centralized managemend server to complement the ReaR software installed on all your Linux servers in your data center.

Statistics

Views

Total Views
3,203
Views on SlideShare
3,201
Embed Views
2

Actions

Likes
0
Downloads
7
Comments
0

2 Embeds 2

http://www.docshut.com 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Relax and Recover rear-server Proposal 1.0 Relax and Recover rear-server Proposal 1.0 Presentation Transcript

    • Relax and Recover Proposal for rear-server1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 1
    • Background ● Proven solution at large enterprise customers ● ReaR established as standard solution for Linux disaster recovery in data centers ● Shipping with Fedora (from 11) and openSUSE ● Integrates with many commercial backup software solutions ● Scales well with large amounts of servers1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 2
    • What is missing? ● Most customers miss a central component for ReaR that ● Gathers information about rear ● Stores rear boot images ● Initiates Disaster Recovery ● Makes rear information available for 3rd party1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 3
    • rear-server version 1 functions ● Information gathering only ● Information pushed to server from rear as part of “rear mkrescue” boot image creation ● Optionally collect also boot images ● Display information about rear-protected systems ● Group information by hosts/domains and tags ● Scalability for thousands of systems ● Simple Web-GUI1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 4
    • implementation requirements ● Use existing network / routing / firewall infrastructure and standard protocols ● No direct connection between rear and rear- server required1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 5
    • rear changes required ● Additional configuration variables ● REAR_SERVER ● REAR_SERVER_SEND_RESULT ● REAR_SERVER_TAGS ● Scriptlets to send the required information to the rear server (similar to existing email support)1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 6
    • rear-server Architecture User access via Browser postfix Apache / PHP @rear-server-domain.com rear-server GUI SMTP virtual alias PHP application“rear mkrescue” rear-server-sink.sh MySQL 1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 7
    • Design Considerations ● SMTP can be routed, is indirect ● Most corporate setups allow sending emails to internal system even for DMZ systems ● Based on standard components (postfix, Apache, PHP, MySQL) ● No “rear daemon” required, use existing daemons of Apache and postfix ● “Free” queuing for incoming requests by postfix ● SMTP can be easily secured1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 8
    • rear-server Web GUI ● Authentication handled by Apache ● Support LDAP, AD, Kerberos etc. ● For version 1 (information gathering) all access has the same security level (in any case only read-only) ● Multiple views: ● Overview ● Last 20 (with auto refresh like “tail -f”) ● Grouped/Filtered by client domain ● Grouped/Filtered by tags ● Search1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 9
    • Delivery ● GPL Software ● Central configuration directory: ● /etc/rear-server ● As RPM that installs rear-server and configures ● postfix ● Apache ● MySQL ● Optionally vendor-based configuration tool ● yast rear-server ● system-config-rear1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 10
    • Roadmap ● 1.0 ● Basic functionality as described in this proposal ● Depending on implementation issues without some advanced parts ● 1.2 ● Implement missing parts, optimize design ● Implement features from customer installations ● Optionally integrate with monitoring solutions (e.g. Nagios) ● 2.0 ● Trigger Disaster Recovery from Web GUI ● Depends on integration with backup software ● 3.0 ● Integrate with system management solutions1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 11
    • Contact Schlomo Schapiro ReaR Maintainer schlomo@schapiro.org +49 170 7537601.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 12