AIX 5.2 Maksysb Image backup/restore


 
Thread Tools Search this Thread
Operating Systems AIX AIX 5.2 Maksysb Image backup/restore
# 1  
Old 06-13-2008
AIX 5.2 Maksysb Image backup/restore

Hello,

I am new to AIX, as I was primarily working on HP-UX servers.

We have some production servers and a couple of lab servers. We have upgraded over 40 servers from 5.2 to 5.3 running a particular application(1) using the golden 5.3 upgraded servers copy of makesysb. We have only two servers left to migrate from 5.2 to 5.3. These servers are running a different application(2) which has a Primary and Replica status.

The OS configurations are the same on the two servers application(2), but different than the 40 application(1) servers. We were wanting to peform a makesysb on the Primary AIX 5.2 server/application(2) and send it to a DAT tape. We would then take the DAT tape makesysb and install it on one of our LAB servers. We would then upgrade the lab server to 5.3 and create a makesysb. It sounds so simple!

The problem is we received a system email stating some of the following:

* Installing from a tape backup whose boot image is too large
* Backing up DMAPI filesystems
* 0512-064


Installing from a tape backup whose boot image is too large



This makes it sound like we are not going to be able to restore our lab server with the Primary AIX 5.2 makesysb.

How do we get a good makesysb from an AIX 5.2 server?
How do we install it on our LAB server?

Thank you!
# 2  
Old 06-13-2008
That reminds me of a bug I encountered some years ago when certain 5.2 modification levels "complained" about bootimage size. I am not sure that this is exactly the problem you describe but if you happen to use no current 5.2 ML you could update to the current 5.2 ML or try to install these APARs: IBM - IY56839: SYSTEM BOOT HANGS WHEN BOOT IMAGE EXCEEDS 12M 04/06/10 PTF PECHANGE
and/or probably IBM - IY64689: BOOT FAILS WITH LARGE BOOT IMAGE.

If that APAR does not apply or if updating the os is not an option you could uninstall some of the device drivers that you don't really use on the particular server. Compare the output of lsdev -C to lslpp -l |grep devices. There might be drivers for Graphics adapters, Token Ring, ATM adapters and CryptoCard for instance. Delete those unnecessary drivers with installp -u to shrink the bootimage size and run mksysb again.
# 3  
Old 06-13-2008
Boot from CD, aix install cd at the same level as the mksysb, and then restore the mksysb.
# 4  
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!!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

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

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

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

10. 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
Login or Register to Ask a Question