Hallo,
seit 21.1.2013 gibt es eine Guideline wie man SharePoint 2013 & SQL Server in Azure VM einrichtet. In der Beschreibung geht es um die Voraussetzungen und Regel was erlaubt ist und was nicht. Die 56 Seiten sind sehr interessant für SharePoint und SQL Geeks.
Ich habe mir mal die Mühe gemacht und die interessantesten Punkte herauskopiert:
Deployment Considerations for SharePoint 2013 on Windows Azure Virtual Machines:
1. VHD-Type: fixed vs. dynamic:
A VHD can be in either a fixed format or a dynamic format, but only the fixed format of VHD files is supported in Windows Azure Virtual Machines. Therefore, it is also required for SharePoint that VHD drives be in fixed format.
2. Hybrid Farm – WFE in Azure und DB-Server onpremise:
For customer’s SharePoint 2013 deployment, they will need to have their SQL servers also located on Windows Azure Virtual Machines. It is not supported to have the SQL Servers on premise or in another datacenter, talking to the SharePoint Virtual Machines on Windows Azure.
3. Garantie der QoS für das Netzwerk: 1 ms Latenz-Regel
Therefore, all SharePoint Virtual Machines in the Windows Azure Virtual Machines farm should be in the sameaffinity group and be on the same VNET. Also Microsoft, does not support a wide area network (WAN) topology in which a server that is running SQL Server is deployed remotely from other components of the farm over a network that has latency greater than 1 millisecond (ms). This topology has not been tested and is not supported. For more information, please see: http://support.microsoft.com/kb/971160/EN-US
4. weitere Hardware Themen:
The following are not supported in a Virtual Machine on Windows Azure:
- Multiple IP addresses in a Virtual Machine
- 32 Bit Applications in a Virtual Machine
- Static IP addresses:
o Dynamic addresses must therefore be used instead, which requires that customers create a Windows Azure Virtual Network. Dynamic addresses are effectively become static once they are assigned. (the dhcp lease Zeit ist extreme lang, so wirkt die dynamische IP wie eine statische)
5. Sysprep Rules für SharePoint:
SysPrep is only supported in the following scenarios with SharePoint:
· SharePoint Products and Technologies Configuration (PSConfig) Wizard has not yet been run after the SharePoint installation.
· SharePoint has not been installed in Standalone mode (Database and SharePoint on the same box). Standalone installation is unsupported due to configuration changes made during install that will not be properly adjusted by SysPrep.
6. Cluster & Hochverfügbarkeit & Disaster Recovery
Windows Azure Virtual Machines support for high availability and/or disaster recovery is currently limited to Database Mirroring and Log Shipping. Currently, AlwaysOn Failover Cluster Instances are not supported. However, Windows Server Failover Cluster to support Availability Groups (non-shared Storage) is currently supported. It is not supported for other uses.
7. Active Directory in Azure für SharePoint:
There are two options available for customers who are running their SharePoint Virtual Machines on Windows Azure Virtual Machines and need to decide where to host their AD Domain Controllers:
1. Hosting Active Directory Domain Controllers on Windows Azure Virtual Machines
2. Connecting to On Premise Active Directory Domain Controllers
(a) For this scenario, customers should keep in mind the latency that is involved here when connecting to their on premise Active Directory. This option might have performance and cost impact.
[ich bevorzuge den Eigene DC als AzureVM]
Subnets must be defined in Windows Server AD DS, a site created, the subnets linked to that site, and connected to other sites using appropriate site-links.
Viel Spaß damit.
Liebe Grüße
Patrick