Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- About the capacity licensing model
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
About reading backup images with nbtar or tar32.exe
NetBackup uses tar-formatted backup images. By using the NetBackup tar32.exe on Windows or nbtar on UNIX or Linux, NetBackup can understand compressed files, sparse files, long pathnames, and ACL information. It offers features similar to those in cpio.
Although non-NetBackup restore utilities that process tar-formatted images can be used to restore files, they provide only limited restore capabilities. You cannot use the NetBackup tar32.exe or nbtar to extract files from a NetBackup for Windows backup image.
Non-NetBackup restore utilities do not supply all of the restore capabilities that the NetBackup /usr/openv/netbackup/bin/nbtar provides. Possible problems result.
The following is a list of consequences that can occur if using non-NetBackup restore utilities:
Non-NetBackup versions of restore utilities may have trouble with sparse files and often skip sparse files.
HP CDFs are restored with non-NetBackup versions of restore utilities. The directory is no longer hidden and the name of the directory has a + appended to it.
If the backup spans more than one piece of media, you must read and combine the fragments from the media to give to the restore utility. To combine the fragments, the system's dd command may be useful.
Another possibility is to use a restore utility on the fragments. To use a restore utility on fragments can allow recovery of any file in the backup other than the one that spanned the media.
Some versions of the HP9000-800 /bin/tar command are known to give a directory checksum error for the second fragment of a backup that crossed media.
Some versions of Solaris tar combine the atime, mtime, and ctime strings with the file name and create the file paths that are not desirable.