[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1089
  • Last Modified:

Aix 6.1 - Error "UP" Kernal Type Invalid

I just installed IBM Tivoli v5.6.5 w/ Sysback and trying to do a sysback up to tape but keep getting the following error:

The "up" kernel type is invalid or support for this kernel is not installed..

I have a Power 5 with a 64Bit 2Ghz processor
0
compdigit44
Asked:
compdigit44
  • 13
  • 12
  • 2
1 Solution
 
compdigit44Author Commented:
Thanks..

I'm not an AIX person but would it be possible to added the Use the "-k 64" flag switch to the end of my old backup script that used to run on my AIX 5.3 to make it work on 6.1
0
 
TomuniqueCommented:
Sorry, I don't use sysback, so can't tell you for sure..

Try the command "man   sysback"
or google it,
 or, try it on your system for a test.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
woolmilkporcCommented:
So you're using a script to run sysback (not smit)?

The "-k" flag of "sysback" defaults to the current kernel, which should really not be "UP" in your case, because AIX 6.1 neither supports nor ships this kernel version anymore.

Are you really sure that there's not a "-k up" flag somewhere in your script?
Of course you could post the script so we can have a look.

Also, what do you see with "ls -l /unix" and "bootinfo -K"?
0
 
compdigit44Author Commented:
I have attached a screen shot of the output of the commands request:

Also, I beleive I was able to ge the "-k 64" synatx to work but my backup still will not run. I keep getting the following error inthe logs:

.../usr/sbin/bosboot[3]: 7667862 HangUp   System backup failed
sysback-screen-shot.bmp
0
 
woolmilkporcCommented:
The message "System backup failed" is usually accompanied by a descriptive text.
Please post the whole thing!

Besides that I think you should anyway consider upgrading your rather old SysBack to a new version (6.1.3).
0
 
compdigit44Author Commented:
There is not other message posted in the error. That's all it's giving me.

I cannot upgrade to the latest version of sysback since my company dropped support for v5.6.5 last year..

Any suggestion to try in smti to get this to work would be helpful..

Please note I only have one VG which is the rootVG which is about 68GB
0
 
woolmilkporcCommented:
"smitty sysback" should give you a good start!
0
 
compdigit44Author Commented:
I tried to use smitty but I'm not sure if the backup is actually running or not. The LED on my tape drive is solid green and usually blinks when a back is being done..

From what I have read IBM Tivoli w/ Sysba k v5.6.5 can be used on a AIX 6.1 platform. Also I'm using technology level 7? Are there other know issues with this older version of sysback that I'm not aware of?
0
 
woolmilkporcCommented:
smitty displays a log and finally a status page during/after the backup run.
Didn't this happen?

And No, I'm not awareof any incompatibility issues between SysBack 5.6 and AIX 6.1
0
 
compdigit44Author Commented:
I was finially able to get the backup to run but it completed with errors...


Generating LVM information ..
exec(): 0509-036 Cannot load program getvginfo_ext because of the following errors:
      0509-130 Symbol resolution failed for getvginfo_ext because:
      0509-136   Symbol lvm_queryvg_ext (number 14) is not exported from
               dependent module /usr/lib/liblvm.a(shr.o).
      0509-192 Examine .loader section symbols with the
             'dump -Tv' command.
exec(): 0509-036 Cannot load program getvginfo_ext because of the following errors:
      0509-130 Symbol resolution failed for getvginfo_ext because:
      0509-136   Symbol lvm_queryvg_ext (number 14) is not exported from
               dependent module /usr/lib/liblvm.a(shr.o).
      0509-192 Examine .loader section symbols with the
             'dump -Tv' command.
exec(): 0509-036 Cannot load program getvginfo_ext because of the following errors:
      0509-130 Symbol resolution failed for getvginfo_ext because:
      0509-136   Symbol lvm_queryvg_ext (number 14) is not exported from
               dependent module /usr/lib/liblvm.a(shr.o).
      0509-192 Examine .loader section symbols with the
             'dump -Tv' command.
exec(): 0509-036 Cannot load program getvginfo_ext because of the following errors:
      0509-130 Symbol resolution failed for getvginfo_ext because:
      0509-136   Symbol lvm_queryvg_ext (number 14) is not exported from
               dependent module /usr/lib/liblvm.a(shr.o).
      0509-192 Examine .loader section symbols with the
             'dump -Tv' command.
Generating table of contents ..
lsfs: 0506-915 No record matching /dev/hd5 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd5 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd6 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd6 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd8 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd8 was found in /etc/filesystems.
0
 
woolmilkporcCommented:
OK,

seems indeed an incompatibility between the SysBack version and the AIX level.

I think you should apply the latest PTFs.

They're available for free here:

ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/sysback/

Try 5.6.8 first. If it complains about missing requisites apply 5.6.6 and 5.6.7 as well.

Installation is done via installp ("installp -acqd sysback.568.ptf.rte all" in the directory where you downloadad the file to), or via "smitty install" as usual. Run "inutoc ." in the download directory first.

I hope this will do the trick. If it doesn't I fear you will have to procure version 6, one way or the other.
0
 
compdigit44Author Commented:
Thanks..

Should I go right for version 6.1.3???
0
 
woolmilkporcCommented:
What you see in the link are PTFs, not Base Level filesets.

PTF 6.1.3 is only applicable to an already installed 6.1.0 base, which you don't have at hand.
0
 
compdigit44Author Commented:
I just ran the install for 5.6.8. How can I easily verify that IBM Tivoli Storage Manager Backup and Recovery is now running at version 5.6.8? I tried using the "lslp -l *Tivoli* command but the default agent that comes with Aix is only listed.
0
 
woolmilkporcCommented:
lslpp -l |grep -i  tivoli

or

lslpp -l '*ivoli*'

The secret is the lowercase "t".
0
 
compdigit44Author Commented:
Thanks..

The update did install successfully and IBM Tivoli Sysback is now running at version 5.6.8 but I'm still having problems with may backup.. PLease see the error logs below..


Changing tape block size to 512 ..
Placing boot image on tape ..
bosboot: Boot image is 43008 512 byte blocks.
Placing install image on tape ..
Placing Backup install programs on tape ..
Returning tape block size to 1024 ..
Repositioning tape ..

Generating LVM information ..
Generating table of contents ..
lsfs: 0506-915 No record matching /dev/hd5 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd5 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd6 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd6 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd8 was found in /etc/filesystems.
lsfs: 0506-915 No record matching /dev/hd8 was found in /etc/filesystems.
Pre-processing / filesystem ..
Pre-processing /usr filesystem ..
Pre-processing /admin filesystem ..
Pre-processing /commvault filesystem ..
Pre-processing /home filesystem ..
Pre-processing /opt filesystem ..
Pre-processing /s filesystem ..
Pre-processing /s/s2 filesystem ..
Pre-processing /s/seclib filesystem ..
Pre-processing /tmp filesystem ..
Pre-processing /users filesystem ..
Pre-processing /users_archive filesystem ..
Pre-processing /var filesystem ..
Pre-processing /var/adm/ras/livedump filesystem ..
Pre-processing /var/adm/ras/platform filesystem ..
Writing table of contents ..
Backing up System:
  Volume Groups " rootvg"
  Start date is Thu Aug 30 02:05:46 EDT 2012
  User is root at sungardalb
  Estimated size is 4107 MB

Backing up / filesystem ..

Backing up /usr filesystem ..

Backing up /admin filesystem ..

Backing up /commvault filesystem ..

Backing up /home filesystem ..

Backing up /opt filesystem ..

Backing up /s filesystem ..

Backing up /s/s2 filesystem ..

Backing up /s/seclib filesystem ..

Backing up /tmp filesystem ..

Backing up /users filesystem ..

Backing up /users_archive filesystem ..

Backing up /var filesystem ..
backup: 0511-089 Cannot open ./tmp/slp_srvreg.lock: Cannot open or remove a file containing a running program.

Backing up /var/adm/ras/livedump filesystem ..

Backing up /var/adm/ras/platform filesystem ..

Backup ended Thu Aug 30 02:18:41 EDT 2012
4109 megabytes written to 1 volume.

WARNING: System backup completed with non-fatal errors.
0
 
woolmilkporcCommented:
This error is quite common and harmless.

/tmp/slp_srvreg.lock is always held open by the slp_srvreg daemon, which is the Service Location Protocol Agent, part of the Tivoli Management Agent.

The file in question does by no means have to be contained in the backup, thus this error can safely be ignored.

Congrats on making the magic work!
0
 
compdigit44Author Commented:
Is there anyway I can skip this file from being backed up?
0
 
compdigit44Author Commented:
Also when I try to run sysback using smit and select the backup system image option. I keep getting the following error...


The "mp" kernal type is invalid or support for this kernal is not installed???

Unable to create boot tape.
0
 
woolmilkporcCommented:
Create an Exclude List.

smitty sysback -> Configuration Options -> Exclude lists -> Add a File

Accept the default list name (/usr/lpp/sysback/.exclude_list).

Under "File or directory name to add" specify the filename exactly as it appeared in the message without the leading dot:
/tmp/slp_srvreg.lock  

Specify the name of this list using the "-E" flag of the sysback command.          
       
That's it.
0
 
woolmilkporcCommented:
Yes, the "mp kernel" thing is a known bug in the smit scripts.

It is solved in 6.1.3, a version which you're not able to install because of the missing 6.1.0 license.

So you will have to live with the fact that you cannot start "backup system image " via smit. You will have to use the commandline.

This is the bug report:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC59774
0
 
woolmilkporcCommented:
I just noticed, specifying the "-E" flag of sysback to indicate the name of the exclude list is not required when using the default file /usr/lpp/sysback/.exclude_list!
0
 
compdigit44Author Commented:
I check my system and I do not have a .exclude_list file present. I didn't have one on my old AIx 5.3 server so I'm not sure why this is an issue with 6.1
0
 
woolmilkporcCommented:
The SLP agent came with AIX 6.1. AIX 5.3 doesn't have it.

And of course you don't have an exclude list yet. I told you how to create one using smit.
0
 
compdigit44Author Commented:
I'm sorry for the stupid question but how do I create an exclude list via smit if I cannot run a back using smit?
0
 
woolmilkporcCommented:
You can do almost everything with "smit sysback" except for "backup system image"
which must be done via commandline.
0

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

  • 13
  • 12
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now