09-20-2013
Quote:
Originally Posted by
abhishekdave
Hello,
Thanks and appreciate you response.
Actually, i am very new to this platform and someone told me to do this task
From Node1
1) create a VG with 1 or more LV
2) create a file system on this vg.
3) varyoff vg1
4) exportvg hdisk31
Now from node1
1) importvg hdisk5
2) varyonvg vg1
As disk is shared among node1 and node2.
I am unable to do that.
For systems which don't have shared disk. I have to do below things
From Node1,
1) use dd to copy whole image ( ~10G) of hdisk31
2) restore on node3 using dd of same size disk.
3) Now, importvg hdisk?
4) Now, ensure vg and lv is available.
5) now, mount file system
am i missing any thing.
We don't have any backup thing. we want to back of dd image only.
Thank in advance.
You are confusing me here, what are you trying to do?
You are saying for system you don't have shared disk you are importing the disk. How come you import a disk? what is the point of importing a disk when it is not shared?
Look, simple approach is use the savevg and restvg.
6 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I have been restoring from tape some old data. I have done quite a few tapes and have had no problems until now.
The command I am running is "dd if=/dev/rmt/1hbn bs=1024 | tar -pBxF - ".
This is the second tape have have come up with the error "Not enough space". This tape has a couple of... (1 Reply)
Discussion started by: mtoombs
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
i am a real dummy to unix and in need of help.My platform is Sun solaris(5.9)
I have a dump file, an oracle cold backup taken with ufsdump command. This dump file resides on the disk, not the tape.
I want to extract this dump file to a directory. But i cant, i read about ufsrestore... (1 Reply)
Discussion started by: merope
1 Replies
3. Solaris
I tried to use zfs .. only for test ..so when I take my test disks into zfs pool their VTOC changed .. and 7th slice does not appear now. How can I restore default VTOC to my disks.
my machine is x86 .. SunFire X4200 .. so this disks do not have slices like sparc machines .. they have... (6 Replies)
Discussion started by: samar
6 Replies
4. AIX
Hi all,
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
5. UNIX for Advanced & Expert Users
Hi guys,
I would like to ask your opinion about my theory, how to fix my broken LVM without risking any data loss.
I use Archlinux at home. I just love this distro, even it gives me a lots of work (particularly after system updates).
Basic system spec:
AMD FX(tm)-6100 Six-Core Processor... (1 Reply)
Discussion started by: lyynxxx
1 Replies
6. HP-UX
Our new rx2800 server is running HP-UX 11iV3. We have a cron script to perform an fbackup to a file on disk nightly. Now I'm trying to do a test restore, but I can't seem to find the correct way to specify the backup file as the source in frecover. Can anyone point me in the right direction?
... (5 Replies)
Discussion started by: jduehmig
5 Replies
LEARN ABOUT OSF1
disklabel
disklabel(4) Kernel Interfaces Manual disklabel(4)
NAME
disklabel - Disk pack label
SYNOPSIS
#include <sys/disklabel.h>
DESCRIPTION
Each disk or disk pack on a system may contain a disk label which provides detailed information about the geometry of the disk and the par-
titions into which the disk is divided. It should be initialized when the disk is formatted, and may be changed later with the disklabel
program. This information is used by the system disk driver and by the bootstrap program to determine how to program the drive and where
to find the file systems on the disk partitions. Additional information is used by the file system in order to use the disk most effi-
ciently and to locate important file system information. The description of each partition contains an identifier for the partition type
(standard file system, swap area, etc.). The file system updates the in-core copy of the label if it contains incomplete information about
the file system.
The label is located in sector number LABELSECTOR of the drive, usually sector 0 (zero) where it may be found without any information about
the disk geometry. It is at an offset LABELOFFSET from the beginning of the sector, to allow room for the initial bootstrap. The disk
sector containing the label is normally made read-only so that it is not accidentally overwritten by pack-to-pack copies or swap opera-
tions; the DIOCWLABEL ioctl, which is done as needed by the disklabel program, allows modification of the label sector.
A copy of the in-core label for a disk can be obtained with the DIOCGDINFO ioctl; this works with a file descriptor for a block or charac-
ter (raw) device for any partition of the disk. The in-core copy of the label is set by the DIOCSDINFO ioctl. The offset of a partition
cannot generally be changed, nor made smaller while it is open. One exception is that any change is allowed if no label was found on the
disk, and the driver was able to construct only a skeletal label without partition information. Finally, the DIOCWDINFO ioctl operation
sets the in-core label and then updates the on-disk label; there must be an existing label on the disk for this operation to succeed.
Thus, the initial label for a disk or disk pack must be installed by writing to the raw disk. All of these operations are normally done
using the disklabel program.
RELATED INFORMATION
Files: disktab(4)
Commands: disklabel(8) delim off
disklabel(4)