Sponsored Content
Full Discussion: IBM AIX 5.2 cloning Hdds
Operating Systems AIX IBM AIX 5.2 cloning Hdds Post 302999416 by MichaelFelt on Tuesday 20th of June 2017 02:15:33 AM
Old 06-20-2017
Hi,

a) AIX 5.2 does not virtualize the same way AIX 5.3 can (no virtual ethernet, no microparititions). The product you needed for that is vWPAR 5.2 - and, as the AIX 5.3 version is rumored to be withdrawn from marketing soon - I am going to guess the vWPAR 5.2 version is already withdrawn.
b) make an mksysb image asap to a file, do not worry about it being bootable or not. Just make sure you have the image.

More to come - my ride has arrived.

So, a day later... continuing as promised.

c) to test your DVD making process - years ago (AIX 5.3 ML05 days) I wrote a short article on how to create a bootable DVD/CD (CD will work in this case) - so that you could then read and install an mksysb file from a second DVD. This was a problem I was having when moving things from some old P43-140 systems to a POWER4. If I recall correctly, the process describes (see http://www.rootvg.net/content/view/134/88/) how a previously captured "mksysb" file can be used as input to the mkDVD process. The mksysb image created was the minimum needed to create a bootable disk.
Largely I gave up on mkDVD as a workable backup method (running the command "live" means you need to have 3X space - the actual system, the temp mksysb file it makes, and then the iso9660 file(s) it creates. One thing I learned to not do is let mkDVD write directly to the DVD (although that is probably not what you have - my POWER4 had a DVD/RAM device, soI could also use the -U option (write as UDF format to the RAM-DVD (special kind of RW-DVD media). (basically, it was so horrendously slow I always wrote to files, transferred them to a PC and burned the DVD on my PC).

So, hoping your system is still alive enough for you to make an mksysb image - I also highly recommend backing up as many non-OS related files (i.e., your real data) in a tar file - so it is easily readable on various platforms.

If you have access to any AIX 5.3 media - this should accept most applications supported on AIX 5.2 - then you could try the process of migrating your applicaitons to AIX 5.3 - and then run that on vWPAR for AIX 5.3.

Hope this helps!

Last edited by MichaelFelt; 06-21-2017 at 07:30 AM.. Reason: promised to continue...
 

10 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. AIX

Help-----ibm Aix???

:confused: Hello everybody, I am a totel dummy when it comes to UNIX!!! Must be wondering what I am doing here right? I'm most keen on knowing about-it-all. I need help. Wanna know all about the IBM AIX. The versions, the latest. Please tell me how do I go about my search. Thanks a... (3 Replies)
Discussion started by: rtanuja
3 Replies

3. HP-UX

hdds physically

Hi, I've a HP-UX 10x running on HP9000 box and also I have 3 scsi hdd(9Gb), one of them is working. I need to check the other 2 hdd physically. Is there an utility to check them from unix or another way to do it? Thanks.... (5 Replies)
Discussion started by: efrenba
5 Replies

4. UNIX for Advanced & Expert Users

how is IBM-AIX better..?

why IBM-AIX is preferred over HP-UX ..... In what way it is better for infrastructure......? Suggestions are welcome... Suggest you read the RULES (0 Replies)
Discussion started by: bishweshwar
0 Replies

5. AIX

IBM-AIX Technical Help

Hi All :b:, Motto : I am in need of IBM-AIX INTERVIEW QUESTIONS. I am working as an a operator, on solaris 5.10 env. i have got an opportunity of IBM-AIX Administrator Job. I really don't want to miss this opportunity. By the way i have basic knowledge of Solaris UNIX, I have confident i... (7 Replies)
Discussion started by: imrankhan.in
7 Replies

6. AIX

ibm aix L1

hello all, can anyone send me ibm aix L1 interview questions... thank u guys...jiyojith (0 Replies)
Discussion started by: jiyojith
0 Replies

7. AIX

IBM AIX on IBM Eseries & x series server

Hi, I want to know whether IBM AIX can be installed on the IBM e series and x series server hardware? Thanks & Regards Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies

8. AIX

pwage-aix for IBM AIX servers

This is the password aging script for aix just completed. So far tested and still testing on one of our aix server running 5.3.0.0. So anyway as you can see it is very similar to pwage-hpux-T the only difference on aix /etc/passwd file looks in this format. Also for this script to work you need to... (0 Replies)
Discussion started by: sparcguy
0 Replies

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

10. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
VOS_BACKUPSYS(1)					       AFS Command Reference						  VOS_BACKUPSYS(1)

NAME
vos_backupsys - Creates a backup volume for several read/write volumes SYNOPSIS
vos backupsys [-prefix <common prefix on volume(s)>+] [-server <machine name>] [-partition <partition name>] [-exclude] [-xprefix <negative prefix on volume(s)>+] [-dryrun] [-cell <cell name>] [-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve] [-help] vos backups [-pr <common prefix on volume(s)>+] [-s <machine name>] [-pa <partition name>] [-ex] [-x <negative prefix on volume(s)>+] [-d] [-c <cell name>] [-noa] [-l] [-v] [-en] [-nor] [-h] DESCRIPTION
The vos backupsys command clones each indicated read/write volume to create a backup version, placing each clone at the same site as its read/write source version. It assigns each clone the same name as the read/write source, adding a ".backup" extension. It assigns the volume ID number already allocated for the backup version in the Volume Location Database (VLDB). If a backup version already exists for a given volume, the new clone replaces it. To clone every read/write volume listed in the VLDB, omit all of the command's options. Otherwise, combine the command's options to clone various groups of volumes. The options use one of two basic criteria to select volumes: location (the -server and -partition arguments) or presence in the volume name of one of a set of specified character strings (the -prefix, -exclude, and -xprefix options). To clone only volumes that reside on one file server machine, include the -server argument. To clone only volumes that reside on one partition, combine the -server and -partition arguments. The -partition argument can also be used alone to clone volumes that reside on the indicated partition on every file server machine. These arguments can be combined with those that select volumes based on their names. Combine the -prefix, -exclude, and -xprefix options (with or without the -server and -partition arguments) in the indicated ways to select volumes based on character strings contained in their names: o To clone every read/write volume at the specified location whose name includes one of a set of specified character strings (for example, begins with "user." or includes the string "afs"), use the -prefix argument or combine the -xprefix and -exclude options. o To clone every read/write volume at the specified location except those whose name includes one of a set of specified character strings, use the -xprefix argument or combine the -prefix and -exclude options. o To clone every read/write volume at the specified location whose name includes one of one of a set of specified character strings, except those whose names include one of a different set of specified character strings, combine the -prefix and -xprefix arguments. The command creates a list of all volumes that match the -prefix argument and then removes from the list the volumes that match the -xprefix argument. For effective results, the strings specified by the -xprefix argument must designate a subset of the volumes specified by the -prefix argument. If the -exclude flag is combined with the -prefix and -xprefix arguments, the command creates a list of all volumes that do not match the -prefix argument and then adds to the list any volumes that match the -xprefix argument. As when the -exclude flag is not used, the result is effective only if the strings specified by the -xprefix argument designate a subset of the volumes specified by the -prefix argument. The -prefix and -xprefix arguments both accept multiple values, which can be used to define disjoint groups of volumes. Each value can be one of two types: o A simple character string, which matches volumes whose name begin with the string. All characters are interpreted literally (that is, characters that potentially have special meaning to the command shell, such as the period, have only their literal meaning). o A regular expression, which matches volumes whose names contain the expressions. Place a caret ("^") at the beginning of the expression, and enclose the entire string in single quotes (''). Explaining regular expressions is outside the scope of this reference page; see the UNIX manual page for regexp(5) or (for a brief introduction) backup_addvolentry(8). As an example, the following expression matches volumes that have the string "aix" anywhere in their names: -prefix '^.*aix' To display a list of the volumes to be cloned, without actually cloning them, include the -dryrun flag. To display a statement that summarizes the criteria being used to select volume, include the -verbose flag. This command can be used to clone a single read/write volume; specify its complete name as the -prefix argument. However, it is more efficient to use the vos backup command, which employs a more streamlined technique for finding a single volume. OPTIONS
-prefix <common prefix> Specifies one or more simple character strings or regular expressions of any length; a volume whose name includes the string is placed on the set of volumes to be cloned. Include field separators (such as periods) if appropriate. This argument can be combined with any combination of the -server, -partition, -exclude, and -xprefix options. -server <machine name> Identifies the file server machine where each read/write 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). This argument can be combined with any combination of the -prefix, -partition, -exclude, and -xprefix options. -partition <partition name> Identifies the partition where each read/write source volume resides. Provide the partition's complete name with preceding slash (for example, "/vicepa") or use one of the three acceptable abbreviated forms. For details, see vos(1). This argument can be combined with any combination of the -prefix, -server, -exclude, and -xprefix options. -exclude Reverses the meaning of the -prefix or -xprefix argument. This flag can be combined with any combination of the -prefix, -server, -partition, and -xprefix options. -xprefix <negative prefix> Specifies a simple character string or regular expression of any length; a volume whose name includes the string is removed from the set of volumes to be cloned. Include field separators (such as periods) if appropriate. This argument can be combined with any combination of the -prefix, -server, -partition, and -exclude options. -dryrun Displays on the standard output stream a list of the volumes to be cloned, without actually cloning them. -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
The command generates the following messages on the standard output stream to confirm that the operation was successful: done Total volumes backed up: <number_cloned>; failed to backup: <failures> If the -dryrun flag is included, a list of the volumes to be backed up precedes the standard confirmation messages. If the -verbose flag is included but not the -dryrun flag, the following messages appear for each volume. The output concludes with the standard confirmation messages. Creating backup volume for <volume_name> on <date/time> {Recloning backup volume | Creating a new backup clone} <backup_volumeID> . . .done If both the -dryrun and -verbose flags are included, the output begins with a statement summarizing the criteria being used to select the volumes, followed by a list of the volumes and the standard confirmation messages. The format of the criteria summary statement depends on which other options are provided: o If only the -prefix argument is provided, or the -xprefix and -exclude options are combined: Would have backed up volumes which are prefixed with <string> [or <string>] . . o If only the -xprefix argument is provided, or the -prefix and -exclude options are combined: Would have backed up volumes which are not prefixed with <string> [nor <string>] . . o If the -prefix and -xprefix arguments are combined: Would have backed up volumes which are prefixed with <string> [or <string>] removing those which are prefixed with <x_string> [or <x_string>] . . o If the -prefix, -xprefix, and -exclude options are provided: Would have backed up volumes which are not prefixed with <string> [nor <string>] adding those which are prefixed with <x_string> [or <x_string>] . . EXAMPLES
The following example creates a backup version of every read/write volume listed in the cell's VLDB whose name begins with the string user. % vos backupsys -prefix user The following example, appropriate in the ABC Corporation cell, creates a backup version of every read/write volume on the file server machine "fs3.abc.com". % vos backupsys -server fs3.abc.com The following example, appropriate in the State University cell, creates a backup version of every read/write volume on the file server machine "db1.stateu.edu" except those whose name includes the string "temp". % vos backupsys -server db1.stateu.edu -prefix '^.*temp' The following example creates a backup version of every volume listed in the cell's VLDB, excluding those whose names contain the string "source", but including those whose names contain the string "source.current". % vos backupsys -prefix '^.*source' -exclude -xprefix '^.*source.current' PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument 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
backup_addvolentry(8), vos(1), vos_backup(1) UNIX manual page for regexp(5) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 VOS_BACKUPSYS(1)
All times are GMT -4. The time now is 04:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy