SAP online/archive backup groups are failing

[JohnPlayerSpecial]

Groups are failing with error message:[host]:backint:SID: Backup failed. Could not execute brbackup/archive. Actually regarding SAP backup logs backups are succesful but for some reason groups are failing. There is no errors on logs located in /nsr/applogs or any other SAP related logs. Only daemon.log has that "could not execute brbackup/archive

 

[605]

So if the backups run fine, you most likeley will not find the problem in the SAP logs if this runs fine. Look at your group's details or open the savegroup completion report (usually a mail to root).

 

[JohnPlayerSpecial]

That "Could not execute brbackup/archive" is from Group details. That's the only error it will give. No errors in SAP or /nsr/applogs. Still all groups with this specific client are failing and those failures will produce lot of false alerts which I have to handle every day.

This is running on Solaris 9 witn nmsap3.0 module. The configuration is exatly the same as in other SAP instances.

 

[hoinz]

Which version of brbackup/brarchive?
There are problems with 6.40
6.20 works well for me.

 

[JohnPlayerSpecial]

It's 6.40. Those clients with 6.20 are running ok.

 

[JohnPlayerSpecial]

Do you have more information about these problems? Legato bulletins or any other information. Thanks in advance.

 

[hoinz]

Hi,

I encountered the same problem with brtools 6.40.
In January I was told by a Legato consultant that Legato currently does not support 6.40. I don't know if this has changed by now.
It is a compatibility issue. Legato will have to develop a new backint program. I haven't any information on when this might be available.
However 6.40 works well even with Legato, as you can see in SAP's transaction DB12. Only problem is that Legato misinterprets return codes, as SAP changed them.

For instance, in 6.20 you have this:
BR232I 6 of 6 files saved by backup utility

whereas in 6.40 it reads:
BR0232I 6 of 6 files saved by backup utility

regards

 

[JohnPlayerSpecial]

Thank you very much for the information. This helps a lot since now we now it'a bug not configuration issue.

I don't know much about programming but I hope Legato will give us the new version soon since problem is very strict. I will install at least 10 new instances next two months and you can guess how many false alarms we have after that...