Understanding recovery plans – Developing Business Continuity
Using recovery plans allows you to have far greater control over what is failed over and when. Using this mechanism, you can have more direct control over the timing of failovers for individual services. Typically, you would group applications into a recovery plan; for example, if you have a web application consisting of a VM …
Understanding recovery plans – Developing Business ContinuityRead More
Planning for Site Recovery – Developing Business Continuity
Business-critical applications may have different backup and recovery requirements to servers that don’t change often or store data. For applications that need to be recovered quickly, or that need to be backed up every few minutes or hours, Recovery Services values also provide a tool called Azure Site Recovery. Both Azure Backup and Azure Site …
Planning for Site Recovery – Developing Business ContinuityRead More
Understanding backup policies – Developing Business Continuity
A backup policy is used to define different aspects of how you want to back up your workloads, and multiple policies can be created and used. For example, you may want to use one policy for application VMs that don’t change very often, and a separate policy for database VMs, whose data changes continually. Once …
Understanding backup policies – Developing Business ContinuityRead More
Understanding the Recovery Point Objective (RPO) – Developing Business Continuity
An RPO is often stated alongside an RTO. If you are architecting a solution that performs regular backups of your platform, then you also need to consider how often those backups are taken. This effectively determines your RPO, which is the maximum amount of time that can pass between backups. For example, an RPO of …
Understanding the Recovery Point Objective (RPO) – Developing Business ContinuityRead More
Understanding security and compliance – Designing for Logging and Monitoring
Security and compliance are important factors in all organizations. As we move our solutions to the cloud, we need to ensure that the resources we build do not expose data to the public network. In addition, many organizations define governance policies that must be adhered to; sometimes these are aligned to regulatory compliance, and sometimes …
Understanding security and compliance – Designing for Logging and MonitoringRead More
Azure Metrics – Designing for Logging and Monitoring
At the start of the chapter, we said that metrics describe an aspect of a system at a particular point in time and are displayed in numerical values. Typical examples include CPU utilization, disk reads and writes, network usage, and storage capacity or usage. As each service in Azure performs different tasks, the metrics we …
Azure Metrics – Designing for Logging and MonitoringRead More
Understanding deployment options – Designing for Logging and Monitoring
By default, only Azure activity logs and platform metrics are enabled. Sending those logs to a Log Analytics workspace or enabling VM agents must be explicitly done. The VM agents are installed when you activate specific tools, such as VM insights, enabling guest-level monitoring, or enabling Logs in the Azure portal. As we see in …
Understanding deployment options – Designing for Logging and MonitoringRead More
VM logging and monitoring – Designing for Logging and Monitoring
Because VMs generate logs as part of the operating system – Windows event logs for Windows servers and syslogs for Linux servers – Microsoft provides agents that must be installed on the VMs. There are four different agents that can be installed on VMs, and each either collects different logs or can send them to …
VM logging and monitoring – Designing for Logging and MonitoringRead More
Understanding data types and sources – Designing for Logging and Monitoring-2
By default, basic logs and metrics are stored automatically on the platform and you can view up to 30 days of history. These default views also provide basic filtering and monitoring options to get a high-level view of what is happening to your solutions. If you need longer retention of logs or wish to perform …
Understanding data types and sources – Designing for Logging and Monitoring-2Read More
Understanding data types and sources – Designing for Logging and Monitoring-1
Monitoring data is largely split into two different types – metrics and logs. Metrics describe an aspect of a system at a particular point in time and are displayed in numerical values. They are capable of supporting near real-time scenarios. Logs are different from metrics. They contain data that is organized into records, with different …
Understanding data types and sources – Designing for Logging and Monitoring-1Read More
