10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies
2. Shell Programming and Scripting
Hello,
I would like to make a script that searches through a SRC folder and copies only files it's never seen before to a DEST folder.
SRC = /user/.phonesync/photos-backup
DST = /usr/.phonesync/photos-new
So basically, I'd start with a:
md5sum /user/.phonesync/photos-backup/* >... (29 Replies)
Discussion started by: nbsparks
29 Replies
3. Shell Programming and Scripting
When script is running you only see when some of the commands are not successfull.
Is there a way to see which command are executed and to show the substitution of variables as every line is executed ? (3 Replies)
Discussion started by: gr0124
3 Replies
4. UNIX for Advanced & Expert Users
I am trying to list the name of files on an MOD - I use the command
tar vtf /MOD_DRIVE|more
and I get a nice list of filenames/directories on this particular MOD. When I put in another MOD that contains software options I get the error "directory checksum error". I would like to be able to... (2 Replies)
Discussion started by: drew_holm
2 Replies
5. UNIX for Dummies Questions & Answers
I have found a question from the exercises of my study mat. The question is
"Why are there a in-core copy and a disk-copy of i-node block and super block?"
If any one know the proper answer then please send me..... (1 Reply)
Discussion started by: dearanik
1 Replies
6. Solaris
Hi,
i have problems with my system disk (os solaris 5.10) and i'm wondering if there is any way to copy the whole disk to a new one, without reinstalling everything (so to do a mirroring)??
thanks in advance (3 Replies)
Discussion started by: sprehodec
3 Replies
7. UNIX for Dummies Questions & Answers
i am novice in unix. in me office my boss hav given me a system with Unix OS. i know about windows and Dos. in dos we access cd or floppy through writing following commands a: or d: copy filename.ext to a:
i dont even now how to access CD Rom or floppy drive in unix. please tell... (1 Reply)
Discussion started by: fassi
1 Replies
8. Solaris
Hi
how do u make "copy" of o level dump taken via ufsdumo in solaris?
To elaborate, imagine you have taken a 0 level dump via the following command
ufsdump 0ulf /dev/rmt/1n /
and then again execute the same command to take a second 0 level dump
Now take an incremental dump
ufsdump 1ulf... (2 Replies)
Discussion started by: vishalsngh
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160).
During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Discussion started by: yurist
2 Replies
10. UNIX for Dummies Questions & Answers
I do not have a Unix machine, i do have a Linux machine.. i have a Unix boot disk that is essencial to my unit. Is there any way in Windows98 or Linux to make copies of this disk. So far i can't get either to read the disk. (1 Reply)
Discussion started by: deathsfriend
1 Replies
vxdarestore(1M) vxdarestore(1M)
NAME
vxdarestore - restore simple or nopriv disk access records
SYNOPSIS
/etc/vx/bin/vxdarestore
DESCRIPTION
The vxdarestore utility is used to restore persistent simple or nopriv disk access (da) records that have failed due to changing the naming
scheme used by vxconfigd from c#t#d#-based to enclosure-based.
The use of vxdarestore is required if you use the vxdiskadm command to change from the c#t#d#-based to the enclosure-based naming scheme.
As a result, some existing persistent simple or nopriv disks go into the "error" state and the VxVM objects on those disks fail.
vxdarestore may be used to restore the disk access records that have failed. The utility also recovers the VxVM objects on the failed disk
access records.
Note: vxdarestore may only be run when vxconfigd is using the enclosure-based naming scheme.
Note: You can use the command vxdisk list da_name to discover whether a disk access record is persistent. The record is non-persistent if
the flags field includes the flag autoconfig; otherwise it is persistent.
The following sections describe how to use the vxdarestore utility under various conditions.
Persistent Simple/Nopriv Disks in the rootdg Disk Group
If all persistent simple or nopriv disks in the rootdg disk group go into the "error" state, use the following procedure:
1. Use the vxdiskadm command to change back to the c#t#d# based naming scheme.
2. Either shut down and reboot the host, or run the following command:
vxconfigd -kr reset
3. If you want to use the enclosure-based naming scheme, add a non-persistent simple disk to the rootdg disk group, use vxdiskadm to
change to the enclosure-based naming scheme, and then run vxdarestore.
Note: If not all the disks in rootdg go into the error state, simply running vxdarestore restores those disks in the error state and the
objects that that they contain.
Persistent Simple/Nopriv Disks in Disk Groups other than rootdg
If all disk access records in an imported disk group consist only of persistent simple and/or nopriv disks, the disk group is put in the
"online dgdisabled" state after changing to the enclosure-based naming scheme. For such disk groups, perform the following steps:
1. Deport the disk group using the following command:
vxdg deport diskgroup
2. Run the vxdarestore command.
3. Re-import the disk group using the following command:
vxdg import diskgroup
NOTES
Use of the vxdarestore command is not required in the following cases:
o If there are no persistent simple or nopriv disk access records on an HP-UX host.
o If all devices on which simple or nopriv disks are present are not automatically configurable by VxVM. For example, third-party
drivers export devices that are not automatically configured by VxVM. VxVM objects on simple/nopriv disks created from such disks
are not affected by switching to the enclosure based naming scheme.
The vxdarestore command does not handle the following cases:
o If the enclosure-based naming scheme is in use and the vxdmpadm command is used to change the name of an enclosure, the disk access
names of all devices in that enclosure are also changed. As a result, any persistent simple/nopriv disks in the enclosure are put
into the "error" state, and VxVM objects configured on those disks fail.
o If the enclosure-based naming scheme is in use and the system is rebooted after making hardware configuration changes to the host.
This may change the disk access names and cause some persistent simple/nopriv disks to be put into the "error" state.
o If the enclosure-based naming scheme is in use, the device discovery layer claims some disks under the JBOD category, and the vxdd-
ladm rmjbod command is used to remove remove support for the JBOD category for disks from a particular vendor. As a result of the
consequent name change, disks with persistent disk access records are put into the "error" state, and VxVM objects configured on
those disks fail.
EXIT CODES
A zero exit status is returned if the operation is successful or if no actions were necessary. An exit status of 1 is returned if vxdare-
store is run while vxconfigd is using the c#t#d# naming scheme. An exit status of 2 is returned if vxconfigd is not running.
SEE ALSO
vxconfigd(1M), vxdg(1M), vxdisk(1M), vxdiskadm(1M), vxdmpadm(1M), vxintro(1M), vxreattach(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdarestore(1M)