JcGaming

F_ias

Dec 10th, 2024
69
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.23 KB | None | 0 0
  1. Presentation Script: Disaster Recovery Plan for Local Area Network (LAN) System at PTC Organization
  2. Slide 1: Title Slide
  3. Speaker Notes:
  4. Good [morning/afternoon], everyone. Today, I will be presenting the Disaster Recovery Plan for the Local Area Network, or LAN, system at PTC Organization. This plan is crucial in ensuring that our critical IT infrastructure and business operations can recover quickly and efficiently in the event of any disaster.
  5.  
  6. Slide 2: Overview
  7. Speaker Notes:
  8. Our LAN infrastructure is the backbone of essential business processes at PTC. It supports file sharing, database management, domain services, and intranet applications. The primary goal of this Disaster Recovery Plan, or DRP, is to minimize downtime and data loss during disasters. To achieve this, we leverage robust backup systems, failover solutions, and a designated hot site.
  9.  
  10. This plan is tailored to our infrastructure's specific needs, ensuring continuity and resilience.
  11.  
  12. Slide 3: Primary and Hot Site Servers
  13. Speaker Notes:
  14. Let’s take a closer look at our servers:
  15.  
  16. Primary Server: Located at our College Street office in Pateros, Metro Manila.
  17.  
  18. Model: HPE ProLiant ML350 Gen10
  19. Operating System: Microsoft Windows Server 2022
  20. Key Specifications:
  21. 2 Intel Xeon Gold CPUs
  22. 256 GB of RAM
  23. 8 TB of RAID 10 storage
  24. Redundant power supplies and NICs ensure hardware resilience.
  25. Hot Site Server: This is located at the San Pedro Campus in Pateros and acts as our failover server.
  26.  
  27. Model: HP ProLiant DL380 Gen10
  28. Operating System: Windows Server 2019
  29. Specifications include 128 GB RAM and 3 TB of RAID 5 storage.
  30. It supports essential backup services, such as file sharing, database replication, and intranet hosting.
  31. Having this redundancy enables us to quickly restore services even during severe outages.
  32.  
  33. Slide 4: Applications
  34. Speaker Notes:
  35. Our LAN system hosts several critical applications:
  36.  
  37. Primary Site Applications:
  38.  
  39. File Sharing Services
  40. Database Management using SQL Server
  41. Active Directory for domain services
  42. Intranet Hosting
  43. Hot Site Applications:
  44.  
  45. File Sharing Services
  46. Backup SQL Server database
  47. Backup Intranet Hosting
  48. By having mirrored functionality at the hot site, we ensure business continuity in case of disasters.
  49.  
  50. Slide 5: Backup Strategy
  51. Speaker Notes:
  52. Regular backups are essential for effective disaster recovery. Here’s our backup strategy:
  53.  
  54. Daily Backups: Performed at 3:00 AM every day.
  55. Monthly Backups: Scheduled for the first Saturday of each month.
  56. Quarterly Backups: Conducted on the first Sunday of every quarter.
  57. These backups are stored securely offsite and are regularly tested to ensure data integrity and reliability.
  58.  
  59. Slide 6: Disaster Recovery Procedures
  60. Speaker Notes:
  61. Our recovery procedures are designed to address specific scenarios. Let’s explore two critical scenarios:
  62.  
  63. Total Loss of Data:
  64.  
  65. Notify the IT Manager and stakeholders.
  66. Access offsite backups to restore critical files and applications.
  67. Conduct verification tests to ensure the integrity of restored data.
  68. Total Loss of Hardware:
  69.  
  70. Replace failed hardware with equivalent or upgraded equipment.
  71. Reconfigure the system and restore data from backups.
  72. Test all restored services to ensure they function correctly.
  73. These steps ensure that we can resume operations as quickly as possible.
  74.  
  75. Slide 7: Risk Management
  76. Speaker Notes:
  77. Effective disaster recovery requires understanding potential risks. Here are some examples:
  78.  
  79. Server Room Fire:
  80.  
  81. Probability: Low; Impact: High
  82. Consequences: Total hardware and data loss
  83. Mitigation: Install fire suppression systems and maintain offsite backups.
  84. Cyberattacks (Ransomware):
  85.  
  86. Probability: Medium; Impact: Medium
  87. Consequences: Service disruption and data theft
  88. Mitigation: Conduct security audits and use updated antivirus software.
  89. Power Outages:
  90.  
  91. Probability: High; Impact: Medium
  92. Mitigation: Use UPS systems and backup generators to maintain uptime.
  93. By evaluating risks and implementing mitigation strategies, we can better prepare for potential disasters.
  94.  
  95. Slide 8: Emergency Contacts
  96. Speaker Notes:
  97. Having an efficient communication structure during disasters is crucial. Here are the key contacts:
  98.  
  99. System Owner: Reagan Ricafort – 09583468120
  100. Database Owner: Irene Green – 09567122951
  101. Application Owner: Bryony Castillo – 09345688139
  102. Offsite Storage Contact: Omar Holt – 09984568124
  103. These individuals are trained and ready to respond to incidents, ensuring that recovery efforts are coordinated and efficient.
  104.  
  105. Slide 9: Recovery Timeline
  106. Speaker Notes:
  107. Time is critical in disaster recovery. Our recovery timeline includes:
  108.  
  109. Emergency-Level Service: Within 2 business hours.
  110. Key Services Restored: Within 4 business hours.
  111. Full Recovery: Within 8 to 24 hours.
  112. This timeline ensures that we prioritize critical services while restoring full operations within a day.
  113.  
  114. Slide 10: Conclusion
  115. Speaker Notes:
  116. In conclusion, our LAN Disaster Recovery Plan is designed to provide a structured, efficient response to any incident that threatens our IT systems. By leveraging robust infrastructure, comprehensive backups, and a dedicated hot site, we aim to ensure continuity and resilience for PTC’s critical business operations.
  117.  
  118. Thank you for your attention. I’m happy to take any questions.
Advertisement
Add Comment
Please, Sign In to add comment