Server Management: Linux Backups


Published on

Linux server backup tips and strategy for managing backups. High level overview of how to think about backing up your servers and how rackAID has used R1Soft's CDP server to meet our client's data protection needs.

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Server Management: Linux Backups

  1. 1. Linux Server Management Best Practices:<br />Backup & Recovery Solutions<br />Jeff Huckaby<br />rackAID<br /><br />
  2. 2. rackAID: Quick Facts<br />300+ management clients <br />200 servers in backup farms<br />Backup operations in 4 cities<br />Started with R1Soft in 2007<br />>90% of clients use backups<br />
  3. 3. Backup & Recovery Practices<br />Understanding Data Loss<br />Setting Disaster Recovery Goals<br />Backup & Recovery Questions<br />rackAID & R1Soft<br />Tips, Tricks and Traps<br />Questions?<br />
  4. 4. Understanding Data Loss<br />
  5. 5. Is this You?<br />
  6. 6. Set Your Disaster Recovery Goals<br />Business needs drive your goals:<br />What can you afford to lose?<br />How long can you be down?<br />What is the cost of downtime?<br />Some Goals:<br />Fully restore a failed server in 24 hours.<br />Replace accidently deleted files in 30 minutes.<br />Restored hacked web site files in 1 hour.<br />
  7. 7. Backups are Easy Recovery Is Hard<br />#FAIL<br />
  8. 8. Backups & Recovery Questions<br />Backup Questions<br />What to backup?<br />When to backup? <br />Where to backup?<br />How often to backup?<br />How long to keep?<br />Legal requirements?<br />Recovery Questions<br />Do I have the assets?<br />Do I have the time? <br />Do I have the staff?<br />How do I test?<br />Remote tools?<br />How often to review?<br />
  9. 9. rackAID’s Goals: Enter R1Soft<br />By Setting Goals You Set Expectations<br />Be able to recover failed server in under 24 hours.<br />Be able to recover files quickly (< 30 mins) and easily.<br />Centralized management and reporting.<br />Scalable solution – add storage or servers as needed<br />Extensible solutions – integrate into existing operations via API.<br />Commodity hardware – no special hardware to buy.<br />Clear flexible licensing – fits our MSP business model.<br />Good error reporting – make it easy for us to spot issues.<br />Pure Linux environment – must be Linux.<br />
  10. 10. rackAID’s R1Soft Deployment<br />Locations: Dallas, DC, Seattle, NYC<br />Disks: >4 SATA Disks in RAID 5 or 10<br />CPU: Dual Core or Better<br />RAM: 4GB or more<br />Network: GigE Throughout<br />
  11. 11. Backup Management Tools<br />Cacti<br />Nagios<br />Splunk><br />Kayako Help Desk<br />
  12. 12. Data and Server Recovery<br />Data Restores<br />Conflicting processes<br />Watch network loads<br />Watch disk capacity<br />Bare Metal Restores<br />KVM over IP<br />Rescue console<br />Kernel Rebuilds<br />
  13. 13. Backup and Recovery Pitfalls<br />Corrupt File Systems<br />System may not boot<br />Too many files<br />Slow restores<br />Too slow a network<br />10Mbits = ~4 GB/hr<br />Too small a disk<br />No bare metal restore<br />Isolated backups<br />Delays recovery<br />
  14. 14. Backup and Recovery Tips<br />Check file systems as needed.<br />Don’t backup what you don’t need.<br />Keep tabs on backup server capacity<br />Test, test and test again.<br />Backup errors signal hardware issues.<br />Disk safe verifications are important.<br />Maintain written recovery procedures.<br />
  15. 15. Questions?<br />Contact Me:<br />Jeff Huckaby<br /><br />rackAID Services<br /><br /><br />