Sponsored Content
Operating Systems AIX AIX 5.2 Maksysb Image backup/restore Post 302205822 by dayinthelife on Monday 16th of June 2008 11:13:44 AM
Old 06-16-2008
Thanks for the Replies!

I may have to wait for my counterpart to get back from vacation.

I am going to try and boot off the fakemaksysb image I created off the primary server. Hopefully we will receive the DAT maksysb image. I will try to install the DAT with the bootable CD.

Here was some more of the verbeage in the email we received after creating the DAT maksysb.

1). Boot off of media that has a smaller boot image and is at the same level
as the backup. (For example, the AIX product media, or network boot image.)
Then, select "3 Access Advanced Maintenance Functions", select "4 Install
from a System Backup", select tape drive and install. If you do not have AIX
product media at the same level, see "CREATING BOOTABLE CD MEDIA" below.

Note: If install media is not at equal to or higher maintenance level than
the level of the backup image being installed, unpredictable results might occur.

2). Remove filesets from the system that would result in a smaller boot image
and then create a new backup.

This option might not be valid if the system requires all the filesets that it
currently has on it to run. This includes filesets whose names begin with
devices, for example: devices.pci.xxxxxx.rte). Do not remove any filesets
for devices that you might have on other systems in your environment because
the resulting backup may not be able to boot or install onto those systems.


CREATING BOOTABLE CD MEDIA:

Preferably on the same system that the non-bootable backup came from, execute
the following commands:

# cd /var/adm/ras
# ls ./bosinst.data ./image.data | backup -ivqf/tmp/fakemksysb
# mkcd -m /tmp/fakemksysb -d /dev/cdx # Where cdx is an attached cdwriter
OR
# mkcd -m /tmp/fakemksysb -S # Will create a CD image which can be
# transferred to a system with a cdwriter

Note: The final mkcd command in the previous example makes an image that could
be transferred to another system (AIX or non-AIX) for burning.
Note: The bosinst.data file must be set for a prompted install (PROMPT = yes).



Thanks again for your assistance!!
 

10 More Discussions You Might Find Interesting

1. AIX

AIX backup --> Linux Restore

Hi all, I have a large number of backup tapes which were originally written with the AIX "backup" command. I now need to convert these to "tar" format, but unfortunately I no longer have access to an AIX machine. I have been able to connect the old tape drive (3590) to a Linux box and it works... (2 Replies)
Discussion started by: jauru
2 Replies

2. AIX

AIX backup and restore

Hello, Some background so you can see what I'm trying to do on AIX: In Windows its possible to partition a single hard drive into 2 separate logical paritions which may appear as a C and a D drive. It is then possible to to use 3rd party software such as Power Quest Drive Image to create a... (3 Replies)
Discussion started by: quickfirststep
3 Replies

3. Filesystems, Disks and Memory

Boot Sequence changed After Image Restore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- " ..... EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies

4. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

5. AIX

AIX Tivoli Image Restore

Dear Team: I am new to this Forum and I need your help for my AIX restoration problem its very urgent my problem as follow failure I have a Tivoli Storage Manger was installed on that server. I created backup image using Tivoli and it created a set of files each file is around 2GB so... (1 Reply)
Discussion started by: Firas_Abed
1 Replies

6. Red Hat

Backup / Restore

Hi, I need to back up a RH file system (96G). The files are oracle .dbf format some of which are 5G in size. I know that tar has got a size restriction of 2G so I cannot use this. Can anyone recommend an alternative way of backuping up this FS? I have been looking at dump but this... (6 Replies)
Discussion started by: Duffs22
6 Replies

7. AIX

[Tip] Backup and restore on AIX

Pretty penny's. Just remember that mksysb and savevg are just front-ends for backup. In other words, backups on AIX are organized by volume groups. mksysb is specialized for rootvg and savevg is used for other volume groups. Ignoring that rootvg also creates files needed to boot a system... (1 Reply)
Discussion started by: MichaelFelt
1 Replies

8. AIX

Restore mksysb image on cloned LPAR

Hi Folks, How to restore mksysb image on LPAR which is already having cloned AIX OS installed on hdisk0 (nothing configured, only full partition image is sitting on hdisk0) Let me know. Thank a lot. (1 Reply)
Discussion started by: snchaudhari2
1 Replies

9. Solaris

Solaris 10 Restore from flar image

Hi! I want to migrate Sun Fire v240 server (sun4u) with Solaris 10 update 6 to LDOM virtual host (sun4v). I was mount NFS directory from another server in /mnt and did this steps on v240 1) I add to the /var/sadm/system/admin/.platform PLATFORM_GROUP=sun4v # cat... (1 Reply)
Discussion started by: pbubentsov
1 Replies

10. AIX

AIX 7.2 MKSYSB Backup and Restore Best Practices?

Hello, Running AIX 7.2 on Power9 bare-metal (no LPAR and no NIM server), in the process of creating a guide on MKSYSB process. I understand that MKSYSB is a backup of the rootvg and we can exclude stuff via exclude.rootvg file, the rest of the data volumes are mapped to the system as LUNs via... (7 Replies)
Discussion started by: c3rb3rus
7 Replies
pmerge(8)						      System Manager's Manual							 pmerge(8)

NAME
pmerge - Builds a network bootable kernel. SYNOPSIS
/usr/sys/bin/pmerge bootfile kernel.name new.kernel DESCRIPTION
The kernel, vmunix, is not bootable over the network. The pmerge utility prepends the bootfile onto the kernel image (kernel.name) to cre- ate a new operating system image (new.kernel) that is bootable over the network. Instead of a booting a network loadable kernel, it is sometimes desired to bootstrap link a kernel over the network. In this case, (ker- nel.name) is the name of the sysconfigtab file on the server containing the list of modules to be loaded to the client. These modules are then linked to create a bootable kernel on the client. The pmerge utility is used by doconfig(8) to create a bootable operating system for dataless management services (DMS) client systems to boot over the network. The pmerge utility is automatically invoked by doconfig(8) during the kernel build process and should not be invoked independently. The pmerge utility is located in /var/adm/dms/dmsn.alpha/root/usr/sys/bin on the DMS server. SEE ALSO
Commands: dmu(8), doconfig(8) Sharing Software on a Local Area Network pmerge(8)
All times are GMT -4. The time now is 05:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy