02-09-2013
Quote:
Originally Posted by
filosophizer
any other ideas ?
Yes: start over. Obviously what you want is not a clone. A clone is an identical copy - up to the size information. Dukessd has already said it: clone a 10GB-disk and you get another 10GB-disk. What you want is a
different disk with the same content as the original. For this purpose everything "clone" is the wrong tool.
First, use "extendvg" to make the new disk part of the rootvg. Then "mirrorvg" to create copies of the LVs on the new disk. Wait, because this will take some time (depending on the load the system is under and the traffic on the rootvg some minutes to half an hour approximately).
Perform a "bosboot" to create a boot block on the new disk. Then shut down the system. Disconnect the newly created disk and boot again. Correct the errors because of the now missing disk. (Don't forget to correct the bootlist too.)
Start a new system with the cloned disk. You will have to correct the same errors because of the missing mirror disk on the new system. Note that you have an absolutely identical copy of the system - connect both to the same network and you get duplicate IP address errors.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello folks,
I have a sun sparcstation 20, I would like to upgrade one of the hard disks to a larger one. The one I would like to upgrade only contains user data. Here are my thoughts:
1. Backup the specific file system
2. Replace the disk with the larger disk
3. Create a new file... (2 Replies)
Discussion started by: DLongan
2 Replies
2. UNIX Desktop Questions & Answers
could anyone give me a general idea of how i may clone a 2 Gig disk running Solaris 7 on it to another disk of the same size?
currently, this system only has one disk in it though. i do have the ability to hook up another disk via SCSI.
i have been told i need to boot to "miniroot" to run... (9 Replies)
Discussion started by: obosha
9 Replies
3. Solaris
I have just been assigned the task of upgrading to a larger disk on a e250; however, I am use to working on Linux and x86 hardware. I would be very appreciative if someone could inform me on how this procedure can be done safely.
To begin with, the e250 has a 18 Gig primary scsi disk and a 18... (3 Replies)
Discussion started by: cstovall
3 Replies
4. Filesystems, Disks and Memory
Disk cloning
I had an external SCSI master disk that I used to clone to an identical external SCSI disk because the other SCSI disk would become corrupted. My original Master became corrupted so I used one of the other to good disk to copy back to the master. Unfortunately the new master needs... (1 Reply)
Discussion started by: stamperr
1 Replies
5. Solaris
Dear friends & gurus
i have some servers running solaris 10 intel machines,they are in mirror disk 2 disk there is no any hardware RAID only software RAID and they are in remote place.
1) solaris 10 OS c0t0d0(Disk1) & cotod1(Disk2) in mirror (SVM)
2) i want to break the mirror
3) boot... (0 Replies)
Discussion started by: niru
0 Replies
6. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
7. UNIX for Advanced & Expert Users
Guys can anyone tell how can we do faster disk cloning
Below i found in google
1. dd if=/dev/sda of=/dev/sdb bs=4096 conv=noerror,sync
So adding "conv=noerror,sync " makes it faster looks against not adding it
2. Enable write cache activated (hdparm -W1 /dev/sda) then run dd ..
... (2 Replies)
Discussion started by: heman96
2 Replies
8. 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
9. AIX
Hello to all,
Im having a new task in a new world (AIX - IBM Servers)
I have an IBM Server (Type - 9111-285 very old one) with one Hard disk (73 GB 10 K) with AIX 5.x, and I need to clone the existing disk to another with the same specifications.
Could you please give me some advice in order... (7 Replies)
Discussion started by: trevian3969
7 Replies
LEARN ABOUT OSF1
volrecover
volrecover(8) System Manager's Manual volrecover(8)
NAME
volrecover - Performs volume recovery operations
SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...]
OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started
before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera-
tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available
for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5
parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back-
ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will
be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no
other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list
of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name,
the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume.
State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the
recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume.
Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion
status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim-
its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame
operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated
relative to the given disk group.
Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk
group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu-
ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre-
fix:options can be specified to restrict the set of commands that the -o option should be applied to.
Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity
rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes)
Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies
to mirror resynchronization and RAID5 parity recovery
DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes
residing on the named disks (medianame).
If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group).
If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place.
Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that
involve unrelated disks will run in parallel.
EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command:
# volrecover -b medianame
If you want to monitor the operations, use the command:
# volrecover -v medianame
SEE ALSO
volintro(8), volplex(8), volume(8)
volrecover(8)