Overview
History and audit help users track backup job runs and review important actions performed on the Backup Instance by Veeam service.
In the Unify Portal, this group includes two parts:
- Job History: view backup job run history, including manual and scheduled 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.
Job History
Purpose
View backup job run history in the current VPC, including manual runs from Start Manual Backup Job and automatic runs from Auto Scheduled Backup Job.
Steps
- Open the Job History screen on the Unify Portal.
- Review the job run history list.
- Use the filter to filter by status if needed.
- Use the search by Job Name if needed.
- Navigate between pages if the list is long.
Main displayed fields
| Field | Meaning |
|---|
| Object Name | Name of the related object or job |
| Type | Type of history record |
| Start Time | Time the job started |
| End Time | Time the job ended |
| Status | Result or status of the run |
Common filters
| Filter | Meaning |
|---|
| Status | Filter by Success, Working, Fail, or Mounted |
| Keyword | Search by Job Name |
Notes
- If the list has no data, the portal may show "No job history found".
- Version 1.5 does not support viewing the details of a Job History record.
- Version 1.5 does not support downloading or exporting Job History.
- If you cannot find the record you expect, check the status filter, 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, disable backup job |
| Manual/Scheduled Run | Start manual backup job, scheduled job runs |
| Restore Point | Empty restore point or other side-effect restore point operations |
| Restore | Restore, Restore Keep, Instant Recovery if the system records them per audit standard |
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 | Normalized 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 Job History or the current resource status if needed.
Notes
- Activity Log does not replace Job History.
- Job History is used to view backup job 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.
Job History vs Activity Log
| Aspect | Job History | Activity Log |
|---|
| Purpose | Track backup job runs | Audit operations on the portal |
| Main data | Object name, 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 job history | Check the current VPC, keyword, status filter, and Job 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 keywords |
| 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 |