Moving from Aria Operations for Logs 8.x to VCF Operations for logs

Existing Aria Operations for Logs clusters are not upgraded in place. A new VCF Operations for logs cluster is deployed, sources are pointed at it, and historical data is copied across.

No upgrade path exists from Logs clusters at version 8.18 or earlier to VCF Operations for logs.
VCF Operations 9.0 works only with VCF Operations for logs; integrations with older Aria Operations for Logs versions must be deleted, and VCF does not permit integrating VCF Operations with Aria Operations for Logs.
The old 8.18.x instance stays operational during a deprecation period, but active log sources must be reconfigured to send to the new cluster. Where several 8.18.x instances forward to a central aggregator, each remote instance is reconfigured to forward to the new cluster.
Configuring the new cluster as a forwarding destination in Aria Operations for Logs sends only new logs; logs that were already ingested are not forwarded.

Log Data Transfer

Historical logs are copied with Log Data Transfer from Administration > Control Panel > Logs Data Transfer card (INITIATE TRANSFER).

Rule	Detail
Maximum history per transfer	Up to 90 days
Recommended first transfer	The last 10 days
Prerequisite	The operations-logs appliance must already be set up in VCF
Source credentials	All source Aria Operations for Logs nodes must share the same SSH credentials
Connectivity	Source nodes must be reachable on port 22 from the VCF Operations for logs nodes
Capacity	Not all buckets are copied if the target lacks free disk space; check capacity first

Content packs remain available in the VCF Operations for logs UI, but they are being deprecated in favour of management packs; alerts, dashboards and saved queries can be added to management packs in VCF Operations.

Common trap: Planning an in-place upgrade of Aria Operations for Logs 8.18 to 9.0 - there is no upgrade path; deploy a new VCF Operations for logs cluster, redirect sources, and use Log Data Transfer for up to 90 days of history.

Get the whole book

This note is one section of Ultra Transcenders 2V0-17.25: VMware Cloud Foundation Administrator, an independent study guide that explains every topic the exam covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to Broadcom TechDocs.

Amazon.co.ukKindle: coming soonPaperback: coming soon

Amazon.comKindle: coming soonPaperback: coming soon

Publishing soon on Amazon in Kindle and paperback editions.

About the book · 2V0-17.25 terms in the glossary · All 2V0-17.25 study notes

More 2V0-17.25 study notes

Components renamed or replaced in VMware Cloud Foundation 9.0
Aria, Cloud Builder, ESXi and vSphere with Tanzu: what each is called in VCF 9.0 and what replaced it.
vSAN ESA vs vSAN OSA in VCF 9.0
How the Express and Original Storage Architectures differ, and when each fits.
vSAN space efficiency: deduplication, compression and erasure coding
What each vSAN space-efficiency option saves, what it costs and where it applies.
NSX VPCs: centralized vs distributed connectivity
Tier-0 on an Edge cluster or a distributed transit gateway: what each gives VPCs and what it rules out.
VCF Operations metrics, properties and super metrics
The difference between metrics and properties, and when a super metric is the answer.
VCF Operations policies: priority, inheritance and what they control
How VCF Operations policies decide what is collected and alerted on, and which policy applies to an object.
VCF Automation multi-organization tenancy
All Apps and VM Apps organizations, and how providers carve up a VCF Automation instance.