Sponsored Content
Full Discussion: HP-UX server cloning
Operating Systems HP-UX HP-UX server cloning Post 302597127 by vbe on Thursday 9th of February 2012 09:10:51 AM
Old 02-09-2012
Are your disks identical?
If strictly identical, there is an option you should try: vgreduce or split the mirror to have only one disk in vg00 then do a dd...
It should boot...
dont forget to turn off the VG_AUTO_ACTIVATE for vg01... for you will need to import the correct definition of the VG (dont know how you will do that though for SAN is not the same...)
My 2 cents:
I would go and boot the system, that will complain (duplicate address) so try to boot single user modify all that is need, ( /etc/lvmtab, fstab etc...) give a new IP and get your network team to create a VLAN so you can use it even if you are the only node in that sublan...
Once OK, activate you mirroring...
Now add vg01 (pvcreate etc...) and create all lvm as on the original.
Either copy or restore (if you backup utility will do such tasks...).
All this should be done at init level2 to be safe with no fancy unwanted overhead.

this sort of manipulation were my daily routine one time, but long, long ago...
An L3000 had at configuration/order time an option at order: you could choose a tape drive OR a DVD internal... If you wanted both you had to choose which device was external.. I had both and believe the internal tape was the best choice...

P.S.
I did also use the mirror, but had some much issues I gave up... the best of all is by far the Ignite tape, since you can start almost a fresh "install" and configure the new box immediately by giving his new name , IP etc...
Ever considered Ignite via LAN?
This User Gave Thanks to vbe For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Aix Cloning

Is there anyone out there who knows anything about aix cloning? I would be very grateful for any information at all. Thanking you in advance :) (4 Replies)
Discussion started by: annette
4 Replies

2. Filesystems, Disks and Memory

Unix Cloning

I'm looking for software that can clone Unix Partitions. (2 Replies)
Discussion started by: jimv2502893
2 Replies

3. 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

4. UNIX for Dummies Questions & Answers

HP10.20 Cloning

Good day all. So, here's the situation. I have (7x) B180L VISUALIZE WORKSTATION's with Transtec 5100 RAID (RAID 5, 9.1 GB HDD's) towers running of UNIX HP10.20. It's time to replace the RAID's with new ones, them being Fibrenetix FX606 5 bay SATA RAID, 5 bay SATA-SCSI desktop RAID including 80Gb... (1 Reply)
Discussion started by: Tony_dw
1 Replies

5. Red Hat

cloning a server

I wish to clone a RedHat EL5 server. What's the easiest way to do this? Thanks :) (4 Replies)
Discussion started by: wazzu62
4 Replies

6. Shell Programming and Scripting

Cloning

Hi, Is there disadvantages if we do AIX Serevr cloning to the new AIX server. Thanks in advance (0 Replies)
Discussion started by: kmsekhar
0 Replies

7. AIX

AIX Server Cloning

Hi, Is there disadvantages if we do AIX Serevr cloning to the new AIX server. Thanks in advance (2 Replies)
Discussion started by: kmsekhar
2 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
set_parms(1M)															     set_parms(1M)

NAME
set_parms - set system initial identity parameters: hostname, date/time, root password, and networking SYNOPSIS
DESCRIPTION
The command is an interactive system set-up command that allows you to specify various "initial identity parameters" when first booting a newly installed operating system (whether preinstalled, or installed locally from media or an install server), and to revise these parame- ters later on a running system. Initial identity parameters are a minimal set of values required to bring a system to an initially useful state. They include the following: o system hostname o timezone for the system's location o date and time o root password o IP address, netmask o routemask, routing gateway, DNS, and NIS information o local language In a first-boot situation, is invoked automatically by For purposes, "first-boot" is defined as having no hostname set when the system starts up. This causes to step through all of its sub-areas to help you set all of the initial identity parameters. After the system has booted and is running, may also be called directly from the command line to step through all areas (via similar to how it works at first-boot, or to finish setting up a particular sub-area (the latter forms above). There are certain limitations to its actions when it's run after first-boot, as described see below. Note: The command only sets the root (superuser) password during "initial" processing, and then only if it is not already set. If so, it uses the command, so the effect is immediate. See the passwd(1) manpage. The command is also DHCP-aware. If you attempt to change DHCP-supplied data such as the hostname or IP address, issues a warning. If you continue with the changes, relinquishes the DHCP lease. On first-boot, asks if you would like to try getting set-up data from a DHCP server. However invoked, the command often knows and provides default values for many of the initial identity parameters, based on values specified to Ignite-UX in a previous or recent installation of the system or found in system configuration files. The command can be run only by the user with appropriate privilege. Options Each sub-area of is described below. In a first-boot situation all of the sub-areas are run sequentially. Special first-boot behavior is noted below if applicable, along with any special cases when invoking on a running system. When calling a sub-area directly, only a unique portion of the sub-area name is required to be given; for example, This allows the user to sequentially invoke all the sub-areas mentioned below. The user can configure multiple interfaces which are physically connected to the network using the Termi- nal User Interface (TUI). A in the user interface field indicates a lan which is not physically connected to the network. If lan interfaces are configured as DHCP, the options and are skipped. Set the system hostname: Validates a user-supplied hostname according to host-naming conventions and sets various system initialization variables to operate with that hostname. Particularly, edits to associate the new hostname with the current IP address of the system, if that can be determined. Note: It does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. WARNING: When changing the hostname, does not know about optionally-installed software. If any such software remembers the previous hostname, it might not work properly after the hostname is changed. A mechanism is provided that helps generalize the hostname changing function. The command calls, in sorted order, any exe- cutable commands found in the directory This occurs for both first-boot and non-first-boot calls. HP may in the future sup- ply special commands in this location. The system administrator may also supply custom commands (programs or scripts) for site installations using, for example, Ignite-UX. The system must be rebooted for any change to take full effect. Select a timezone based on your country of location. Also allows you to set a user-supplied timezone. The system must be rebooted for any change to take effect. Set the system date and time interactively: This is similar to calling as a privileged user, but without having to format a time specification string. The change takes effect immediately. Set or change the IP address and subnet mask for the system. This function edits the file to associate the new IP address with the current hostname. Note: it does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. If multiple lan interfaces are present, the user can select each LAN interface (network interface card or NIC) separately to configure it. The system must be rebooted for any change to take effect. Set the route mask (which defines the network and local subnet portions of a network address), set the routing gateway, and define access to the Domain Name System (DNS) and Network Information Service (NIS). First-boot: These changes take effect immediately, without a reboot, because starts networking after setting the parameters. Non-first-boot: A reboot is required for all of these changes to take effect. Allow the user to set the local language settings. The user can either select one of the languages from the menu or they can set new valid language. will verify whether the new language is installed. If it is not installed, the user must install the language before executing this option. set_parms, Ignite-UX or Cold Install After "cold-installing" HP-UX from tape, CD-ROM, or DVD, or using Ignite-UX to install HP-UX from any source including an install server, the file is generally left on the system. This file is used to communicate to and other tools the hostname, networking, and other informa- tion that was used during the installation, to make it easier to use any of these values as final system parameters. In particular, uses as defaults the shell-style variables in this file that begin with For example, indicates which LAN interface was used during a network cold install. This is the LAN interface that configures. In general, first looks in for default information, then in the system configuration files in the directory. If any parameter is defined in both locations, the latter takes precedence. If Ignite-UX is installed on your system, see the manpage entries for ignite(5) and instl_adm(4). In particular, read instl_adm(4) for descriptions of the and variables. Interaction with auto_parms During the boot-up sequence, always invokes which in turn detects the first-boot situation and it calls if either or both of these condi- tions are true. The starts its interface and, based on user input, might call back into to obtain and set up the management of a DHCP lease. After completes this and other system set-up tasks, control passes back to which completes the boot-up sequence using the newly- created system initial identity parameters. See the rc(1M) manpage for information about for invocation context in the first-boot case. If the system has multiple lan interfaces and the user wishes to configure some with DHCP and others with static IP, the user must invoke first to configure all the lan interfaces which they wish to configure as DHCP. The user should not allow the system to be rebooted while doing this configuration. Then the user should invoke to configure the remaining lan interfaces. also allows the user to specify the DHCP server from which to get hostname and networking parameters and Class ID. If multiple interfaces are configured with DHCP, there is a chance that multiple hostnames will be returned through different DHCP enabled lan interfaces. If hostname is not set in and none of the interfaces are configured with addresses, then the hostname returned by the interface is updated in FILES
The command itself. Common subroutines used by and the sub-area commands. Directory holding all of sub-area commands called by which runs them in sorted order. Directory containing any hostname-change commands defined by the user. These are standalone commands run, in sorted order, by when setting or changing the hostname. File set by Ignite-UX or Cold Install that contains networking and other system information used during the installation. System configuration files modified by AUTHOR The command was developed by HP. SEE ALSO
passwd(1), auto_parms(1M), dhcpdb2conf(1M), rc(1M), instl_adm(4), ignite(5). set_parms(1M)
All times are GMT -4. The time now is 07:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy