Jboye slides-27-02-2013

•

0 likes•429 views

High availability is ultimately measured by the end user experience and minimizing downtime. The goal is to balance business needs with technical capabilities and costs. A system is considered highly available if it meets the agreed upon availability percentage. SharePoint 2013 requires all servers in a farm to be located in the same data center, so redundancy between data centers is not supported. Load balancing multiple web frontends across servers improves availability.

High availability med SharePoint
2013 hos Saxobank
Hvilke karv og overvejelser har vi gjort os indtil i dag

IT er generelt nød til at lytte til forretningens krav.

GOVERNANCE

Fysisk arkitektur
Logisk arkitektur
Farm

Zone Web App Service App

Content DB

Service Site collection

Site

List / Library

[Foldere]

Item / Dokument

Designe udvikle

2 uger

Definere
Deploy

rettelser
vedligehold

måling

For a given software application or service, high availability is ultimately measured in terms of the end user’s experience and expectations. The tangible and perceived business
impact of downtime may be expressed in terms of information loss, property damage, decreased productivity, opportunity costs, contractual damages, or the loss of goodwill.

The principal goal of a high availability solution is to minimize or mitigate the impact of downtime. A sound strategy for this optimally balances business processes and Service
Level Agreements (SLAs) with technical capabilities and infrastructure costs.

A platform is considered highly available per the agreement and expectations of customers and stakeholders. The availability of a system can be expressed as this calculation:

Actual uptime/Expected uptime X 100%

The resulting value is often expressed by industry in terms of the number of 9’s that the solution provides; meant to convey an annual number of minutes of possible uptime,
or conversely, minutes of downtime.

Number of 9's Availability Percentage Total Annual Downtime
2 99% 3 days, 15 hours
3 99.9% 8 hours, 45 minutes
4 99.99% 52 minutes, 34 seconds
5 99.999% 5 minutes, 15 seconds

http://technet.microsoft.com/en-us/library/jj715263.aspx

Load balance

Web frontend Web frontend

Site Site

Central admin Central admin

Load balance

Web frontend Web frontend Web frontend Web frontend

Site Site Site Site

Central admin Central admin

http://technet.microsoft.com/en-us/library/cc262485.aspx

All servers that belong to a server farm,
including database servers, must physically
reside in the same datacenter. Redundancy
and failover between closely located data
centers that are configured as a single farm
("stretched farm”) is not supported in
SharePoint 2013.

http://technet.microsoft.com/en-us/library/cc262485.aspx

http://www.pa.com.au/promo/sharepoint-
2013/highavailability/ http://www.slideshare.net/michaeltnoel/sql-2012-
alwayson-availability-groups-for-sharepoint-2013-
sharepoint-connections-amsterdam-2012

http://technet.microsoft.com/en-
us/library/jj715263.aspx

http://blog.appliedis.com/2012/12/12/sharepoint-
conference-2012-high-availability-solutions-with-
sharepoint-2013/

Similar to Jboye slides-27-02-2013

Puppet on a string

Alain Geenrits

This document discusses DevOps automation using Puppet Enterprise and VMware solutions. It describes how Puppet Enterprise can be used to automate the provisioning of multi-node applications on VMware vCloud Automation Center. This allows for self-service provisioning and lifecycle management of applications across heterogeneous infrastructure according to policies and approvals. It also enables drift remediation to fix configurations that deviate from the blueprint.

SharePoint Always-On Deployment

Mike Maadarani

The document discusses implementing an always-on deployment for SharePoint. It covers definitions of business continuity, disaster recovery, high availability and recovery objectives. It also summarizes options for architectures using SQL AlwaysOn across multiple data centers for high availability and disaster recovery of SharePoint environments. Key aspects include synchronous or asynchronous data replication, testing plans and establishing service level agreements.

Enterprise Risk Management Software

Mike Taylor

Metrics that Matter-Approaches To Managing High Performing Websites

Ben Rushlo

SPS Reston SharePoint Alwyays On

Mike Maadarani

SafePeak whitepaper for Cloud Apps

Vladi Vexler

Getting SharePoint 2010 Deployment Right

Mike Watson

This document discusses preparing for a SharePoint 2010 deployment. It recommends learning as much as possible about SharePoint 2010 through online training and trial versions. The environment should be prepared by setting up an evaluation environment, installing and testing SharePoint 2010 and Office 2010, and practicing upgrades. Hardware requirements have increased, so the environment will need more servers to support high availability, scalability, and performance. Database performance is critical, so SQL Server should be configured for best practices and dedicated storage allocated. New tools like Deployment Advisor can help assess system health and identify issues.

System Center Cloud Services Process Pack Administration Guide

Kathy Vinatieri

The document provides instructions for installing and configuring the System Center Cloud Services Process Pack. It outlines the required prerequisites, including installing System Center 2012 products. It then describes how to install the Cloud Services Process Pack on the Service Manager server and how to install the Cloud Services runbooks on the Orchestrator server. The document provides various configuration and administration tasks that must be completed to fully implement the cloud services solution.

Real User Experience Insight

ruiruitang

The document describes a case study of a virtual retail company using Oracle's Real User Experience Insight (RUEI) product. RUEI helped the company by providing insights into real end-user experiences on their website to proactively find and address issues. This improved customer satisfaction and reduced costs by enabling faster response to problems. RUEI also identified bottlenecks and areas of high user frustration through dashboard reports, allowing the company to improve its online shopping experience and prevent lost revenue.

Real User Experience Insight

ruiruitang

The document describes how a virtual retail company implemented Oracle's Real User Experience Insight (RUEI) solution to address challenges with monitoring end-user experience, performance issue response times, and gaining business and IT insights. RUEI provided proactive monitoring and diagnostics to prevent lost revenue, faster response to customer issues through error replay, easy identification of bottlenecks, and powerful reporting dashboards for both business and IT users. The implementation of RUEI helped the company reduce maintenance costs, improve customer satisfaction, and prevent lost revenue from transaction failures.

Real User Experience Insight

ruiruitang

The document describes how a virtual retail company implemented Oracle's Real User Experience Insight (RUEI) solution to address challenges with monitoring end-user experience, performance issue response times, and gaining business and IT insights. RUEI provided proactive monitoring and diagnostics to prevent lost revenue, faster response to customer issues through error replay, easy identification of bottlenecks, and powerful reporting dashboards for both business and IT users. The implementation of RUEI helped the company reduce maintenance costs, improve customer satisfaction and service levels, and prevent lost revenue from transaction failures.

Developing Sandbox Solutions

Mohamed Yehia Abdul Kader

This document discusses sandbox solutions in SharePoint 2010. Sandbox solutions allow developers to deploy solutions without having to make changes to the farm or web.config files. Sandbox solutions run in an isolated process and are subject to controls enforced by the Code Access Security system. They provide a more secure way to rapidly deploy extensions that can be monitored and managed at the site collection level by farm administrators. The document outlines how sandbox solutions work, what types of components they support, restrictions, best practices for developing, validating, managing and monitoring sandbox solutions.

project plan

Jayshankar Kumar

This document provides a software project plan for the WMITS project. It includes sections on goals and scope, estimates and resources, risk management, schedule, team organization, and tracking mechanisms. The project aims to automate environmental inspection processes. Risks include time constraints, funding needs for pilot integration, and obtaining necessary skills. Estimates using process-based and LOC methods indicate effort of 7-14 person-months and costs of $33,000-$40,000. The 3-person team will have specialized roles to complete the project in 3 months.

Alm Specialist Toolkit Team System 2008 Deep Dive

Christian Thilmany

The document discusses software project failures and the benefits of using an integrated platform like Visual Studio Team System (VSTS) for software development. It notes that on average in 2000-2004, software projects were 45% over budget, 63% over schedule, and only delivered 67% of planned functionality. VSTS provides features like version control, work item tracking, build automation, and reporting that help improve collaboration, accountability, visibility and quality of software projects. It discusses how one company saw a 225% ROI and 6 month payback by deploying VSTS across their development teams.

Managing EBS Testing, Performance, Configurations, Change & User experience

InSync Conference

The document discusses Oracle solutions for managing E-Business Suite (EBS) applications, including Oracle Application Testing Suite, Oracle Functional Testing, Oracle Load Testing, Oracle Test Manager, Oracle Real User Experience Insight, and Oracle Application Management Pack. These solutions provide comprehensive application management from testing and implementation to optimization, with features like automated testing, performance monitoring, configuration management, and issue tracking.

Measure and increase developer productivity with help of Severless by Kazulki...

Vadym Kazulkin

The goal of Serverless is to focus on writing the code that delivers business value and offload everything else to your trusted partners (like Cloud providers or SaaS vendors). You want to iterate quickly and today’s code quickly becomes tomorrow’s technical debt. In this talk we will show why Serverless adoption increases the developer productivity and how to measure it. We will also go through AWS Serverless architectures where you only glue together different Serverless managed services relying solely on configuration, minimizing the amount of the code written.

T3 Consortium's Performance Center of Excellence

veehikle

The Complete User Experience Monitoring Solution - eG Enterprise v7

eG Innovations

Application Express - A web development environment for the masses - and for ...

Sage Computing Services

Application express has been enthusiastically adopted by many clients as a tool for the rapid development of database centric web applications. This presentation discusses some of the techniques used to develop Apex applications. It provides guidelines on best practices and includes the initial steps that should be considered when embarking on an Apex development. The presentation includes a look at development techniques for the 2.2 version, and a preview of some of the features that are available in version 3.0.

Sp2010 high availlability

Samuel Zürcher

SharePoint 2010 provides several options for implementing high availability architectures. Key components include web front end servers, application servers, and SQL servers. High availability ensures a predetermined level of uptime through strategies like redundancy, failover, virtualization and disaster recovery. Services like search and user profiles can be made highly available across multiple farms using replication technologies. Monitoring and service distributions are important to achieve redundancy.

Jboye slides-27-02-2013

1. High availability med SharePoint 2013 hos Saxobank Hvilke karv og overvejelser har vi gjort os indtil i dag

4. Udfordringen

5. IT er generelt nød til at lytte til forretningens krav. GOVERNANCE

6. Fysisk arkitektur Logisk arkitektur Farm Zone Web App Service App Content DB Service Site collection Site List / Library [Foldere] Item / Dokument

7. Designe udvikle 2 uger Definere Deploy rettelser vedligehold måling

9. For a given software application or service, high availability is ultimately measured in terms of the end user’s experience and expectations. The tangible and perceived business impact of downtime may be expressed in terms of information loss, property damage, decreased productivity, opportunity costs, contractual damages, or the loss of goodwill. The principal goal of a high availability solution is to minimize or mitigate the impact of downtime. A sound strategy for this optimally balances business processes and Service Level Agreements (SLAs) with technical capabilities and infrastructure costs. A platform is considered highly available per the agreement and expectations of customers and stakeholders. The availability of a system can be expressed as this calculation: Actual uptime/Expected uptime X 100% The resulting value is often expressed by industry in terms of the number of 9’s that the solution provides; meant to convey an annual number of minutes of possible uptime, or conversely, minutes of downtime. Number of 9's Availability Percentage Total Annual Downtime 2 99% 3 days, 15 hours 3 99.9% 8 hours, 45 minutes 4 99.99% 52 minutes, 34 seconds 5 99.999% 5 minutes, 15 seconds http://technet.microsoft.com/en-us/library/jj715263.aspx

12. Aktiv Passiv

13. Aktiv Aktiv

14. Load balance Web frontend Web frontend Site Site Central admin Central admin

17. Load balance Web frontend Web frontend Web frontend Web frontend Site Site Site Site Central admin Central admin

19. http://technet.microsoft.com/en-us/library/cc262485.aspx

22. All servers that belong to a server farm, including database servers, must physically reside in the same datacenter. Redundancy and failover between closely located data centers that are configured as a single farm ("stretched farm”) is not supported in SharePoint 2013. http://technet.microsoft.com/en-us/library/cc262485.aspx

25. Load balance Web frontend Web frontend Web frontend Web frontend Site Site Site Site Central admin Central admin

32. Load balance Web frontend Web frontend Web frontend Web frontend Site Site Site Site Central admin Central admin

33. Med en farm offline:

35. http://www.pa.com.au/promo/sharepoint- 2013/highavailability/ http://www.slideshare.net/michaeltnoel/sql-2012- alwayson-availability-groups-for-sharepoint-2013- sharepoint-connections-amsterdam-2012 http://technet.microsoft.com/en- us/library/jj715263.aspx http://blog.appliedis.com/2012/12/12/sharepoint- conference-2012-high-availability-solutions-with- sharepoint-2013/

Jboye slides-27-02-2013

More Related Content

Similar to Jboye slides-27-02-2013

Similar to Jboye slides-27-02-2013 (20)

Jboye slides-27-02-2013