Step-by-Step Virtual Machine Backup on AZURE
>
SharePoint Portal Migration to AZURE
SharePoint Portal migration to AZURE
plan
Today
I will outline action plan for Intranet/Internet “On-Premise” SharePoint portal
migration to AZURE, at the end of this post you will find the required
links/documents for Implementation steps .
1- SharePoint
Architecture on AZURE
The below Image describing high availability architecture for
SharePoint, SQL Servers and AD DS VMs. Note that you can replace AD DS VMs by
AZURE AD DS “Domain Controller as a Service”.
You can refer to this link for more details about AZURE AD DS
2- SQL
Server Architecture on AZURE
You will need 3 servers one as a file share or quorum and two
servers for Implementing SQL Server Always On.
 |
3- Pre-requisites
a. Global
administrator privilege on AZURE tenant.
b. Contributor/Owner
privilege on AZURE subscription.
c. AZURE
Active Directory Domain Services either Self-Managed or DC as a service.
i. AZURE
AD User for AZURE AD DS joining with global administrator privilege.
ii. VM
for domain joining testing & managing users in AZURE AD DS.
d. Site-To-Site
VPN connection between On-Premise and AZURE.
4- Implementation
Steps
a. Implement
the following steps on Test environment then Production environment
i. Create
two SQL Servers VMs and configure/enable Always On between the two VMs.
ii. Extend
SQL Server Always Availability Groups on On-Premise to AZURE.
iii. Migrate
SharePoint VMs to AZURE using AZURE Migrate.
iv. Test
Failover of SharePoint VMs to a development VMs, then cutover on go live date.
v. Join
SharePoint and SQL Server VMs to AZURE AD DS.
vi. Secure
the application using AZURE Application Gateway.
vii. Test
the application.
5- Post
Implementation Steps
a. Decide
and Implement Backup Policy for VMs and SQL Server on AZURE.
6- Design
considerations:
a. For
SQL Server & SharePoint VMs production environment we need to choose
either:
i. Single
Instance: Virtual Machine using premium storage for all Operating System Disks
and Data Disks, AZURE guarantee you will have Virtual Machine Connectivity of
at least 99.9%
ii. Availability
Sets: VMs are deployed so that they are not all subject to a single
point of failure and not all upgraded at the same time during a host operating
system upgrade in the datacenter; it offers 99.95% VM
uptime SLA.
iii. Availability
Zones: protect from datacenter level failures and it offers 99.99% VM uptime SLA.
This
table Inform about expected down time for each option to be able to decide
which option you will choose
Availability %
|
Downtime
per year
|
Downtime
per month
|
Downtime
per week
|
Downtime
per day
|
99.9% ("three nines")
|
8.77
hours
|
43.83
minutes
|
10.08
minutes
|
1.44
minutes
|
99.95% ("three and a half
nines")
|
4.38
hours
|
21.92
minutes
|
5.04
minutes
|
43.20
seconds
|
99.99% ("four nines")
|
52.60
minutes
|
4.38
minutes
|
1.01
minutes
|
8.64
seconds
|
References:
Step-by-Step Add AZURE Active Directory to your AZURE Subscription
Choose
a solution for connecting an on-premises network to Azure
What
is VPN Gateway?
Tutorial:
Create and configure an Azure Active Directory Domain Services instance
Designing
a SharePoint Server 2016 farm in Azure
Deploying
SharePoint Server 2016 with SQL Server Always On Availability Groups in Azure
Microsoft
SharePoint Server 2016 Architectural Models
SharePoint2016ArchitecturalModels.pdf
Tutorial:
Join a Windows Server virtual machine to a managed domain
Prerequisites
for creating Always on availability groups on SQL Server on Azure virtual
machines
Tutorial:
Configure availability group on Azure SQL Server VM manually
Extend
on-premises Always On Availability Groups to Azure
Deploy
Azure AD Domain Service and Join a Server to the Domain
Run
a highly available SharePoint Server 2016 farm in Azure
Highly
available SharePoint farm
Prepare
Azure for on-premises disaster recovery to Azure
Migrate
on-premises machines to Azure
Prepare
on-premises VMware servers for disaster recovery to Azure
Popular posts from this blog
Step-by-Step Add AZURE Active Directory DS to your AZURE Subscription
In this post I will describe how to add AZURE Active Directory Domain services to your tenant using AZURE Portal and create a VM then join it to the created domain. Login to AZURE Portal Create new resource group Click review and create Search for AZURE AD DS and choose AZURE AD Domain Services Click ADD Choose subscription and resource group After filling the required fields click Next Choose the default VNet & Subnet or customize as per your requirement Add more Administrators If needed or accept the default then click next Accept the default then press Next After validation complete press create Press Ok to start creating AZURE AD Domain Services It might take an hour to be finished
Azure AD DS Highlights
In the following document we will discuss about AZURE AD DS, the following points will be covered: Why AZURE AD DS? Comparison between AD DS, AZURE AD, AZURE AD DS. Azure AD DS and self-managed AD DS. Use Cases. AZURE AD DS Implementation Steps. References. Why AZURE AD DS? If your application is hosted partly on-premises and partly in Azure, it may be more efficient to replicate Active Directory Domain Services (AD DS) in Azure. This can reduce the latency caused by sending authentication requests from the cloud back to AD DS running on-premises. This architecture is commonly used when the on-premises network and the Azure virtual network are connected by a VPN or ExpressRoute connection. This architecture also supports bidirectional replication, meaning changes can be made either on-premises or in the cloud, and both sources will be kept consistent. Typical uses for this architecture include hybrid applications in which functionality is
Step-by-Step Azure Virtual Desktop & Joining AZURE ADDS
In this post I will show how to create Azure virtual desktop and join AZURE Active Directory Domain Services 1- Login to your subscription 2- Enter Windows Virtual Desktop into the search bar, then find and select Windows Virtual Desktop under Services. 3- In the Windows Virtual Desktop overview page, select Create a host pool . 4- In the Basics tab, select the correct subscription under Project details. 5- Either select Create new to make a new resource group or select an existing resource group from the drop-down menu. 6- Enter a unique name for your host pool. In the Location field, select the region where you want to create the host pool from the drop-down menu. 7- Enter the required details. Will create only one VM as this will fit the requirement for now. I used also B2s size and Windows 10 Enterprise multi session. Scroll down and complete the rest of requ
Comments
Post a Comment