Your SlideShare is downloading. ×
0
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Enterprise Support Seminar – June 2005
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Enterprise Support Seminar – June 2005

252

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
252
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Disaster Recovery Steve Menzies
  • 2. Disaster? <ul><li>“ an event which occurs on your network which makes normal day-to-day business functions impossible AND can or will result in data loss “ </li></ul>Microsoft White Paper on Disaster Recovery, November 2004
  • 3. Agenda <ul><li>Causes of a Disaster </li></ul><ul><li>Best Practice </li></ul><ul><ul><li>Overview of previous seminars </li></ul></ul><ul><li>Providing Fault Tolerance </li></ul><ul><ul><li>For Smart-Tools 3 environment </li></ul></ul><ul><li>Backup Provision </li></ul><ul><ul><li>Existing and new solutions </li></ul></ul><ul><li>Summary </li></ul>
  • 4. Causes of a Disaster <ul><li>Inadequate security </li></ul><ul><ul><li>Physical barriers (doors &amp; locks), Authorisation </li></ul></ul><ul><li>Ageing Hardware/Software </li></ul><ul><ul><li>Older equipment more liable to fail, software can become unstable </li></ul></ul><ul><li>Software Updates </li></ul><ul><ul><li>Installing incorrect updates/missing updates </li></ul></ul><ul><li>Physical Considerations </li></ul><ul><ul><li>Air quality, temperature, location </li></ul></ul><ul><li>Human intervention </li></ul><ul><ul><li>Accidental and deliberate, username/password misuse </li></ul></ul><ul><li>Not resolving small insignificant issues </li></ul><ul><ul><li>Fan failures, hard-drive bad blocks, etc </li></ul></ul>
  • 5. Best Practice <ul><li>Points to remember from previous seminars: </li></ul><ul><li>General Network Use </li></ul><ul><li>Server Hardware </li></ul><ul><li>Server Software </li></ul><ul><li>Different Backup Solutions </li></ul><ul><li>Regular Scheduled Backups </li></ul><ul><li>System Recovery </li></ul><ul><li>Hardware Recovery </li></ul><ul><li>Anti-virus provision </li></ul><ul><li>Needs to be integrated into overall college disaster recovery plan </li></ul>
  • 6. Providing Fault Tolerance <ul><li>Native Microsoft Tools </li></ul><ul><li>Network Load Balancing (NLB) </li></ul><ul><ul><li>Not suitable for data critical servers </li></ul></ul><ul><ul><li>Improves data throughput rates/spreads load </li></ul></ul><ul><ul><li>Minimal fault tolerance – no data copying or protection </li></ul></ul><ul><ul><li>Suited for web-servers/ISA Server/Terminal Server </li></ul></ul><ul><ul><li>Maximum of 32 servers per cluster </li></ul></ul><ul><li>Microsoft Clustering Service (MSCS) </li></ul><ul><ul><li>Requires specific hardware specifications (MSHCL) </li></ul></ul><ul><ul><li>Requires Windows Server 2003 Enterprise Edition </li></ul></ul><ul><ul><li>Suitable for File/Print/Database/Email Servers </li></ul></ul><ul><ul><li>Maximum of 2 servers/8 servers (Windows 2000/2003) </li></ul></ul>
  • 7. Providing Fault Tolerance <ul><li>Current fault tolerance in Smart-Tools 3 </li></ul><ul><ul><li>Replica Domain Controllers </li></ul></ul><ul><ul><li>DNS </li></ul></ul><ul><ul><li>DHCP </li></ul></ul><ul><ul><li>drive mappings for RM shares </li></ul></ul><ul><ul><li>cached local log-ons </li></ul></ul><ul><li>As part of your overall fault tolerance provision for Smart-Tools 3 </li></ul><ul><li>DoubleTake </li></ul><ul><ul><li>multiple operating system compatibility </li></ul></ul><ul><ul><li>provides real-time (and open file) data replication </li></ul></ul><ul><ul><li>replicates from a source server to a target server </li></ul></ul><ul><ul><li>block level file replication (saves bandwidth), only changes are copied </li></ul></ul><ul><ul><li>can provide failover for multiple servers </li></ul></ul><ul><ul><li>can be additionally configured using scripting (manual or automatic) </li></ul></ul><ul><ul><li>augments your existing Backup Strategy </li></ul></ul>
  • 8. DoubleTake User Home Directories
  • 9. DoubleTake <ul><li>Demonstration </li></ul><ul><li>Smart-Tools 3 Domain Controller failure </li></ul>Smart-Tools 3 &amp; DoubleTake on Microsoft Virtual Server 2005
  • 10. Providing Fault Tolerance Double Take Native ST3/ Windows Support Service Not required as other DCs can provide roles. FSMO roles should remain on failed server   Domain Controller Roles Can be failed over to Double Take   RM Multimedia RMMC can be accessed on other RM DC   RM Man. Cons. Auditor Database will be unavailable until the Server is recovered   RM Auditor Printer Database will be unavailable until the Server is recovered. Printing will still be available   Printer Credits Certain LRs can be failed over to Double Take   Learning Resources If DC has failed then the UHD will not be accessible until recovered   User Home Directories DNS Queries can be handled by other DCs   DNS DHCP can be load balanced using Standard MS Tools. Can be failed onto DoubleTake Server   DHCP
  • 11. Providing Fault Tolerance <ul><li>DoubleTake Benefits </li></ul><ul><li>Cost </li></ul><ul><ul><li>No Specific Hardware or Software requirements </li></ul></ul><ul><li>Simplicity </li></ul><ul><ul><li>Can be managed from a management console interface </li></ul></ul><ul><li>Scalability </li></ul><ul><ul><li>One DoubleTake Server can provide fault tolerance for multiple servers performing different roles. Server can be added at any time without effecting others </li></ul></ul><ul><ul><li>Can be used to provide tolerance for other mission critical member servers in a Smart-Tools 3 Environment (SQL, IIS) </li></ul></ul><ul><ul><li>DoubleTake does not replace a whole server in the event of a failure but rather provides fault tolerance for services that the failed server provides </li></ul></ul>
  • 12. Network Backup &amp; Restore Protection <ul><li>Existing EBS </li></ul><ul><ul><li>Veritas NetBackup 5 </li></ul></ul><ul><ul><li>Veritas Backup Exec 9 </li></ul></ul><ul><li>New EBS </li></ul><ul><ul><li>Veritas Backup Exec 10 </li></ul></ul><ul><li>Backup regime – full/differential/incremental </li></ul><ul><li>Centralised/local system </li></ul><ul><li>Shrinking backup window / Increasing data volume </li></ul>
  • 13. Network Backup &amp; Restore Protection <ul><li>Eliminating bottlenecks – Data Throughput </li></ul>* Native uncompressed transfer speeds ~ 7.5 MB/sec 100 Mbps Network ~ 1 – 5 MB/sec Typical User File Server ~10 - 15 MB/sec Typical Database Server ~ 75 MB/sec 1 Gbps Network 36 MB/sec* SDLT600 Tapes 16 MB/sec* SDLT320 Tapes 12 MB/sec* AIT3 Tapes
  • 14. Network Backup &amp; Restore Protection <ul><li>Reducing backup time </li></ul><ul><li>Tape technology is fast, and getting faster S4-DLT and LTO3 likely to be around 130MB/sec </li></ul><ul><li>File systems are inherently slow to backup </li></ul><ul><li>Can backup multiple systems concurrently over 1 Gbps network </li></ul><ul><li>Backup straight to tape (multiplex) </li></ul><ul><ul><li>Veritas NetBackup </li></ul></ul><ul><li>Backup to intermediary disk stage </li></ul><ul><ul><li>Veritas Backup Exec 10 or Veritas NetBackup </li></ul></ul>
  • 15. Veritas Backup Exec 10 <ul><li>What’s New? </li></ul><ul><li>Disk Staging </li></ul><ul><li>Policy Based Jobs </li></ul><ul><li>Increased Report Functionality </li></ul><ul><li>Cluster Support </li></ul><ul><li>Fault Tolerant </li></ul><ul><li>Advanced Disk-based Backup Option </li></ul>
  • 16. Veritas Backup Exec 10 <ul><li>Disk Staging Demonstration </li></ul><ul><li>Using Microsoft Virtual Server 2005 </li></ul>
  • 17. Backup Provision    Disk Staging    Enhanced Security Protection         Backup Exec 9.x   MS Virtual Server Compatible   Multiplexing NetBackup 5 Backup Exec 10 EBS Feature   Advanced Disk-based Backup   Standard Components   Enhanced Fault Tolerance   Cluster Support   Enhanced Report Functionality   Policy Based Jobs
  • 18. Disaster Recovery <ul><li>Testing Disaster Recovery </li></ul><ul><li>Equipment </li></ul><ul><ul><li>Live server on the network </li></ul></ul><ul><ul><li>Test server in test network </li></ul></ul><ul><ul><li>Virtual server in virtual network </li></ul></ul>
  • 19. Disaster Recovery <ul><li>Microsoft Virtual Server 2005 benefits </li></ul><ul><ul><li>Provides a test network for disaster recovery testing, software updates, application testing </li></ul></ul><ul><ul><li>Can be used to replace physical server in the event of disaster </li></ul></ul><ul><ul><li>Can consolidate multiple servers on one physical “box” </li></ul></ul>
  • 20. Disaster Recovery <ul><li>Summary </li></ul><ul><li>Protect against disaster </li></ul><ul><li>Disaster recovery strategy </li></ul><ul><ul><li>part of overall college disaster recovery strategy </li></ul></ul><ul><ul><li>plan must be dynamic </li></ul></ul><ul><ul><li>under constant review </li></ul></ul><ul><ul><li>able to change to meet new threats </li></ul></ul><ul><li>Providing fault tolerance </li></ul><ul><ul><li>- data protection/failover </li></ul></ul>
  • 21. Disaster Recovery <ul><li>Recovering from disaster </li></ul><ul><li>Backup and restore strategy must be tried and tested </li></ul><ul><ul><li>When? </li></ul></ul><ul><ul><ul><li>End of term/start of term </li></ul></ul></ul><ul><ul><ul><li>Before/after Significant Network Changes </li></ul></ul></ul><ul><ul><ul><li>“ Quiet” times </li></ul></ul></ul><ul><ul><li>With what? </li></ul></ul><ul><ul><ul><li>Live server equipment – greater risk </li></ul></ul></ul><ul><ul><ul><li>Test server equipment – greater expense </li></ul></ul></ul><ul><ul><ul><li>Virtual server (Microsoft Virtual Server 2005) </li></ul></ul></ul>
  • 22. Disaster Recovery <ul><li>Learn from past experiences </li></ul><ul><li>Seen before somewhere else </li></ul><ul><li>Learn from others </li></ul><ul><li>No need to reinvent the wheel </li></ul><ul><li>“ Every minute saved before the disaster is one that will not be wasted after” </li></ul>

×