Road to cloud-iaas
•Download as PPTX, PDF•
0 likes•280 views
This presentation will go throw IAAS inside Azure
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (14)
Similar to Road to cloud-iaas
Similar to Road to cloud-iaas (20)
Recently uploaded
Recently uploaded (20)
Road to cloud-iaas
- 1. Technology Oriented Course Microsoft Azure IAAS Hatem AlSum Cloud Technical Consultant Cloud Niners
- 4. What the difference from Management perspective
- 5. Storage
- 7. General Purpose Storage Account •Standard Performance •Tables •Blobs •Queues •File •Premium Performance •Azure VMs Disks
- 8. Replication for Durability and High Availability
- 9. Comparison of storage types
- 12. Networking
- 13. Networking in Azure • Overview for Virtual Network • VPN • Site to Site • Point to Site • Load Balancer
- 14. Network : Virtual Network
- 16. Network : Site to Site VPN
- 19. Compute
- 20. VM Compute Size : A Family •Highest Value VM Size •Basic and Standard Sizes •General Purpose and High Memory •Up to 16 Cores , 112 GB RAM A
- 21. VM Compute Size : D Family •60 % Faster CPU •Local SSD Storage •Up to 20 Cores, 140 GB RAM D
- 22. VM Compute Size : G Family •Optimized for data workload •Latest generation on intel processors •Up to 6.1 TB Local Storage •Up to 32 Cores, 448 GB RAM G
- 24. Availability of virtual machines • Planned Maintenance • Periodic Updates • Security Update • Unplanned Maintenance • Hardware or Physical Failure • Network • Local Disks • Rack Level Failure
- 25. Fault Domain , Update Domain • Update Domain: Define group of virtual machines that will be update (could require restart) VMs within same UD could be restarted due planned maintenance • Fault Domain : define the group of virtual machines that share a common power source and network switch
- 26. Best Practice for High Availability • Configure multiple virtual machines in an Availability Set for redundancy • Configure each application tier into separate Availability Sets • Combine the Load Balancer with Availability Sets • Avoid single instance virtual machines in Availability Sets
- 29. Demo Creating Virtual Machine Azure Portal
- 31. Recovery Point Objective • The acceptable time window of lost data due to the recovery process Recovery Time Objective • The maximum amount of time allocated for restoring application functionality.
- 32. Azure Backup
- 33. Azure Backup Methods •Azure Backup agent (Any VM or Physical) •System Center Data Protection Manager (DPM) •Azure Backup (VM extension)
- 34. How Azure Backup Vault with Backup agent
- 38. SQL Server Always On Replication
- 39. Code Demo Infrastructure as a code
- 40. Thank You
Editor's Notes
- Blob Storage stores unstructured object data. A blob can be any type of text or binary data, such as a document, media file, or application installer. Blob storage is also referred to as Object storage. Table Storage stores structured datasets. Table storage is a NoSQL key-attribute data store, which allows for rapid development and fast access to large quantities of data. Queue Storage provides reliable messaging for workflow processing and for communication between components of cloud services. File Storage offers shared storage for legacy applications using the standard SMB protocol. Azure virtual machines and cloud services can share file data across application components via mounted shares, and on-premises applications can access file data in a share via the File service REST API. Blob Storage stores unstructured object data. A blob can be any type of text or binary data, such as a document, media file, or application installer. Blob storage is also referred to as Object storage. Table Storage stores structured datasets. Table storage is a NoSQL key-attribute data store, which allows for rapid development and fast access to large quantities of data. Queue Storage provides reliable messaging for workflow processing and for communication between components of cloud services. File Storage offers shared storage for legacy applications using the standard SMB protocol. Azure virtual machines and cloud services can share file data across application components via mounted shares, and on-premises applications can access file data in a share via the File service REST API.
- A standard performance tier which allows you to store Tables, Queues, Files, Blobs and Azure virtual machine disks. A premium performance tier which currently only supports Azure virtual machine disks. See Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads for an in-depth overview of Premium storage.
- Replication for Durability and High Availability The data in your Microsoft Azure storage account is always replicated to ensure durability and high availability, meeting the SLA for Storage even in the face of transient hardware failures. When you create a storage account, you must select one of the following replication options: Locally redundant storage (LRS). Locally redundant storage maintains three copies of your data. LRS is replicated three times within a single facility in a single region. LRS protects your data from normal hardware failures, but not from the failure of a single facility. LRS is offered at a discount. For maximum durability, we recommend that you use geo-redundant storage, described below. Zone-redundant storage (ZRS). Zone-redundant storage maintains three copies of your data. ZRS is replicated three times across two to three facilities, either within a single region or across two regions, providing higher durability than LRS. ZRS ensures that your data is durable within a single region. ZRS provides a higher level of durability than LRS; however, for maximum durability, we recommend that you use geo-redundant storage, described below. Geo-redundant storage (GRS). Geo-redundant storage is enabled for your storage account by default when you create it. GRS maintains six copies of your data. With GRS, your data is replicated three times within the primary region, and is also replicated three times in a secondary region hundreds of miles away from the primary region, providing the highest level of durability. In the event of a failure at the primary region, Azure Storage will failover to the secondary region. GRS ensures that your data is durable in two separate regions. Read access geo-redundant storage (RA-GRS). Read access geo-redundant storage replicates your data to a secondary geographic location, and also provides read access to your data in the secondary location. Read-access geo-redundant storage allows you to access your data from either the primary or the secondary location, in the event that one location becomes unavailable.
- Planned maintenance events are periodic updates made by Microsoft to the underlying Azure platform to improve overall reliability, performance, and security of the platform infrastructure that your virtual machines run on. The majority of these updates are performed without any impact upon your virtual machines or cloud services. However, there are instances where these updates require a reboot of your virtual machine to apply the required updates to the platform infrastructure. Unplanned maintenance events occur when the hardware or physical infrastructure underlying your virtual machine has faulted in some way. This may include local network failures, local disk failures, or other rack level failures. When such a failure is detected, the Azure platform will automatically migrate your virtual machine from the unhealthy physical machine hosting your virtual machine to a healthy physical machine. Such events are rare, but may also cause your virtual machine to reboot.
- Planned maintenance events are periodic updates made by Microsoft to the underlying Azure platform to improve overall reliability, performance, and security of the platform infrastructure that your virtual machines run on. The majority of these updates are performed without any impact upon your virtual machines or cloud services. However, there are instances where these updates require a reboot of your virtual machine to apply the required updates to the platform infrastructure. Unplanned maintenance events occur when the hardware or physical infrastructure underlying your virtual machine has faulted in some way. This may include local network failures, local disk failures, or other rack level failures. When such a failure is detected, the Azure platform will automatically migrate your virtual machine from the unhealthy physical machine hosting your virtual machine to a healthy physical machine. Such events are rare, but may also cause your virtual machine to reboot.
- Planned maintenance events are periodic updates made by Microsoft to the underlying Azure platform to improve overall reliability, performance, and security of the platform infrastructure that your virtual machines run on. The majority of these updates are performed without any impact upon your virtual machines or cloud services. However, there are instances where these updates require a reboot of your virtual machine to apply the required updates to the platform infrastructure. Unplanned maintenance events occur when the hardware or physical infrastructure underlying your virtual machine has faulted in some way. This may include local network failures, local disk failures, or other rack level failures. When such a failure is detected, the Azure platform will automatically migrate your virtual machine from the unhealthy physical machine hosting your virtual machine to a healthy physical machine. Such events are rare, but may also cause your virtual machine to reboot.
- Planned maintenance events are periodic updates made by Microsoft to the underlying Azure platform to improve overall reliability, performance, and security of the platform infrastructure that your virtual machines run on. The majority of these updates are performed without any impact upon your virtual machines or cloud services. However, there are instances where these updates require a reboot of your virtual machine to apply the required updates to the platform infrastructure. Unplanned maintenance events occur when the hardware or physical infrastructure underlying your virtual machine has faulted in some way. This may include local network failures, local disk failures, or other rack level failures. When such a failure is detected, the Azure platform will automatically migrate your virtual machine from the unhealthy physical machine hosting your virtual machine to a healthy physical machine. Such events are rare, but may also cause your virtual machine to reboot.
- Configure multiple virtual machines in an Availability Set for redundancy Configure each application tier into separate Availability Sets Combine the Load Balancer with Availability Sets Avoid single instance virtual machines in Availability Sets
- This is based on business requirements and is related to the importance of the application. Critical business applications require a low RTO
- Using Backup Vault and Azure Backup Agent
- Configure multiple virtual machines in an Availability Set for redundancy Configure each application tier into separate Availability Sets Combine the Load Balancer with Availability Sets Avoid single instance virtual machines in Availability Sets
- https://azure.microsoft.com/en-us/blog/disaster-recovery-to-azure-using-azure-site-recovery-is-now-ga/