Vxrestore


 
Thread Tools Search this Thread
Operating Systems HP-UX Vxrestore
# 1  
Old 10-22-2007
Vxrestore

Hi All,

Iam in trouble, hope with all yours contribution, ican solve this VXRESTORE issue.

Iam taking backup of my file system in DLT tape with the help of
#vxdump -0 -u -f /dev/rmt/0mn<file system> . It is done successfully , I can view the files which is backup on tapes with the help of #vxrestore -i

But the problem is iam unable to restore it back with the help of #add <ex.unix> then #extract.

The messages iam getting :
vxrestore:wrong volume(1)
vxresotre:you have not read any tapes yet unless you know which volume your file(s) are on you should start with the last volume and work towards the first.

Please help me to vxrestore my selected file in the different or same location of the file system with DLT backup.

I appreciate your valuable help .
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
device_maps(4)							   File Formats 						    device_maps(4)

NAME
device_maps - device_maps file SYNOPSIS
/etc/security/device_maps DESCRIPTION
The device_maps file contains access control information about each physical device. Each device is represented by a one line entry of the form: device-name : device-type : device-list : where device-name This is an arbitrary ASCII string naming the physical device. This field contains no embedded white space or non-printable characters. device-type This is an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices of like type. This field contains no embedded white space or non-printable characters. device-list This is a list of the device special files associated with the physical device. This field contains valid device special file path names separated by white space. The device_maps file is an ASCII file that resides in the /etc/security directory. Lines in device_maps can end with a `' to continue an entry on the next line. Comments may also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'. Leading and trailing blanks are allowed in any of the fields. The device_maps file must be created by the system administrator before device allocation is enabled. This file is owned by root, with a group of sys, and a mode of 0644. EXAMPLES
Example 1 A Sample device_maps File The following is a sample device_maps file: # scsi tape st1: rmt: /dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 /dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m /dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn /dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn: FILES
/etc/security/device_maps Contains access control information for devices. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
allocate(1), bsmconv(1M), deallocate(1), list_devices(1), dminfo(1M), device_allocate(4), attributes(5) NOTES
The functionality described in this man page is available only if Solaris Auditing has been enabled. See bsmconv(1M) for more information. On systems configured with Trusted Extensions, the functionality is enabled by default. On such systems, the device_allocate(4) file is updated automatically by the system. SunOS 5.11 30 Apr 2008 device_maps(4)