Veritas NetBackup™ Snapshot Client Administrator's Guide
- Snapshot Client features
- About snapshot basics
- Off-host backup overview
- Off-host backup methods
- About alternate client backup
- Snapshot Client requirements
- Policy configuration
- Selecting the snapshot method
- Configuration parameters for Snapshot Client
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- About configuring VxVM
- About storage lifecycle policies for snapshots
- Network Attached Storage (NAS) snapshot configuration
- Configuration of software-based snapshot methods
- Software-based snapshot methods
- Cache device requirements
- About VxFS_Checkpoint
- About VxVM
- About FlashSnap
- About VVR
- About VSS
- Software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- About the new disk array snapshot methods
- Disk array configuration tasks
- OS-specific configuration tasks
- About VSS configuration (Windows)
- About EMC CLARiiON arrays
- Configuring NetBackup to access the CLARiiON array
- Configuring a NetBackup policy for a CLARiiON array method
- About EMC Symmetrix arrays
- About configuration for EMC_TimeFinder_Mirror
- About configuration for EMC_TimeFinder_Clone
- About HP EVA arrays
- Verifying connectivity from clients to array using SSSU 5.0
- About IBM DS6000 and DS8000 arrays
- Configuring NetBackup to access the IBM DS6000 or DS8000 array
- About IBM DS4000 array
- About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
- Hitachi array software requirements
- About HP-XP arrays
- About array troubleshooting
- Troubleshooting issues pertaining to all arrays
- Troubleshooting IBM DS6000 and DS8000 arrays
- Troubleshooting IBM4000 arrays
- Troubleshooting Hitachi arrays
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- About restores from a FlashBackup backup
- Instant Recovery restore features
- About Instant Recovery: block-level restore
- About Instant Recovery: file promotion
- About Instant Recovery: Fast File Resync (Windows clients only)
- About Instant Recovery: point in time rollback
- About configurations for restore
- About restoring from a disk snapshot
- Logging directories for UNIX platforms
- Logging folders for Windows platforms
- FlashBackup and status code 13
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
- Appendix C. NetBackup integration with CloudPoint for snapshot managment
Except as noted in this topic, you can also use the Logging Assistant (in the NetBackup Administration Console) to configure VxMS logging. For details on the Logging Assistant, see the NetBackup Administrator's Guide, Volume I.
- Create the VxMS log directory:
For logging to occur, the VxMS folder must exist.
If you have run the NetBackup mklogdir.bat command, the VxMS log directory already exists.
- In the Windows registry, create the DWORD registry entry
VXMS_VERBOSEin the following location:
HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion > Config
- To configure the logging level, set the numeric value of
VXMS_VERBOSEto 0 or greater. Larger numbers result in more verbose logs.
See Table: VxMS logging levels for the available logging levels.
- To change the log location:
Open regedit and go to the following location:
HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion
Create the registry entry
vxmslogdirwith a string value
(REG_SZ). For the string value, specify the full path to an existing folder.
You can use NTFS compression on VxMS log folders to compress the log size. The new logs are written in compressed form only.
If the VxMS log location is changed, the Logging Assistant does not collect the logs.
Table: VxMS logging levels lists the VxMS logging levels.
Logging levels higher than 5 cannot be set in the Logging Assistant.
Logging levels higher than 5 should be used in very unusual cases only. At that level, the log files and metadata dumps may place significant demands on disk space and host performance.
Table: VxMS logging levels
Level 1 + warning messages.
Level 2 + informative messages.
Same as level 3.
Highly verbose (includes level 1) + auxiliary evidence files (.mmf, .dump, VDDK logs, .xml, .rvpmem).
You can set the logging level for the VDDK messages.
VIX (VMware virtual machine metadata) dumps only.
VHD (Hyper-V virtual machine metadata) dumps only.
Full verbose + level 5 + level 6 + level 7.