Displaying and Customizing Reports : Viewing storage reports : Viewing the Backups report
  
Viewing the Backups report
The Backups report summarizes the status of the last backups (up to five), organized by Edge and server. VMs are listed under each server, and you can expand each VM to view its backup history.
What this report tells you
The Backups report answers these questions:
•  What is the status of the last five backups on a specific Edge, server, or VM?
•  Which Edges, VMs, or servers have backup policies?
•  Which backups have failed? Which backup failed most recently?
To display the Backups report
1. Choose Reports > Data Protection: Backups to display the Backups page.
You can also access the Backups page from the Dashboard by clicking More in the Backups pane.
At the Edge level, the Status column displays a roll-up summary of all Edges.
Figure: Backups report page
2. Click the right arrow next to the Edge to view its associated servers, and then click the right arrow next to a server to view its VMs.
The Status column displays a roll-up summary of the Edges and VMs, depending on the current level.
3. Click the right arrow next to the VM to view the backup report details.
To perform a search at the VM level, use the search field (identified by the magnifying glass icon). Start typing a VM name to narrow down the view to a particular VM. Any matching results are displayed dynamically in the table.
Figure: Backups report page
Viewing the report details
This table summarizes the information shown in the Backups report.
Status
Description
Last Status
The last status of the backup policy. The status details vary, depending on whether you select an Edge, server, or VM.
•  Succeeded - The last time the backup policy was executed, it completed successfully with no errors. A caution icon (exclamation point) next to the Succeeded message indicates that although the status shows as Succeeded, one or more of the last five backups has failed. Expand the backup policy to view the details.
•  Partially Succeeded - One or more of the configured backups has failed.
•  Failed - All of the configured backups have failed. There are several possible reasons for this failure:
•  Unable to connect to proxy server.
•  Unable to take snapshot on storage.
•  Unable to mount the datastore.
•  Unable to register the VMs.
•  Not Configured - This Edge or server isn’t included in any backup policy.
•  Never Succeeded - This backup policy has never been executed correctly.
•  No Operations Completed - This backup policy has not been triggered yet.
•  No VMs detected for this server - No VMs have been detected for this backup policy.
•  No Servers detected for this Edge - No servers have been detected for this Edge.
Last Successful
The date and time of the last successful backup.
Status
Any success or failure messages related to the policy (if the Edge isn’t expanded). Some sample status messages include:
•  All recent backups succeeded.
•  All recent backups succeeded on all VMs.
•  All recent backups succeeded on all servers.
•  The first scheduled backup for any VM on this Edge has not yet completed.
•  The first scheduled backup for any VM on this server has not yet completed.
Backup Policy Details
Expand a VM to view its backup policy details:
•  Backup Policy - The name of the current backup policy.
•  Most Current Protection - The date and time of the last successful backup.
•  History - The number of backups that have reached the Core (up to five are displayed), and their details. If Core has returned from a WAN outage, protection operations triggered during that time are displayed as Skipped.
•  Backup Proxy - The IP address of the VMware ESXi server used in this backup policy.
•  Backup Schedule - The currently configured backup schedule.
Note: In an Edge high availability (HA) setup, if a protection operation is triggered on a backup policy on the active Edge, and an Edge HA failover occurs within approximately 30 seconds of triggering it, the protection operation will fail with the error “Nothing to Protect.” The protection operation will succeed the next time it is triggered.