1 / 0

South Florida SharePoint Users Group

South Florida SharePoint Users Group. Introduction. Chuck Hughes – Admin/Arch. Senior Consultant: SharePoint Architect - Auxis SharePoint Training Instructor - PC Professor Been working with SharePoint since SharePoint Team Services. Stacy Draper – Development.

sancho
Download Presentation

South Florida SharePoint Users Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. South Florida SharePoint Users Group

    Introduction
  2. Chuck Hughes – Admin/Arch. Senior Consultant: SharePoint Architect - Auxis SharePoint Training Instructor - PC Professor Been working with SharePoint since SharePoint Team Services
  3. Stacy Draper – Development Owner, Master Developer – Wild Wires LLC
  4. The Users We want to know about you and what your current SharePoint experience is, as well as what you want to get out of these Group Meetings? Next slide is the Agenda…

  5. South Florida SharePoint Users Group

    Agenda
  6. Agenda 6:10-6:20 – Mission Statement The South Florida SharePoint User Group purpose is to provide its members and the public with opportunities for information sharing and collaboration to enhance the communities’ knowledge of SharePoint. Introductions
  7. Agenda 6:20-6:30 – Upcoming 5 meetings Dates December 4th January 8th February 5th March 5th April 2nd Topics (suggestions) Infrastructure + Business Productivity Online Services Governance & Planning Security Modeling Taxonomy Branding + Customization
  8. Agenda Vendors & Tools Demos(Prospective) Based on Users feedback Security Workflows Web parts Speakers Chuck Hughes Stacy Draper SharePoint SME Speakers (Future)
  9. Agenda Meeting Format 2 Speakers/ 1 Topic (Subject to change) (30 -40 min) SUG Owned (Format Can Change) (Topic can be driven by you!) Communication Website LinkedIn E-Mail Mailer
  10. Agenda 6:40-7:20 – Business Continuity Plan What is BCP? Planning & Best Practices Best methods matrix Preventive Maintenance Planning Testing & Validating 7:20-7:45 – Q & A 7:45 - Audience Feedback 8pm – Network Next slide is the Agenda…

  11. Business Continuity Planning

    Explained!
  12. Single Points of Failure The first line of defense in Business Continuity. Do not! Have all your servers running on the same VM Have all your servers in the same rack/power supply Do! Make sure SQL is Clustered Make sure you have a minimum 2 Front End Web Server So if one thing fails they all fail.
  13. Typical Sever Environments Demo Medium Farm Large Farm Small Farm Next slide is the Purpose…
  14. The purpose of the SharePoint Business Continuity Plan is to ensure that we have a plan to keep business moving if in the event that the SharePoint is unavailable. Purpose
  15. What is the Objectives? Ensure a critical business system is operational Plan of action in case of failure Plan for business continuity server readiness People, equipment, processes, and supplies necessary for recovery of the core business functions. Plan for preventive maintenance & testing Next slide is the Planning…

  16. Senario: Secondary SharePoint instance that is ready to go when needed!

    Planning
  17. Plan of action in case of failure The plan is the sequence of events that happens in case of system failure, showing the steps and personnel that will be used to act on using the continue Business Continuity Plan while main system is evaluated and restored.
  18. Plan for business continuity server readiness If the Company Main Portal service is interrupted this is the timeframe for acting on the Company Main Portal Business Continuity plan. Setting limits  If downtime exceeds: 30 minutes on during business hours between Mon – Fri, 8am till 6pm 1 hour on off-business hours
  19. Plan for Actions Steps Next would be creating the steps to act upon to initiate the Examples: Step 1 – Alert all users via email Step 2 – Take Production Server offline Step 3 – Ensure that BC server is running Step 4 – DNS change Step 5 – Etc….. Then the reverse steps once the production server is back up.
  20. Sample Model A server running MOSS 2007 and SQL server that can run as our internal Business Continuity Server. The server needs to have the same or identical hardware specifications to support this method which can all reside on the same server. Production Portal is backed up (Nightly) Backup is restored to Business Continuity Server (Weekly)
  21. Server Plan
  22. Other Model Options Mirrored System Pros – 100% availability Cons - Very Complex, Hard to maintain Microsoft System Center Data Protection Manager 2007 Pros - Recover files in minutes instead of hours, Use advanced functionality at low cost Cons - Complex Next slide is the Resources…

  23. This area is for the hardware and software requirement information that is needed.

    Resources
  24. Business continuity team members and responsibilities. Strategic Election of members for a Continuity Team board. The members of this team sit as an oversight board to ensure the Business Continuity Plan is being implemented and governed. Operational Support staff necessary for recovery of the core business functions. The Members of this team are the required support staff to carry out the plan Next slide is the Preventive Maintenance & Testing…

  25. To ensure that this plan is used in a worst case scenario, we have to ensure that the servers are well maintained and tested periodically.

    Preventive Maintenance & Testing
  26. Preventive Maintenance Server Updates - needs to be checked monthly Application Service Packs – needs to be done after the release has been acknowledged and a troubleshooting and back out plans have been established. Application Hot fixes – Case by case basis depending on the severity.
  27. Testing All too often no one tests their plans for restoring the system, then come too find it does not work. The Business Continuity Plan: should be tested no less than monthly to ensure smooth transition. SharePoint Admin Backup & Restore should be done monthly to ensure the backup finishes & to test process Next slide is the Q & A…

  28. Q & A

More Related