Overview
History and audit help users track backup and restore runs and review important actions performed on the Backup Instance by Veeam service.
In the Unify Portal, this group includes two parts:
- History: view backup and restore run history, including manual, scheduled, and hourly runs.
- Activity Log: look up audit logs of operations that change data or state.
Prerequisites
- The tenant has Backup Instance by Veeam service activated.
- The user is logged in to the Unify Portal.
- The user has permission to view the corresponding history or audit log.
- History data is within the VPC or resource scope the user is allowed to access.
History
Purpose
View backup and restore run history in the current VPC, including manual runs from Start manual, automatic runs from scheduled jobs (Daily, Monthly, and Hourly), and restore actions.
Steps
- Open the History screen on the Unify Portal.
- Review the run history list.
- Use the filter to filter by status if needed.
- Use the search to find a record by resource if needed.
- Navigate between pages if the list is long.
Main displayed fields
| Field | Meaning |
|---|
| Resource | Name of the related object or job |
| Action Type | Type of the history record, such as a backup run or a restore action |
| Start Time | Time the run started |
| End Time | Time the run ended |
| Status | Result or status of the run |
Filters and search
| Control | Meaning |
|---|
| Status | Filter by Success, Working, Fail, or Mounted |
| Search | Search by resource |
Notes
- If the list has no data, the portal shows "No history found".
- Hourly schedule runs generate a history record like any other scheduled run.
- Viewing the detail of a single history record is not supported.
- Downloading or exporting the history is not supported.
- If you cannot find the record you expect, check the status filter, the search keyword, and the current VPC.
Activity Log
Purpose
Activity Log audits operations that change data or state on the portal. It is a shared portal logging mechanism, not a backup-specific screen.
Backup operations that typically generate activity logs
| Operation group | Example |
|---|
| Backup Job | Create, update, delete, enable, or disable a backup job |
| Manual/Scheduled Run | Start a manual backup job, or scheduled job runs |
| Restore Point | Delete a restore point or empty restore points |
| Restore | Restore and Restore Keep |
Common fields in activity log
| Field | Meaning |
|---|
| Time | When the log was generated |
| Actor | The user or system that performed the operation |
| Action | The action performed |
| Resource | The affected resource |
| Status | The result of the operation |
| Error | Standardized error information when the operation fails |
How to use
- Open the Activity Log screen or audit log area on the Unify Portal if you have access.
- Filter by time, actor, action, or resource if the portal supports it.
- Open the record to inspect.
- Cross-check the log status with History or the current resource status if needed.
Notes
- Activity Log does not replace History.
- History is used to view backup and restore run results.
- Activity Log is used to audit who did what and when.
- For asynchronous operations, the log may contain multiple checkpoints such as request accepted and completion result.
- Read-only operations may not always have an activity log, depending on the portal audit policy.
History vs Activity Log
| Aspect | History | Activity Log |
|---|
| Purpose | Track backup and restore runs | Audit operations on the portal |
| Main data | Resource, action type, start time, end time, status | Actor, action, resource, status |
| Triggered by system | Yes, for scheduled runs | Sometimes, depending on the action |
| Used to | Verify job success or failure | Trace who did what, and when |
Common errors
| Situation | Resolution |
|---|
| Cannot see history | Check the current VPC, search keyword, status filter, and history view permission |
| Cannot see the most recent run | Wait for data sync or refresh the screen |
| Filter returns no data | Remove some status filters or the search keyword |
| Cannot see activity log of an operation | Check audit log permission and portal logging policy |
| History status and activity log status differ | Compare update times; async operations may log multiple states along the way |