Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SRT creation failed for kernel version reason

Created: 07 Oct 2012 | 5 comments

Netbackup version: 7.5

The creation of SRT worked fine with dvd whom solaris kernel version is the one used to install netbackup software.

While performing Prepare To Restore, I got the following warning:

[Info] V-126-78  WARNING: The kernel versionof the SRT, 'Generic_142909-12', is not the same as the kernel version of the client , ''Generic_147440_12'

Using another dvd containing the same kernel version as the client, to create SRT, we got the following message:

Enter a [hostname:/]pathname containing a suitable Solaris 5.10
OS CDROM or OS image location [/cdrom/cdrom0] : /mnt
[Error] V-125-802 Boot server with kernel version(Generic_144488-08) can not hos                        (error message strangely truncated ?!)

I understood that the kernel version of the client is Generic_147440-12, so higher than the netbackup server.

Is it possible to prepare and make restore with BMR for this client without any bad impact on it.

Should we upgrade Solaris in Netbackup server every time we may upgrade the clients.

Thanks for your help.

Comments 5 CommentsJump to latest comment

mandar_khanolkar's picture

Hi,

>> [Info] V-126-78  WARNING: The kernel versionof the SRT, 'Generic_142909-12', is not the same as the kernel version of the client , ''Generic_147440_12'

This is a warning message indicating BMR SRT is based upon lesser or greater version of kernel than the client solaris kernel level which is being restored.

There is very very little risk associated in BMR restore failure due to little kernel matching problem. But BMR just flags this as warning to user.

In your case it is absolutely fine where SRT kernel is more than your client. Please proceed with the client recovery.

>> Should we upgrade Solaris in Netbackup server every time we may upgrade the clients.

No, server solaris version need not to be upgraded due to client OS upgrade. Though you may need to create a different new BMR SRT with latest Solaris OS (same used to install OS on client) in case any older SRT is failing to restore client.

Thanks.

Mandar

 

eomaber's picture

Hi,

>> [Info] V-126-78  WARNING: The kernel version of the SRT, 'Generic_142909-12', is not the same as the kernel version of the client , ''Generic_147440_12'

In my case SRT kernel is less than my client.

When I tried to create a new BMR SRT with latest Solaris OS that exists in the client, I got an error:

[Error] V-125-802 Boot server with kernel version(Generic_144488-08) can not hos

The error text was truncated for unknown reason.

I understood this version (Generic_144488-08) is the kernel version of Netbackup server. So, SRT (Boot Server) and Netbackup are of different version. How this could happen. Is SRT the previous version of the client before the client has been upgraded.

I read this in Symantec documentation: "For NBU 7.X, Boot Server software is installed with client software installs. As such, any patch updates will automatically update both the client and Boot Server software".
How this is done: automatically or need to run acommand to do so.

Thanks

mandar_khanolkar's picture

Hi

>> [Info] V-126-78  WARNING: The kernel version of the SRT, 'Generic_142909-12', is not the same as the kernel version of the client , ''Generic_147440_12'

My bad that i stated this vice versa. :-)

But i can tell you this is ok to proceed with bmr restore. If a restore test works then it is abosolutely fine to use this srt for recovery of this client or family of this client version.

BTW (Generic_144488-08) is kernel version of your solaris OS and not of netbackup.

thanks.

mandar

eomaber's picture

Hi

Let me try to restore as such and see. I will communicate the results later.

Thanks

Omar

 

Mark_Solutions's picture

There was a big change between Solaris 9 and Solaris 10 (or at least one the versions that came between them)

I believe the error should say that the BMR Boot Server can not host that SRT

You may well need an additional Solaris 9 (or early V10 - which ever matches that client) BMR Boot Server.

I have seen a similar issue before and due to a major kernel change that customer had to have an additional BMR Boot Server setup.

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.