Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Relax and Recover                 Proposal for rear-server1.0 | 2009-06-21 | Schlomo Schapiro   Relax and Recover | Propos...
Background ●   Proven solution at large enterprise customers ●   ReaR established as standard solution for     Linux disas...
What is missing? ●   Most customers miss a central component for     ReaR that       ●   Gathers information about rear   ...
rear-server version 1 functions ●   Information gathering only ●   Information pushed to server from rear as part of     “...
implementation requirements ●   Use existing network / routing / firewall     infrastructure and standard protocols ●   No...
rear changes required ●   Additional configuration variables       ●   REAR_SERVER       ●   REAR_SERVER_SEND_RESULT      ...
rear-server Architecture                                                                                         User acce...
Design Considerations ●   SMTP can be routed, is indirect ●   Most corporate setups allow sending emails to     internal s...
rear-server Web GUI ●   Authentication handled by Apache      ●   Support LDAP, AD, Kerberos etc.      ●   For version 1 (...
Delivery ●   GPL Software ●   Central configuration directory:      ●   /etc/rear-server ●   As RPM that installs rear-ser...
Roadmap ●   1.0     ●   Basic functionality as described in this proposal     ●   Depending on implementation issues witho...
Contact                                           Schlomo Schapiro                                           ReaR Maintain...
Upcoming SlideShare
Loading in …5
×

Relax and Recover rear-server Proposal 1.0

4,204 views

Published on

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Relax and Recover rear-server Proposal 1.0

  1. 1. Relax and Recover Proposal for rear-server1.0 | 2009-06-21 | Schlomo Schapiro Relax and Recover | Proposal for rear-server 1
  2. 2. 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
  3. 3. 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
  4. 4. 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
  5. 5. 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
  6. 6. 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
  7. 7. 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
  8. 8. 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
  9. 9. 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
  10. 10. 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
  11. 11. 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
  12. 12. 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

×