* Reading Current System Information * Selecting System Image To Clone * Selecting Target Disk * The disk "/dev/dsk/c40t0d0" contains data which will be overwritten. * Selecting Volume Manager For New System Image * Analyzing For System Image Cloning * Creating New File Systems * Copying File Systems To New System ImageERROR: Exiting due to hang-up signal. * Unmounting New System Image Clone * System image: "sysimage_001" on disk "/dev/dsk/c40t0d0" * Cleaning up after clone errors. * Copying File Systems To New System Image failed with 1 error.

Re: DRD fail with a hang-up signal

The target's physical disk need not be as large as the disk allocated for the root group, as longas there is enough space for a copy of each logical volume in the root group. However, the diskneeds to be larger than the used space in each logical volume because each logical volume willbe created with the number of physical extents currently allocated to the corresponding rootgroup logical volume.

You can use drd clone with the -p option to get minimal availability information about a disk.

# /opt/drd/bin/drd clone –p –v –t /dev/dsk/cxtxdx

The preview operation includes disk space analysis that shows whether a target disk is largeenough. If you prefer to investigate disk sizes before previewing the clone, you can use thediskinfo command.

I am an HP Employee

Was this post useful? - You may click the KUDOS! star to say thank you.

Re: DRD fail with a hang-up signal

Hi

From running "vgdisplay -v /dev/vg00 | more" I can see that PE size is 32 and Alloc PE is 7521, so roughly 240Gb of space is being used, and my target disk is exactly 250Gb. I beleive this should not be a problem.

* Reading Current System Information * Selecting System Image To Clone * Selecting Target DiskNOTE: There may be LVM 2 volumes configured that will not be recognized.ERROR: Selection of the target disk fails. - Selecting the target disk fails. - Validation of the disk "/dev/dsk/c40t0d0" fails with the following error(s): - The disk "/dev/dsk/c40t0d0" contains data. To overwrite this disk use the option "-x overwrite=true". * Selecting Target Disk failed with 1 error. * DRD operation failed, contents of /var/opt/drd/tmp copied to /var/opt/drd/save.

Re: DRD fail with a hang-up signal

@Nandinho wrote:

I am using ssh putty session that if stays idle for more than 10 minutes losses the connection to the server. Would this be the culprit, causing a kill -1?

As the parent process the PuTTY session, a SIGHUP would be sent to the DRD process, killing it. You could avoid this by starting it with 'nohup' in the background. You could defeat whatever timeout the session enforces too.