Sponsored Content
Full Discussion: Hpux Disk Cloning
Operating Systems HP-UX Hpux Disk Cloning Post 302075739 by eykyn17 on Tuesday 6th of June 2006 01:59:19 PM
Old 06-06-2006
thanks msuluhan i got it
 

10 More Discussions You Might Find Interesting

1. SCO

Disk cloning

Hello everybody, :confused: I have to change the system disk on an old PC running SCO 5.0.5. The disk is up and running, this is a preventive action. My experience on UNIX is very limited and I look for the easyest solution to clone this unit. Is it possible with commands or through a clone... (2 Replies)
Discussion started by: mhachez
2 Replies

2. UNIX for Dummies Questions & Answers

Full System Backup / Cloning HPUX

I am new to UNIX and need help in cloning a HPUX 10.2 Ace 5, can anybody please guide me in making a full system backup. Real Chess (0 Replies)
Discussion started by: real-chess
0 Replies

3. Solaris

Disk cloning using ufsrestore

I am using ufsdump and ufsrestore to clone the root disk on one of my servers. I would like to automate this as much as possible, but have run into a problem where it prompts for changing the owner/mode when it is complete. Any ideas for running this in the background and not being prompted? ... (4 Replies)
Discussion started by: patricko0317
4 Replies

4. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

5. Solaris

Problem by cloning boot disk.

Hello guys! I use the Solaris 10 x86 machine. I need to clone the boot disk. Why, when I copy slice 1 - there is a following: # ufsdump 0f - /dev/rdsk/c0d0s1 | (cd /mnt && ufsrestore rf - ) DUMP: Warning - super-block on device `/dev/rdsk/c0d01` is corrupt - run fsck Dump: The Entire... (6 Replies)
Discussion started by: wolfgang
6 Replies

6. Filesystems, Disks and Memory

Automated disk cloning

Hi, I'm running Ubuntu on my laptop. To keep my data safe and easy disaster recovery as well I bought similar HDD to one installed in my laptop with higher capacity and using USB box I'm doing disk clone to it. So at any time I can replace disk and carry on with my work as before. I'm trying... (2 Replies)
Discussion started by: uvaio
2 Replies

7. HP-UX

Recovering files from unbootable disk in HPUX 9

First of all, forgive me if I come off as naive. Normally I'm doing day-to-day management of a Server 2008 network, so HP-UX isn't exactly my forte. We have several HP 715/100 machines running UX 9.x, and recently one of them stopped being able to boot. In the boot menu the disk shows up with... (3 Replies)
Discussion started by: GoldnPantaloons
3 Replies

8. Ubuntu

dd cloning of whole disk

I am using 'dd' to clone an entire hard drive which only has Ubuntu 11.10 and some data with no special options. The disks are both 1Tb, However, I did re-partition the target disk with gparted successfully. The new partions are not the same size as the source disk. When starting 'dd' no partitions... (24 Replies)
Discussion started by: Royalist
24 Replies

9. Linux

Disk cloning ?

Dear All I needed to clone my disk to another hard drive . I did it as the following : #dd if=/dev/sdb of=/dev/sdc But after a while, the procedure ended with the "writing to /dev/sdc input/output error" message. Can you please let me know how can I overcome this as the fdisk now returns as "... (1 Reply)
Discussion started by: hadimotamedi
1 Replies

10. HP-UX

Unable to add 300gb secondary disk to running 11.11 HPUX system

This has got to be the system from hell. Once again, on the RP4440 (after the supplier replaced the entire box due to the bad RTC battery), finally have it all reloaded with the packages the developers need. The last thing is to add the secondary disk to the OS. BCH sees both OS and secondary... (2 Replies)
Discussion started by: mrmurdock
2 Replies
VOS_CLONE(1)						       AFS Command Reference						      VOS_CLONE(1)

NAME
vos_clone - Creates a shared-space copy of a volume on a partition SYNOPSIS
vos clone [-id] <volume name or ID> [-server] <server name> [-partition] <partition name> [-toname <volume name on destination>] [-toid <volume ID on destination>] [-offline] [-readonly] [-cell <cell name>] [-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve] [-help] vos cl [-i] <volume name or ID> [-s] <server name> [-p] <partition name> [-ton <volume name on destination>] [-toi <volume ID on destination>] [-o] [-r] [-c <cell name>] [-noa] [-l] [-v] [-e] [-nor] [-h] DESCRIPTION
The vos clone command creates a copy-on-write copy of a volume on the same partition and server as the parent volume. A clone is a copy of a volume that only stores the changes from the parent volume. Cloning is a primitive operation that is used by the vos move, vos backup, and vos release commands. A clone functions using the same mechanism as a backup volume, but it is persistent. Clone volumes can be used as point-in-time copies of the parent volume, but they must be used with care. CAUTIONS
This command is not used during normal OpenAFS administration and may have adverse effects on the VLDB if not used properly! This command should only be used by an expert. Deleting or moving the parent volume makes the clone volume inaccessible, but the clone volume remains in the VLDB and on disk, and it needs to be cleaned up manually. There is a maximum limitation of 7 clones when using the namei fileserver. You may safely create up to 4 clones using the vos clone command. The other three clone slots are used by the backup volume, a read-only replica and the temporary clone that is created when executing a vos move, vos dump, or other vos commands. Some commands do not work properly on clone volumes. vos move is one such command. Currently, the maximum size of a volume is 2 terabytes (2^31 bytes). OPTIONS
[-id] <volume name or ID> Specifies either the complete name or volume ID number of a read/write volume. [-server] <machine name> Identifies the file server machine where the source volume resides. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1). [-partition] <partition name> Names the partition where the source volume resides. Provide the full partition name (for, example, /vicepa) or one of the abbreviated forms described in vos(1). -toname <volume name for new copy> The complete name of the new volume to create. -toid <volume id for new copy> The complete id of the new volume to create. -offline Leaves the new volume flagged as off-line in the volume database. -readonly Flags the new volume as read-only in the volume database. -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1). -noauth Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1). -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1). -verbose Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear. -encrypt Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. -noresolve Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
This command has no output unless "-verbose" is specified or there is an error. PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machines specified with the -toserver and -fromserver arguments and on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root". SEE ALSO
vos(1), vos_backup(1), vos_copy(1), vos_move(1), vos_shadow(1) COPYRIGHT
Copyright 2008 Jason Edgecombe <jason@rampaginggeek.com> This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS. OpenAFS 2012-03-26 VOS_CLONE(1)
All times are GMT -4. The time now is 10:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy