OneView Archiving

The historic data that is searchable in OneView is automatically moved to the long-term storage by the scheduled process, called archiving.

The OneView automated archiving impacts only the length of time, for which the historical data is visible in OneView searches, Homepages widgets and related API’s.

Any object that is sent to the data lake is unaffected by this, the timeline history of the object can be archived from OneView but the object, actual data, is untouched.

The archives are stored for an unlimited time. OneView searches and API’s do not see messages in the long-term storage but do see messages after they are restored.

The selected messages for a time window can be temporarily restored if required, see OneView Restore.

The data retention period is affected by the processing status.

There are two statuses:

  • Complete
  • In-flight

The message timeline, which is in-flight, is kept visible in OneView searches and related APIs for a longer retention period. Today, the retention period defaults to 180 days for all documents.

A message is considered being in-flight when it is sent from one component to another and it is not yet delivered there.

The Process Monitor, Workflow, Activation Policies, Alarms, are components on their own. After a message is delivered (Workflow started, monitor triggered, etc.), the message is not in-flight anymore.

If an in-flight message timeline is archived, then it does not prevent ION from working correctly for an action that is in progress. For example the user can still complete any open task or alert, only the timeline details are archived.