| PAGE CONTENTS |
| Preamble |
| What is Multi-AZ: Aria Operations for Logs |
| What it means for Customers |
Preamble : VMware has forged its committment in providing highly resilient Modern Applications/Solutions in Multi-Cloud Universe. Aria Operations for Logs has an robust architecture which has methodical FT, HA & DR strategies in place. “Multi-Availability Zone support for Aria Operations for Logs” is a testimony of VMware meliorating in every aspect of service delivery to its customers.
What are Multi-Availability Zones: Aria Operations for Logs
What is Cloud Region: actual, real-life geographic location where your public cloud resources are located.
What is a Multi-Availability Zone: These are Multiple, Isolated locations within each region.
VMware has diligently engineered its Aria Operations for Logs in different levels of availability and different SLA Objectives. The application has been entrusted by customers to provide high throughput, responsiveness, and recovery time in case of failure. Considering the deployment-specific requirements, distributing compute and storage across availability zones in a combination with placement groups/policies is a way to address this challenge of High Availability. A pragmatic combination of those options discussed above and proprietary backend apps can meet the requirements presented by each layer in the entire Aria Operations for Logs Stack.
‘Aria Operations for Logs’ have been made available in “Multiple Availability Zones” for a given region.
What it means for Customers
The distinct challenge for any service to be highly available, fault-tolerant and the lowest time to recovery on the cloud lies in data. Aria Operations for Logs being highly resilient in being able to be accessible by all customers worldwide is one dimension, another dimension is to have their customer data (logs ingested) be made highly available, fault-tolerant & low MTTR is a very crucial aspect. The critical data apart from credentials & configurations are the logs ingested into the Indexed Partitions & Non-Indexed Partitions.
VMware understands that logs ingested data in both partitions are equally important for customers. Indexed Partition has 30 days of retention & Non-Indexed Partitions have a retention period of up to 7 years. Relatively Non-Indexed Storage with an option of log data retentions up to 7 years has been given with the purpose of meeting ISO/IEC requirements that the organization has been certified for, statutory, regulatory, legal, and audit requirements.
When a Primary Availability Zone is DOWN
On deep contemplation considering the above, VMware has introduced the availability of Non-Indexed Partitions in case the Primary Availability Zone is DOWN for a given region. The Indexed Partition will not be available till the Primary Availability Zone is UP and Running. Whilst, Primary Availability Zone is DOWN, all the logs sent from various endpoints for a given customer VMware Cloud Org are stored in the buffer. Once the Primary AZ is UP, the logs would be ingested from the buffer which ensures there is no log data loss during the outage.
For easier understanding, read below based on the context.
When Primary Availability Zone is DOWN
- There is no impact on Aria Operations for Logs. End Users will continue to use the services in their respective tenants in VMware Cloud Services Console.
- The Logs stored in Non-Indexed Partitions will continue to be available and end users can query on Non-Indexed Partitions.
- The Indexed Partition will ‘NOT’ be available for end users. This means end users will not be able to query Old or New logs.
- Once the Primary Availability Zone is UP & Running, the Aria Operations for Logs will ingest all the logs stored in a buffer and it will work without any loss of data or log data that is ingested during an outage.