avtex lync 2013 event - fargo
Post on 30-Oct-2014
515 Views
Preview:
DESCRIPTION
TRANSCRIPT
LYNC SERVER 2013SERVER INFRASTRUCTURE / HIGH AVAILABILITY / DISASTER
RECOVERY
RICHARD BRYNTESON
MICROSOFT CERTIFIED MASTER (MCM) LYNC SERVER
FRONT-END POOL- STANDARD AND ENTERPRISE
• ENTERPRISE POOL – MAX 80,000 HOMED USERS
• 6,660 USERS PER FRONT-END SERVER
• MAXIMUM 12 SERVERS PER POOL
• MICROSOFT HARDWARE RECOMMENDATION
• DUAL HEX-CORE / 32 GB RAM
• DISK: 8 X 10K DRIVE OR SSD WITH SIMILAR PERFORMANCE OF 10K
Capacity Planning - http://technet.microsoft.com/en-us/library/gg615015.aspx
FRONT-END POOL- STANDARD AND ENTERPRISE
• STANDARD POOL – MAX USERS UNKNOWN
• MICROSOFT HAS NOT YET RELEASED USER INFORMATION
• MICROSOFT HARDWARE RECOMMENDATION
• SAME AS ENTERPRISE EDITION FRONT-END
Server Hardware Platform - http://technet.microsoft.com/en-us/library/gg398835.aspx
FRONT-END POOL- BEST PRACTICES & MUST KNOW
• VIRTUALIZATION HARDWARE• SUPPORTS WINDOWS 2012 AND 2008 R2 HYPER-V
• NO STATEMENT ON VMWARE, YET!
• NO SIZING GUIDELINES – EXPECTED AROUND GA
Virtualization - http://technet.microsoft.com/en-us/library/gg399035.aspx
FRONT-END POOL- BEST PRACTICES & MUST KNOW
• BEST PRACTICES• ENTERPRISE POOLS SHOULD INCLUDE A MINIMUM OF THREE (3)
FRONT-END SERVERS
• CAN DEPLOY TWO IN A POOL BUT NOT RECOMMENDED• RESET-CSPOOLREGISTRARSTATE -RESETTYPE QUORUMLOSSRECOVERY -POOLFQDN
<FQDN>
• NEED A MINIMUM NUMBER OF SERVERS FOR SERVICES TO START
Front-End Components - http://technet.microsoft.com/en-us/library/gg412996.aspx
FRONT-END POOL- BEST PRACTICES & MUST KNOW
Total number of Front End Servers in the pool
Number of servers that must be running for pool to be functional
1-2* 1*
3-4 2
5-6 3
7-8 4
9-10 5
11-12 6
Front-End Components - http://technet.microsoft.com/en-us/library/gg412996.aspx
FRONT-END POOL- CONFERENCE
• CONFERENCE OVERVIEW• NO LONGER A DEDICATED AV ROLE
• CONFERENCE MAXIMUMS ARE STILL 250 PEOPLE + 125 PEOPLE IN OTHER CONFERENCES
• LARGE CONFERENCE SUPPORT IS 1000 PEOPLE
• REQUIRES A DEDICATED POOL W/ AT LEAST ONE FRONT-END AND ONE SQL SERVER
• OWAS CAN BE SHARED IN DEDICATED POOL
Large Pool - http://technet.microsoft.com/en-us/library/jj205074.aspx
OTHER ROLES
• MEDIATION SERVER• DEDICATED CAN SUPPORT 1100 TO 1500 NON-MEDIA BYPASS CALLS
• COLLOCATED MEDIATION CAN SUPPORT 150 NON-MEDIA BYPASS CALLS
• EDGE SERVER
• 12,000 CONCURRENT USERS
• HARDWARE: DUAL QUAD CORE / 16 GB RAM
Server Hardware - http://technet.microsoft.com/en-us/library/gg615015.aspx
OTHER ROLES
• OFFICE WEB APP SERVER (OWAS)• 700 ACTIVE USERS PER OWAS SERVER
• AVERAGE 1.25 MB IN SIZE / 15 SLIDES
• HARDWARE
• 2 CORE / 8GB RAM
• STILL IN FLUX…
OWAS Capacity Planning - http://download.microsoft.com/download/7/F/0/7F069D0B-B6BD-4692-868B-E8555BB72445/OfficeWebAppsCapacityPlanningDoc.docx
OTHER ROLES
• PERSISTENT CHAT• SAME HARDWARE REQUIRED AS FRONT-END SERVERS
• 20,000 USERS PER SERVER
• MAX FOUR SERVERS PER POOL / 80,000 USERS
• CAN BE COLLOCATED ON STANDARD EDITION
• CAN BE INSTALLED ON LYNC STANDARD EDITION – LOCAL SQL EXPRESS DATABASE – TECHNET IS WRONG!!!
• DIRECTOR
• STILL EXISTS – NO NEED TO DEPLOY
Server Hardware - http://technet.microsoft.com/en-us/library/gg398835.aspx
The PChat backend can be collocated on the SQL Express in case of Standard Edition. Adding our content person to make sure the docs can updated.
Kavita Kamani – Persistent Chat Product Manager, Microsoft
SMALL ORGANIZATION
MEDIUM ORGANIZATION
SUPER ENTERPRISE• MULTIPLE SITES
• EACH SITE IS SIMILAR TO MEDIUM ORGANIZATION
• POOL PAIRING BETWEEN ORGANIZATIONS
• SUPPORTS OVER 80K USERS
OCS 2007 R2/LYNC 2010 UPGRADE
• SUPPORT• NO UPGRADE FROM LCS 2005 OR OCS 2007
• NO TRI-SUPPORT
• CANNOT HAVE OCS 2007 R2, 2010 AND 2013 IN THE SAME TOPOLOGY
• NO GUIDANCE ON CWA 2007 R2
• DOES WORK. NEEDS TO REMOVE CWA 2007 R2 FIRST AND THEN INSTALL NEW 2007 R2 AGAINST THE 2013 POOL
OCS 2007 R2/LYNC 2010 UPGRADE
• CLIENT SUPPORT• OCS 2007 CLIENT IS NOT SUPPORTED!
• OCS 2007 R2 CLIENT SUPPORTED FOR ONLY IM/P
• LYNC 2010 CU7 OR LATER
• LYNC 2013 (REMEMBER WINDOWS 7 OR 8 ONLY)
Upgrade Notes - http://technet.microsoft.com/en-us/library/gg398499.aspx
HIGH AVAILABILITY / DISASTER RECOVERY
• POOL PAIRING• ALLOWS TWO POOLS TO BE PAIRED
• BEST PRACTICE IS TO POOL SIMILAR POOLS
• STANDARD TO STANDARD OR ENTERPRISE TO ENTERPRISE / NOT ENTERPRISE TO STANDARD
• NEAR REAL-TIME REPLICATION OF INFORMATION FROM POOL TO POOL
• REPLICATION DEFAULT IS 2 MINUTES
• CHANGE IT: SET-CSBACKUPSERVICECONFIGURATION –SYNCINTERVAL 00:05:00
POOL PAIRING – WHAT DOES IT LOOK LIKE
• DURING POOL OUTAGE• BUDDY LIST IS NOT AVAILABLE
• CONFERENCING IS NOT AVAILABLE
• CHANGING CALL FORWARDING RULES NOT AVAILABLE
• CAN MAKE/RECEIVE IN-BOUND CALLS
• CALLS CAN BE REDIRECTED TO VOICE MAIL, ASSUMING EXCHANGE UM SERVER IS AVAILABLE
POOL PAIRING DETAILS
• WHAT IS SYNCED• CONTACT INFORMATION
• CONFERENCING MEETINGS AND DATA
• 50 MB LIMIT ON CLIENT UPLOAD OF ATTACHMENTS/POWERPOINT
• WHAT IS NOT SYNCED
• RESPONSE GROUPS & CUSTOM AUDIO FILES
Response Groups - http://blogs.technet.com/b/nexthop/archive/2012/09/04/lync-server-2013-preview-recovering-response-groups-during-disaster-recovery.aspx
POOL PAIRING DETAILS
• GET-CSBACKUPSERVICESTATUS –POOLFQDN <POOLNAME>
• GET-CSPOOLBACKUPRELATIONSHIP –POOLFQDN (DETERMINE YOUR POOL PAIRING STATUS)
• INVOKE-CSBACKUPSERVICESYNC –POOLFQDN (FORCE REPLICATION BETWEEN THE PAIR)
POOL PAIRING DETAILS
• FAILOVER PROCESS• HAVE BACKUPS OF YOUR RGS CONFIGURATION (EXPORT-CSRGSCONFIGURATION)
• POOL A HAS FAILED
• FAILOVER CMS (IF HOSTED ON POOL A)
• RESTORE RGS FROM POOL A TO POOL B (IMPORT-CSRGSCONFIGURATION)
• INVOKE-CSPOOLFAILOVER –POOLFQDN POOLA.DOMAIN.COM –DISASTERMODE
• NOTE: WHEN RGS IS FAILED TO POOL B – CAN ONLY BE MANAGED VIA POWERSHELL
Pool Failover - http://technet.microsoft.com/en-us/library/jj721939.aspx
POOL PAIRING DETAILS
• FAILBACK PROCESS• EXPORT RGS FROM POOL B WITH –OWNERAS FLAG
• BRING POOL A BACK ONLINE
• INVOKE-CSPOOLFAILBACK TO POOL A
• IMPORT RGS INTO POOL A
Pool Failover - http://technet.microsoft.com/en-us/library/jj721939.aspx
LYNC 2013 BANDWIDTH NEEDS
• POTENTIAL FOR SIGNIFICANTLY MORE BANDWIDTH USAGE• NEED TO MAKE SURE TO ACCOUNT FOR BANDWIDTH
• RTVIDEO TO H.264 SVC
• CLIENT CAN STREAM UP TO AND RECEIVE UP TO FIVE VIDEO STREAMS
• AUDIO DIDN’T CHANGE
• RTAUDIO / MAX 62 KBPS & G722 / 101 KBPS
Network Bandwidth - http://technet.microsoft.com/en-us/library/jj688118%28v=ocs.15%29.aspx
Video codec Resolution and aspect ratio Maximum video payload bitrate (Kbps)
Minimum video payload bitrate (Kbps)
H.264 320x180 (16:9)212x160 (4:3) 250 15
H.264/RTVideo 424x240 (16:9))320x240 (4:3 350 100
H.264 480x270 (16:9)424x320 (4:3) 450 200
H.264/RTVideo 640x360 (16:9)640x480 (4:3) 800 300
H.264 848x480 (16:9) 1500 400
H.264 960x540 (16:9) 2000 500
H.264/RTVideo 1280x720 (16:9) 2500 700
H.264 1920x1080 (16:9) 4000 500
H.264/RTVideo 960x144 (20:3) 500 15
H.264 1280x192 (20:3) 1000 250
H.264 1920x288 (20:3) 2000 500
Network Bandwidth - http://technet.microsoft.com/en-us/library/jj688118%28v=ocs.15%29.aspx
LYNC 2013 BANDWIDTH EXAMPLE
Network Bandwidth - http://technet.microsoft.com/en-us/library/jj688118%28v=ocs.15%29.aspx
1
5 Users 5 Users
101 Kbps (G722) Per User X 5 Users = 505 Kbps
WAN
250 Kbps (H.264) Per User X 5 Users = 1250 Kbps
101 Kbps (G722) for 1 Active Speaker = 101 Kbps
(250 Kbps X 5) = 1250 Kbps X 5 People = 6250 Kbps
LYNC 2013 BANDWIDTH EXAMPLE | COMPLEX
Network Bandwidth - http://technet.microsoft.com/en-us/library/jj688118%28v=ocs.15%29.aspx
1
5 Users 5 Users
101 Kbps (G722) Per User X 5 Users = 505 Kbps
WAN
250 + 450 Kbps Per User X 5 Users = 3500 Kbps
101 Kbps (G722) for 1 Active Speaker = 101 Kbps
(250 Kbps X 5) = 1250 Kbps X 3 People = 3750 Kbps
(450 Kbps X 5) = 2250 Kbps X 2 People = 4500 Kbps
top related