User manual QUANTUM ESXPRESS 3.6 BACKUP REPORTS GUIDE REV A

[. . . ] COPYRIGHT STATEMENT Copyright 2010 by Quantum Corporation. Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law. [. . . ] Refer to the GUI Appliance Guide or the Reference manual for details. The remaining sections in this guide describe the esXpress backup reports in detail. Quantum esXpress Backup Reports Guide 5 Chapter 1: Introduction 6 Quantum esXpress Backup Reports Guide Chapter 2: Backup Status Reports 2 Backup Status Reports The daily backup status report contains information about all of the VMs backed up in the last backup window. The report would have been emailed with the subject line containing "All Good" because all backups completed without error. Other email subject lines could consist of "Warnings today" or "Errors Today. " "Warnings Today" indicates that during the backup job, something occurred, but all VMs were backed up. This may happen if the target was rebooted during backups or some backups timed out and had to be retried. The reason for the warning can be found in the logs. "Errors Today" indicates that at least one VM did not backup properly. There are many reasons for this, and a review of the logs is required in order to find the cause. Sorted Backup Status The status report shows an alphabetical list of all VMs backed up along with the information from the first report. This makes it easier to see the events surrounding the VMDK backups of a single VM. Had there been warnings or errors in by nightly backup as indicated by a status of 'Errors Today' or 'Warnings Today, ' a summary of all errors or warnings would appear next in the logs. The following example shows the first part of the log. This is a common point of failure--if the VMDK is a raw RDM or a VMDK in independent mode, snapshots cannot be taken and the backup will fail. If esXpress detects another snapshot and Snapshot on Snapshot is not enabled, backup of the VM will also fail. If esXpress detects its own snapshot was left hanging from a previous backup, esXpress will clean up old esXpress snapshots before starting the backup. Note that esXpress will also detect hanging snapshots from other backup products, but will not commit them nor will it continue with a backup if the snapshots were not left in a clean state. 2009-10-02 11:33:37. 952 2009-10-02 11:33:37. 955 2009-10-02 11:33:37. 958 2009-10-02 11:33:37. 961 2009-10-02 11:33:37. 964 2009-10-02 11:33:37. 966 2009-10-02 11:33:37. 969 2009-10-02 11:33:37. 972 04:24s ON, : 2009-10-02 11:33:38. 080 2009-10-02 11:33:38. 611 Folder Name: DisplayName: VMX UUID : VMX GuestOS: VMX Version: ESX Version: Annotation : /vmfs/volumes/Storage1/2003/PHDTerm. vmx - ON PHDTerm 564d832e-8822-f12e-1b0c-39913c94db7f winnetstandard 4 VMware ESX 4. 0. 0 build-164009 _esXpress: 2009-10-01 22:14 - OK - 1/1/1 disks, (2. 4%) 290m/12g/12g (98% Data), DISK 1 = scsi0:0. fileName = /Storage1/2003/PHDTerm. vmdk Helper License OK, Starting Helper for VM '2003' Next, esXpress reads the VMX file for the VM. The state of the VM in this example is `ON. ' esXpress by default will not backup VMs that are powered off. [. . . ] Next, 100MB of the VMDK are read and timed. This gives a preview as to how quickly the LUN/Disk being backed up can deliver data. In this example the disk can deliver data at 50MB/sec. [. . . ]