Veritas NetBackup™ 8.0 for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Configure NetBackup policies for VMware
- VMware backup options
- Configure a VMware Intelligent Policy
- Reduce the size of backups
- Back up virtual machines
- Use Accelerator to back up virtual machines
- Restore virtual machines
- Restoring the full VMware virtual machine
- Virtual Machine Recovery dialog boxes (restore to original location)
- Virtual Machine Recovery dialogs boxes (restore to alternate location)
- Restoring VMware virtual machine disks
- Restoring individual files
- Browse and search virtual machines for restore
- Restore virtual machines with Instant Recovery
- Use NetBackup for vCloud Director
- Virtual machine recovery dialog boxes for vCloud Director
- Best practices and more information
- Troubleshooting
- Appendix A. NetBackup commands to back up and restore virtual machines
- Using NetBackup commands to create a VMware policy
- Appendix B. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 (NetBackup for VMware)
- About configuring services for NFS on Windows 2008 and 2008 R2 (NetBackup for VMware)
- About configuring Services for Network File System (NFS) on the Windows 2003 R2 SP2 NetBackup media server and NetBackup clients (NetBackup for VMware)
- Appendix C. The Reuse VM selection query results option
- Appendix D. Backup of VMware raw devices (RDM)
- Appendix E. SYMCquiesce utility for Linux virtual machines
SYMCquiesce logging and troubleshooting
This topic applies to NetBackup for VMware.
SYMCquiesce logs indicate whether quiescence of the Linux virtual machine volumes was successful. SYMCquiesce logs are written to /opt/SYMCquiesce/logs
. Logging is enabled by default (no configuration step is required) and cannot be disabled.
Log file names are of the form mmddyy.log
. When a backup runs, a new log is created if one does not already exist for that date. A backup that runs on the 22nd of October 2010 creates a log named 102210.log
.
An example from a SYMCquiesce log:
Stats - Thu Oct 28 18:51:58 2010 Freeze of volume [/] returned status [0] Thaw of volume [/] returned status [0] Freeze of volume [/boot] returned status [0] Thaw of volume [/boot] returned status [0]
Where:
Stats
: shows the time of the log entry when volumes where being quiesced.
status [0]
: no error. The freeze (or thaw) completed successfully.
status [-1]
: error. The freeze operation or the thaw operation did not complete successfully.
If the freeze (and the thaw) completed successfully, the volume was successfully quiesced.
Note the following:
You can use the logs with the
fail_snapshot_on_failure
option in /opt/SYMCquiesce/config file. If that option is enabled and snapshots fail, consult the SYMCquiesce logs to see which volume's quiescence fails.If the virtual machine has both ext2 and ext3 volumes (or ext2 and ext4), and the
fail_snapshot_on_failure
option is enabled, the snapshot fails. ext2 file systems do not support quiescence. You must disable thefail_snapshot_on_failure
option to get a successful snapshot of the volumes. Note however that the ext2 volume cannot be quiesced: Any data changes that have not been flushed to disk are not included in the snapshot.