Clone 1 Hard disk fromIBM Intellipoint server with AIX 5.x


 
Thread Tools Search this Thread
Operating Systems AIX Clone 1 Hard disk fromIBM Intellipoint server with AIX 5.x
# 8  
Old 06-21-2017
OK, now i got it: you were trying to clone a server. This is far easier done (and much more reliably so) by using the following information:

Investigate the mksysb command. It creates a backup image of a rootvg, but enriched by boot code and other information necessary to isntall a system from this image. You need a tape drive or disk space outisde of your rootvg to do it.

Result of the mksysb is a system image, basically a file. If it is written to some special devices (DVD, tape) it is bootable and you can use it on another system (doesn't even have to be identical, just sufficiently similar) to boot this and install it to a copy of the system from which you took it.

If you use any other device as a target (including a disk file) this will not be bootable by itself so you will need a boot media to boot the system and then you are able to still use the file as a source of installation arriving at the sasme result as above.

I hope this helps.

bakunin
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. AIX

AIX hard disk failure

Hi all, I have encountered the issue with the hard disk, the disk is failed and need to replace by the new one. As my understanding, this is just to take out the failed disk and insert the new ones, and that's all. But the third party hardware vendor said, there should be another procedure... (9 Replies)
Discussion started by: Phat
9 Replies

2. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

3. Linux

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

Hi all, I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies

4. Red Hat

How to monitor HP server hard disk failure ?

in red hat 4, 5 any one know any commands or any scritps to monitor HP DL 380 G5/6 server and trigger alarm when hard disk failed. thanks for all support ---------- Post updated at 02:45 PM ---------- Previous update was at 12:00 PM ---------- does HP ProLiant Support Pack support is... (4 Replies)
Discussion started by: maxlee24
4 Replies

5. SCO

Hard disk clone of OpenServer 5.0.0 didn't work, why?

Continuing saga of working on making a retail store more robust by creating a backup clone of the main server, a 1995 era :eek: PC running SCO OpenServer 5.0.0b and a discontinued Point of Sales (POS) software system. I have a PC of the same make and model. The CPU runs faster and it has a... (5 Replies)
Discussion started by: jgt10
5 Replies

6. SCO

Clone hard disk using Ghost

Hi. We tried cloning a SCO Unix hard disk using Norton Ghost. However, the new cloned hard disk encounter booting problem. What possibly go wrong? (1 Reply)
Discussion started by: Mizan
1 Replies

7. Solaris

Add new hard disk to sun sparc server?

A sparc server has a new SCSI hard disk added and labeled by the engineer, but they need to be formatted identically to an existing disk (c4t0d0). You decide to script the process and run from the command line without interaction. I know that the following command line must be achieve this. #... (3 Replies)
Discussion started by: kingsan
3 Replies

8. Shell Programming and Scripting

IInd Hard Disk Mounting Problem on 1st HDD On SCO UNIX Open Server

Hi Engg. ! :mad: I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Discussion started by: Niraj Gopal Sha
0 Replies

9. AIX

hard disk information in AIX

Hi, Other than df -k, is there any command that will tell me all physical hard drives installed on the system as well as the size of each one? I'm using AIX 5.1 Thanks, (3 Replies)
Discussion started by: quickfirststep
3 Replies
Login or Register to Ask a Question
Data::Clone(3pm)					User Contributed Perl Documentation					  Data::Clone(3pm)

NAME
Data::Clone - Polymorphic data cloning VERSION
This document describes Data::Clone version 0.003. SYNOPSIS
# as a function use Data::Clone; my $data = YAML::Load("foo.yml"); # complex data structure my $cloned = clone($data); # makes Foo clonable package Foo; use Data::Clone; # ... # Foo is clonable my $o = Foo->new(); my $c = clone($o); # $o is deeply copied # used for custom clone methods package Bar; use Data::Clone qw(data_clone); sub clone { my($proto) = @_; my $object = data_clone($proto); $object->do_something(); return $object; } # ... # Bar is also clonable $o = Bar->new(); $c = clone($o); # Bar::clone() is called DESCRIPTION
"Data::Clone" does data cloning, i.e. copies things recursively. This is smart so that it works with not only non-blessed references, but also with blessed references (i.e. objects). When "clone()" finds an object, it calls a "clone" method of the object if the object has a "clone", otherwise it makes a surface copy of the object. That is, this module does polymorphic data cloning. Although there are several modules on CPAN which can clone data, this module has a different cloning policy from almost all of them. See "Cloning policy" and "Comparison to other cloning modules" for details. Cloning policy A cloning policy is a rule that how a cloning routine copies data. Here is the cloning policy of "Data::Clone". Non-reference values Non-reference values are copied normally, which will drop their magics. Scalar references Scalar references including references to other types of references are not copied deeply. They are copied on surface because it is typically used to refer to something unique, namely global variables or magical variables. Array references Array references are copied deeply. The cloning policy is applied to each value recursively. Hash references Hash references are copied deeply. The cloning policy is applied to each value recursively. Glob, IO and Code references These references are not copied deeply. They are copied on surface. Blessed references (objects) Blessed references are not copied deeply by default, because objects might have external resources which "Data::Clone" could not deal with. They will be copied deeply only if "Data::Clone" knows they are clonable, i.e. they have a "clone" method. If you want to make an object clonable, you can use the "clone()" function as a method: package Your::Class; use Data::Clone; # ... my $your_class = Your::Class->new(); my $c = clone($your_object); # $your_object->clone() will be called Or you can import "data_clone()" function to define your custom clone method: package Your::Class; use Data::Clone qw(data_clone); sub clone { my($proto) = @_; my $object = data_clone($proto); # anything what you want return $object; } Of course, you can use "Clone::clone()", "Storable::dclone()", and/or anything you want as an implementation of "clone" methods. Comparison to other cloning modules There are modules which does data cloning. "Storable" is a standard module which can clone data with "dclone()". It has a different cloning policy from "Data::Clone". By default it tries to make a deep copy of all the data including blessed references, but you can change its behaviour with specific hook methods. "Clone" is a well-known cloning module, but it does not polymorphic cloning. This makes a deep copy of data regardless of its types. Moreover, there is no way to change its behaviour, so this is useful only for data which link to no external resources. "Data::Clone" makes a deep copy of data only if it knows that the data are clonable. You can change its behaviour simply by defining "clone" methods. It also exceeds "Storable" and "Clone" in performance. INTERFACE
Exported functions clone(Scalar) Returns a copy of Scalar. Exportable functions data_clone(Salar) Returns a copy of Scalar. The same as "clone()". Provided for custom clone methods. is_cloning() Returns true inside the "clone()" function, false otherwise. DEPENDENCIES
Perl 5.8.1 or later, and a C compiler. BUGS
No bugs have been reported. Please report any bugs or feature requests to the author. SEE ALSO
Storable Clone AUTHOR
Goro Fuji (gfx) <gfuji(at)cpan.org> LICENSE AND COPYRIGHT
Copyright (c) 2010, Goro Fuji (gfx). All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2011-01-15 Data::Clone(3pm)