Sponsored Content
Operating Systems Solaris Archiveadm system cloning - Solaris 11.4 Post 303032071 by samthewildone on Sunday 10th of March 2019 08:49:39 PM
Old 03-10-2019
I know this is long overdue but I kid you not we had this done recently after my comments above;
A) If you want to do media creation from the archiveadm you need to exclude non-root datasets
B) If you have non-root datasets they're usually not a part of rpools; if this makes any sense.
1b) It should be a zpool just for those datasets which can be exported
2b) Exported zpools can be imported to another system or reattached to current system
C) Once you create a bootable UAR from the archiveadm, you will be able to install the cloned system and, have the ability to re-attach
the non-root datasets / zpools.
We were able to do this with a little hiccup here and there but the job went well...
Please if you have additional questions of the process just let me know so we can share with others who come across
this article.
 

9 More Discussions You Might Find Interesting

1. AIX

Problem cloning system

Hi everyone, I want to clone a AIX 5.2 system from a machine to another one. So i modified bosinst.data and image.data files (according to future platform) before making mksysb on old platform. After booting on CD and restoring system using mksysb tape, the installation is launched but ever... (2 Replies)
Discussion started by: fgaulois
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

Solaris 10 Zones cloning

I have gone over some articles regarding zones, I haven't found one that gives the exact information I'm looking for. I think I'm close though. I have 2 servers, each with a HBA into a SAN, they are both presented with the same luns. On server1, configured and installed the zone (zone1), the... (6 Replies)
Discussion started by: beaker457
6 Replies

4. UNIX for Advanced & Expert Users

Cloning a solaris system

I have several Solaris 8,9 and 10 servers. I need to refresh them and avoid doing any OS upgrades. I may have to apply patches when I am done due to the new hardware. My current servers have internal disk and my new target servers (same processor types) will have only SAN storage. Once the... (0 Replies)
Discussion started by: zzqv9p
0 Replies

5. Solaris

Cloning Solaris 10 perdicament

Hello and let me say at first, thank you for viewing this problem I have. From the top! Where I work, we have a Dell PowerEdge T300 X86 system running Solaris 10 8/07 s10x_u4wos_12b X86, and we realized, if this machine went down, we would be in trouble. So to fix that situation, I took it... (5 Replies)
Discussion started by: nitrolinux
5 Replies

6. Solaris

Cloning Solaris 10 with zones

Hello, What is the best method to use to clone a Solaris 10 machine with zones, to ensure all software and config can be easily installed on new hardware? Thank You (4 Replies)
Discussion started by: da2013
4 Replies

7. Solaris

Cloning RAID0 drives, Solaris 10u11

Hello all, this is my first time posting here. Where I work we have multiple servers (x3-2's) running Solaris 10u11 with 2 drives configured as RAID0, 300GB per. There are 4-6 open slots for drives to clone to. Past attempts to clone/backup these drives has failed. One of the machines is... (1 Reply)
Discussion started by: eprlsguy
1 Replies

8. Cybersecurity

How to protect system from cloning?

Hello there, I would like to protect a Linux system from cloning, I don't mind if the cloned hard drive works in the same computer, but I need to avoid it to work in other one, even if it uses exactly same mainboard model and rest of computer parts. I want the cloned system to get frozen or... (4 Replies)
Discussion started by: Installimat
4 Replies

9. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
ExtUtils::Constant(3pm) 				 Perl Programmers Reference Guide				   ExtUtils::Constant(3pm)

NAME
ExtUtils::Constant - generate XS code to import C header constants SYNOPSIS
use ExtUtils::Constant qw (WriteConstants); WriteConstants( NAME => 'Foo', NAMES => [qw(FOO BAR BAZ)], ); # Generates wrapper code to make the values of the constants FOO BAR BAZ # available to perl DESCRIPTION
ExtUtils::Constant facilitates generating C and XS wrapper code to allow perl modules to AUTOLOAD constants defined in C library header files. It is principally used by the "h2xs" utility, on which this code is based. It doesn't contain the routines to scan header files to extract these constants. USAGE
Generally one only needs to call the "WriteConstants" function, and then #include "const-c.inc" in the C section of "Foo.xs" INCLUDE const-xs.inc in the XS section of "Foo.xs". For greater flexibility use "constant_types()", "C_constant" and "XS_constant", with which "WriteConstants" is implemented. Currently this module understands the following types. h2xs may only know a subset. The sizes of the numeric types are chosen by the "Con- figure" script at compile time. IV signed integer, at least 32 bits. UV unsigned integer, the same size as IV NV floating point type, probably "double", possibly "long double" PV NUL terminated string, length will be determined with "strlen" PVN A fixed length thing, given as a [pointer, length] pair. If you know the length of a string at compile time you may use this instead of PV SV A mortal SV. YES Truth. ("PL_sv_yes") The value is not needed (and ignored). NO Defined Falsehood. ("PL_sv_no") The value is not needed (and ignored). UNDEF "undef". The value of the macro is not needed. FUNCTIONS
C_stringify NAME A function which returns a 7 bit ASCII correctly escaped version of the string passed suitable for C's "" or ''. It will die if passed Unicode characters. perl_stringify NAME A function which returns a 7 bit ASCII correctly escaped version of the string passed suitable for a perl "" string. constant_types A function returning a single scalar with "#define" definitions for the constants used internally between the generated C and XS func- tions. memEQ_clause NAME, CHECKED_AT, INDENT A function to return a suitable C "if" statement to check whether NAME is equal to the C variable "name". If CHECKED_AT is defined, then it is used to avoid "memEQ" for short names, or to generate a comment to highlight the position of the character in the "switch" statement. If CHECKED_AT is a reference to a scalar, then instead it gives the characters pre-checked at the beginning, (and the number of chars by which the C variable name has been advanced. These need to be chopped from the front of NAME). assign INDENT, TYPE, PRE, POST, VALUE... A function to return a suitable assignment clause. If TYPE is aggregate (eg PVN expects both pointer and length) then there should be multiple VALUEs for the components. PRE and POST if defined give snippets of C code to proceed and follow the assignment. PRE will be at the start of a block, so variables may be defined in it. return_clause return_clause ITEM, INDENT A function to return a suitable "#ifdef" clause. ITEM is a hashref (as passed to "C_constant" and "match_clause". INDENT is the number of spaces to indent, defaulting to 6. XXX document me switch_clause INDENT, NAMELEN, ITEMHASH, ITEM... An internal function to generate a suitable "switch" clause, called by "C_constant" ITEMs are in the hash ref format as given in the description of "C_constant", and must all have the names of the same length, given by NAMELEN (This is not checked). ITEMHASH is a reference to a hash, keyed by name, values being the hashrefs in the ITEM list. (No parameters are modified, and there can be keys in the ITEMHASH that are not in the list of ITEMs without causing problems). params WHAT An internal function. WHAT should be a hashref of types the constant function will return. params returns a hashref keyed IV NV PV SV to show which combination of pointers will be needed in the C argument list. dump_names dump_names DEFAULT_TYPE, TYPES, INDENT, OPTIONS, ITEM... An internal function to generate the embedded perl code that will regenerate the constant subroutines. DEFAULT_TYPE, TYPES and ITEMs are the same as for C_constant. INDENT is treated as number of spaces to indent by. OPTIONS is a hashref of options. Currently only "declare_types" is recognised. If the value is true a $types is always declared in the perl code generated, if defined and false never declared, and if undefined $types is only declared if the values in TYPES as passed in cannot be inferred from DEFAULT_TYPES and the ITEMs. dogfood dogfood PACKAGE, SUBNAME, DEFAULT_TYPE, TYPES, INDENT, BREAKOUT, ITEM... An internal function to generate the embedded perl code that will regenerate the constant subroutines. Parameters are the same as for C_constant. C_constant C_constant PACKAGE, SUBNAME, DEFAULT_TYPE, TYPES, INDENT, BREAKOUT, ITEM... A function that returns a list of C subroutine definitions that return the value and type of constants when passed the name by the XS wrapper. ITEM... gives a list of constant names. Each can either be a string, which is taken as a C macro name, or a reference to a hash with the following keys name The name of the constant, as seen by the perl code. type The type of the constant (IV, NV etc) value A C expression for the value of the constant, or a list of C expressions if the type is aggregate. This defaults to the name if not given. macro The C pre-processor macro to use in the "#ifdef". This defaults to the name, and is mainly used if value is an "enum". If a reference an array is passed then the first element is used in place of the "#ifdef" line, and the second element in place of the "#endif". This allows pre-processor constructions such as #if defined (foo) #if !defined (bar) ... #endif #endif to be used to determine if a constant is to be defined. A "macro" 1 signals that the constant is always defined, so the "#if"/"#endif" test is omitted. default Default value to use (instead of "croak"ing with "your vendor has not defined...") to return if the macro isn't defined. Spec- ify a reference to an array with type followed by value(s). pre C code to use before the assignment of the value of the constant. This allows you to use temporary variables to extract a value from part of a "struct" and return this as value. This C code is places at the start of a block, so you can declare variables in it. post C code to place between the assignment of value (to a temporary) and the return from the function. This allows you to clear up anything in pre. Rarely needed. def_pre =item def_post Equivalents of pre and post for the default value. utf8 Generated internally. Is zero or undefined if name is 7 bit ASCII, "no" if the name is 8 bit (and so should only match if SvUTF8() is false), "yes" if the name is utf8 encoded. The internals automatically clone any name with characters 128-255 but none 256+ (ie one that could be either in bytes or utf8) into a second entry which is utf8 encoded. PACKAGE is the name of the package, and is only used in comments inside the generated C code. The next 5 arguments can safely be given as "undef", and are mainly used for recursion. SUBNAME defaults to "constant" if undefined. DEFAULT_TYPE is the type returned by "ITEM"s that don't specify their type. In turn it defaults to IV. TYPES should be given either as a comma separated list of types that the C subroutine "constant" will generate or as a reference to a hash. DEFAULT_TYPE will be added to the list if not present, as will any types given in the list of ITEMs. The resultant list should be the same list of types that "XS_constant" is given. [Otherwise "XS_constant" and "C_constant" may differ in the number of parameters to the constant function. INDENT is currently unused and ignored. In future it may be used to pass in information used to change the C indentation style used.] The best way to maintain consistency is to pass in a hash reference and let this function update it. BREAKOUT governs when child functions of SUBNAME are generated. If there are BREAKOUT or more ITEMs with the same length of name, then the code to switch between them is placed into a function named SUBNAME_LEN, for example "constant_5" for names 5 characters long. The default BREAKOUT is 3. A single "ITEM" is always inlined. XS_constant PACKAGE, TYPES, SUBNAME, C_SUBNAME A function to generate the XS code to implement the perl subroutine PACKAGE::constant used by PACKAGE::AUTOLOAD to load constants. This XS code is a wrapper around a C subroutine usually generated by "C_constant", and usually named "constant". TYPES should be given either as a comma separated list of types that the C subroutine "constant" will generate or as a reference to a hash. It should be the same list of types as "C_constant" was given. [Otherwise "XS_constant" and "C_constant" may have different ideas about the number of parameters passed to the C function "constant"] You can call the perl visible subroutine something other than "constant" if you give the parameter SUBNAME. The C subroutine it calls defaults to the name of the perl visible subroutine, unless you give the parameter C_SUBNAME. autoload PACKAGE, VERSION, AUTOLOADER A function to generate the AUTOLOAD subroutine for the module PACKAGE VERSION is the perl version the code should be backwards compati- ble with. It defaults to the version of perl running the subroutine. If AUTOLOADER is true, the AUTOLOAD subroutine falls back on AutoLoader::AUTOLOAD for all names that the constant() routine doesn't recognise. WriteMakefileSnippet WriteMakefileSnippet ATTRIBUTE => VALUE [, ...] A function to generate perl code for Makefile.PL that will regenerate the constant subroutines. Parameters are named as passed to "WriteConstants", with the addition of "INDENT" to specify the number of leading spaces (default 2). Currently only "INDENT", "NAME", "DEFAULT_TYPE", "NAMES", "C_FILE" and "XS_FILE" are recognised. WriteConstants ATTRIBUTE => VALUE [, ...] Writes a file of C code and a file of XS code which you should "#include" and "INCLUDE" in the C and XS sections respectively of your module's XS code. You probably want to do this in your "Makefile.PL", so that you can easily edit the list of constants without touch- ing the rest of your module. The attributes supported are NAME Name of the module. This must be specified DEFAULT_TYPE The default type for the constants. If not specified "IV" is assumed. BREAKOUT_AT The names of the constants are grouped by length. Generate child subroutines for each group with this number or more names in. NAMES An array of constants' names, either scalars containing names, or hashrefs as detailed in "C_constant". C_FILE The name of the file to write containing the C code. The default is "const-c.inc". The "-" in the name ensures that the file can't be mistaken for anything related to a legitimate perl package name, and not naming the file ".c" avoids having to override Makefile.PL's ".xs" to ".c" rules. XS_FILE The name of the file to write containing the XS code. The default is "const-xs.inc". SUBNAME The perl visible name of the XS subroutine generated which will return the constants. The default is "constant". C_SUBNAME The name of the C subroutine generated which will return the constants. The default is SUBNAME. Child subroutines have "_" and the name length appended, so constants with 10 character names would be in "constant_10" with the default XS_SUBNAME. AUTHOR
Nicholas Clark <nick@ccl4.org> based on the code in "h2xs" by Larry Wall and others perl v5.8.0 2002-06-01 ExtUtils::Constant(3pm)
All times are GMT -4. The time now is 04:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy