Sponsored Content
Operating Systems AIX How to restore rootvg archive after AIX 6.1 crash Post 302523785 by dukessd on Thursday 19th of May 2011 07:31:17 PM
Old 05-19-2011
Hi,

It sounds like you were very lucky with your recovery but I would be both dubious of relying on this for a production restore and also about how valid the recovery is on your test box for further development on this system.

For the ISO backup you'll find all sorts of problems like the 2GB file limit on VIOS install media meaning the image is split into more than one file, let alone more than one ISO although I suspect it will just create a second ISO for the remaining data. Good luck with that one, please let us know what you find out.

For your bootp issue you'll find VIOS and AIX installs and install media are quite different.
AIX installs from scratch or base filesets with a full base install process but VIOS media actually contains a backup or mksysb that is restored during the VIOS install, much like a mksysb migration of AIX and I suspect the linux bootp VIOS install relies on this.

You could probably create a generic AIX mksysb and use that to deploy AIX in the method suggested but I don't think it will work with AIX install media because the two installs are so completely different.

HTH and good luck, please keep us updated on your progress.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Selective restore from a cpio tape archive

Hi, I use following command to restore data from my cpio tape archive: $cpio -icvd < /dev/rct0 But this'll restore all tape contents to the current path, what if I want only selected files from the tape, suppose I want /home/compdir/home2/Rev83/data/PL/01/*.* files to be restored... (8 Replies)
Discussion started by: tayyabq8
8 Replies

2. Solaris

Can I restore from a flash archive without re-entering the basic sys info?

Hi I would like to be able to take adhoc backups of my systems using flash archive - flarcreate - and then restore from them to the same system without having to enter the basic configuration again when I boot from the Solaris CD. So, I'd like to be able to create a flar archive ... (1 Reply)
Discussion started by: emjs
1 Replies

3. UNIX for Advanced & Expert Users

Archive and Restore

Can someone please let me have a nice shell script to: 1) Identify all folders/sub-folders/files older than 365 days with the exception of one or two folders e.g. named - "common" or "test" 2) Archive (1) above for example in a TAR file 3) Delete all in (1) above and that's it... 4) In case... (1 Reply)
Discussion started by: mahmud
1 Replies

4. AIX

AIX Rootvg mirror and sysdumplv

Guys, In my AIX 6.1 box the rootvg was on hdisk2, I tried to migrated it to hdisk0 Added hisk0 to rootvg , mirrored rootvg and changed bootlist and and sucessfully rebooted from hdisk0 Now I tried to remove the hdisk2 from rootvg so breaked mirror -bash-3.00# unmirrorvg rootvg hdisk2... (3 Replies)
Discussion started by: kkeng808
3 Replies

5. HP-UX

restore data after system crash

Hi all, I have a server running HP-UX 11i V1 (11.11). We had a problem with the system disk which cannot boot and the recovery with the CD failed too. the only solution was to re-install the system on a new disk. The problem now is to get access to the data which are on other disks, not... (2 Replies)
Discussion started by: aribault
2 Replies

6. AIX

Erase AIX rootvg system disk

Hello all, I need help for erasing IBM P5 machine running AIX 5.3. I have 2 system disks (Hardware mirror) and i'm looking for a way like a LIVE CD bootable CD so I can boot with the cd and then format the system disks with a "secure erase" software. (7 Replies)
Discussion started by: kobi gabai
7 Replies

7. UNIX for Dummies Questions & Answers

Unable to restore cpio archive to a directory

Hello Every one, I want to back up all passwd files to /xyz/passfiles.cpio and Then restore them to /abc directory. Here is what I wrote: find / -name passwd | cpio -oc > /tmp/passwd.cpio and to restore cd abc cpio -ium < /tmp/passwd.cpio I can not find the files restored to /abc... (2 Replies)
Discussion started by: drdigital_m
2 Replies

8. Solaris

Restore from Flash Archive on local filesystem

I am doing a practice restore using a test UNIX(Solaris) system, and a SCSI Hard Drive whose slice 5 contains the Flash Archive file that I need to restore from. The test system is offline( no network ) and does not have external devices, such as tape drive. My goal is to somehow restore the... (9 Replies)
Discussion started by: the.gooch
9 Replies

9. AIX

Using restorevgfiles to restore entire directory from rootvg problems

I am trying to restore a specific directory and all sub-directories therein using a rootvg tape. I am using the following command to make the backup: mksysb -m -i -v /dev/rmt0 However, I am getting the following result: tctl status rmt0 Available 04-08-00-0,0 LVD SCSI 4mm Tape Drive... (10 Replies)
Discussion started by: herot
10 Replies

10. AIX

AIX break rootvg mirror from system down

Hello, aix 5.2, mirrored rootvg on hdisk0 and hdisk1. hdisk0 is dead. I can boot to cd, into sms, into maintenance mode. I can fsck all the various partitions on hdisk1 (the hd4 hd2 hd3, etc...) all is fine. But without the hdisk0 part of the mirror I cannot get the system to boot. ystem hangs on... (6 Replies)
Discussion started by: sshapiro
6 Replies
TRACE-CMD-RESTORE(1)													      TRACE-CMD-RESTORE(1)

NAME
trace-cmd-restore - restore a failed trace record SYNOPSIS
trace-cmd restore [OPTIONS] [command] cpu-file [cpu-file ...] DESCRIPTION
The trace-cmd(1) restore command will restore a crashed trace-cmd-record(1) file. If for some reason a trace-cmd record fails, it will leave a the per-cpu data files and not create the final trace.dat file. The trace-cmd restore will append the files to create a working trace.dat file that can be read with trace-cmd-report(1). When trace-cmd record runs, it spawns off a process per CPU and writes to a per cpu file usually called trace.dat.cpuX, where X represents the CPU number that it is tracing. If the -o option was used in the trace-cmd record, then the CPU data files will have that name instead of the trace.dat name. If a unexpected crash occurs before the tracing is finished, then the per CPU files will still exist but there will not be any trace.dat file to read from. trace-cmd restore will allow you to create a trace.dat file with the existing data files. OPTIONS
-c Create a partial trace.dat file from the machine, to be used with a full trace-cmd restore at another time. This option is useful for embedded devices. If a server contains the cpu files of a crashed trace-cmd record (or trace-cmd listen), trace-cmd restore can be executed on the embedded device with the -c option to get all the stored information of that embedded device. Then the file created could be copied to the server to run the trace-cmd restore there with the cpu files. If *-o* is not specified, then the file created will be called 'trace-partial.dat'. This is because the file is not a full version of something that trace-cmd-report(1) could use. -t tracing_dir Used with -c, it overrides the location to read the events from. By default, tracing information is read from the debugfs/tracing directory. -t will use that location instead. This can be useful if the trace.dat file to create is from another machine. Just tar -cvf events.tar debugfs/tracing and copy and untar that file locally, and use that directory instead. -k kallsyms Used with -c, it overrides where to read the kallsyms file from. By default, /proc/kallsyms is used. -k will override the file to read the kallsyms from. This can be useful if the trace.dat file to create is from another machine. Just copy the /proc/kallsyms file locally, and use -k to point to that file. -o output' By default, trace-cmd restore will create a trace.dat file (or trace-partial.dat if -c is specified). You can specify a different file to write to with the -o option. -i input By default, trace-cmd restore will read the information of the current system to create the initial data stored in the trace.dat file. If the crash was on another machine, then that machine should have the trace-cmd restore run with the -c option to create the trace.dat partial file. Then that file can be copied to the current machine where trace-cmd restore will use -i to load that file instead of reading from the current system. EXAMPLES
If a crash happened on another box, you could run: $ trace-cmd restore -c -o box-partial.dat Then on the server that has the cpu files: $ trace-cmd restore -i box-partial.dat trace.dat.cpu0 trace.dat.cpu1 This would create a trace.dat file for the embedded box. SEE ALSO
trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1) AUTHOR
Written by Steven Rostedt, <rostedt@goodmis.org[1]> RESOURCES
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git COPYING
Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL). NOTES
1. rostedt@goodmis.org mailto:rostedt@goodmis.org 06/11/2014 TRACE-CMD-RESTORE(1)
All times are GMT -4. The time now is 03:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy