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
snaplist shows the amount of client write activity that occurred during an nbu_snap snapshot. Information is displayed for all snapshots that are currently active.
Execute this command as root:
Information is displayed in the following form:
id ident size cached minblk err time 9 6730 2097152 2560 0 0 05/29/03 07:52:18 device = /dev/vx/rdsk/omaha/tcp1 cache = /dev/vx/rdsk/omaha/sncache 16 7857 2097152 128 0 0 05/29/03 12:16:00 device = /dev/vx/rdsk/omaha/vol01 cache = /dev/vx/rdsk/omaha/sncache 17 7908 20971520 4224 0 0 05/29/03 12:17:38 device = /dev/vx/rdsk/omaha/vol03 cache = /dev/vx/rdsk/zetab/cache
If no snapshots are currently active, no output is returned.
Description of output:
The snapshot ID. The snapoff command uses this ID to terminate the snapshot.
A unique numeric identifier of the snapshot. ident is the pid of the process that created the snapshot.
The size of the client's snapshot source in 512-byte blocks. The snapshot source is the partition on which the client's file system (the file system being backed up) is mounted.
size is not a reliable guide to the size of the cache that is needed for the snapshot. The user write activity during the snapshot is what determines the size of the cache needed. See the cached column of this output.
The number of 512-byte blocks in the client file system that were changed by user activity while the snapshot was active. Before being changed, these blocks were copied to the cache partition. The more blocks that are cached as a result of user activity, the larger the cache partition required. However, additional overhead - which is not shown in this cached value - is required in the cache. To see the total space that is used in a particular cache partition, use the snapcachelist command.
In the partition on which the file system is mounted, minblk shows: the lowest numbered block that is monitored for write activity while the snapshot is active. Only FlashBackup policies use minblk.
An error code; 0 indicates no error. If a snapshot has encountered an error, the err is non-zero and the snapshot is inaccessible. It can be terminated using snapoff and the snapshot ID. Error codes are identified in /usr/include/sys/errno.h. Also, error messages may be found in /var/adm/messages.
The time at which the snapshot was started.
The raw partition containing the client's file system data to back up (snapshot source).
The raw partition used as cache by the copy-on-write snapshot process. Make sure that this partition is large enough to store all the blocks likely to be changed by user activity during the backup.
To determine the total space that is used in a particular cache partition by all active snapshots, use the snapcachelist command.