> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Archive Older OCI Log Analytics Data

> Set a 30-day archival period in OCI Log Analytics so older log data moves to cheaper archival storage.

OCI Log Analytics bills active storage at a higher rate than archival storage. Without an archival period, all log data stays in active storage for as long as it is kept. nOps finds Log Analytics data held in active storage with little or nothing archived, measures how much of it is older than 30 days, and estimates the saving from archiving that part.

| | |
| - | - |
| **Cloud** | Oracle Cloud (OCI) |
| **Category** | Management and governance |
| **Service** | OCI Log Analytics |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Most log searches, dashboards and alerts look at recent data, while older data stays in active storage and is billed at the full rate.

## How nOps finds it

nOps reads OCI Log Analytics storage billing. Active storage must be billed on at least 30 of the last 31 days, archival storage must be under 20% of active, and active storage must not have fallen in the last 37 days. The share older than 30 days is measured as the storage held 30 days ago divided by the storage held now. The saving is the last 7 days of active storage cost, scaled to a month, times that share, times the difference between Oracle's archival list price ($0.02 per 300 GB unit per hour) and the active rate you pay. It must be at least $5 a month, and tenancies with 90% or more of Log Analytics spend covered by credits are left out.

## Before you start

Confirm data older than 30 days is not needed for interactive searches, dashboards or alerts.

## How to implement

1. Check which searches, dashboards and alerts read data older than 30 days.
2. In the OCI Console, open **Log Analytics → Administration → Storage** and enable archiving with an active period of 30 days.
3. Check the next week's billing for archival storage replacing part of active storage.

## Risks and considerations

* Archived data must be recalled before it can be searched again, and recalling it is charged.
* To roll back, turn archiving off or lengthen the active period; recall any archived data you need active again.

## Related

* [Move Older Log Analytics Data to Long-Term Retention](https://help.nops.io/inform/supported-recommendations/move-older-log-analytics-data-to-long-term-retention)
* [Move Long-Term Log Retention to Cloud Storage Archive](https://help.nops.io/inform/supported-recommendations/move-long-term-log-retention-to-cloud-storage-archive)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.