Netbackup for lotus Notes- circular Trans_Style Enabled- Failing with status code 90

[nbkpadm]

Greetings

Please assist to fix a Transaction log (Circular) backup failure in NetBackup for Lotus Notes.

Issue:

Master & Media Server - NBU 7.5.0.7 , OS - win 2008 R2

Client - NBU 7.5.0.7, OS - Win 2008 R2

Client is installed with Netbackup for lotus notes agent. The transaction log backups are failing with error code 90. Transaction logs style : Circular is enabled lotus end

Detailed status shows the following msg

Analysis & Troubleshooting done:

Reffered to Article:TECH19310 and was in an impression that the transaction styling has to be archival for the successful Backup. But referred the Netbackup admin guide for lotus and found that the archival transaction style is required for incremental backups. Linear & Circular Transaction styles are supported for full backups. But in our environment full backups are also failing with error : status: 90: media manager received no data for backup image 

Detailed status shows: WRN - Transaction Log backup was requested but Archive Logging is not configured (0x0).

Not sure why netbackup is not detecting the trancation style as circular while the Trans_style is mentioned as 0 (circular) in lotus.ini file

Referred TECH164221 and verified the exclude list.    *.txn files are not excluded.

The full backups were getting successful and this issue has started few days ago and now the transaction log backups are failing for all clients. No recent activity has been performed in the client or server end recently. The FS backups are successful in the client. Please assist.

[Marianne · Accepted solution]

I see the following in NBU for Lotus Notes Admin Guide:

Circular:
When you enable circular-style logging, the transaction log
extents are reused as the size limit of the log file is reached.
The reuse saves resources, but limits your recovery options.
Transaction log extents are not backed up by database agent
when circular-style logging is enabled. Therefore, you can
only recover logged Lotus Notes databases to the point in
time when the transaction log extents were overwritten.

Archive:
When you enable archive-style logging, transaction log
extents are generated as needed and are limited in number
only by the capacity of your mass storage. Archive-style
transaction log extents must be backed up, unlike
circular-style and linear-style transaction log extents, which
cannot be backed up. They can be used as the incremental
backup for all logged databases. Backups of the archive-style
transaction log extents ensure that the transaction log
extents are marked as available to be recycled. These
backups also prevent your mass storage from filling up.
Unlike circular-style and linear-style logging, archive-style
logging does not limit the point in time to which a database
can be recovered. With archive-style logging enabled, a
logged database can be recovered to any point in time. This
time can be any time between when the database itself was
last backed up to the current time.