On the initial overview screen I am seeing a notice about 5 incomplete backups.

What defines a backup as "Incomplete"?  

What am I supposed to do with this information?  Most of these are much older than our tape retention.  The oldest is over a decade old.

These are all old enough that the VIEW BRMS LOG is fruitless.wrk

The underlying SQL is 

SELECT
  CONTROL_GROUP,
  TYPE,
  SAVE_START,
  SAVE_END,
  BACKUP_MINUTES,
  OBJECTS_SAVED,
  SAVE_STATUS
FROM
  QUSRBRM.CG_STATUS
WHERE
  SAVE_STATUS = 'INCOMPLETE'
ORDER BY
  SAVE_END DESC

------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
------------------------------

#BRMSfori

I wonder what your log retention is set to.....in any event - here's a link to the doc that explains the "incomplete" 

QUSRBRM.BACKUP_STATUS view SQL service - IBM Documentation

As far as "what to do" - nothing if you don't care about it :-) 

if you have recent saves that are showing incomplete - might need to refer to the job log of the backup to see why the backup is not able to save all objects. (i.e - object locks, commits, etc)

------------------------------
Rich Malloy
------------------------------

Incompletes show up as *QUAL on PRTRPTBRM.  Some of those entries are quite dated.  One run with *QUAL is over a decade old and the media is gone (we changed VTL models since then).

IBM/Fortra is saying this:

• When using PRTRPTBRM TYPE(*CTLGRPSTAT) the following entries change:

  • Entries with a Save Status of *NOERR or *QUAL are removed one year after the backup history expires, even if the media has been reused.

  • Entries with a Save Status of *ACT are changed to *ERROR if the job no longer exists.

  • Entries with a Save Status of *ERROR or *CANCL are removed after 30 days.

    That doesn't seem to be happening.  I'm still working with them on this.

    https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/165642258/Backup+Control+Group+Status+Report

------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
------------------------------

Original Message:
Sent: Fri January 17, 2025 03:46 PM
From: Rich Malloy
Subject: GUI: Incomplete backups

I wonder what your log retention is set to.....in any event - here's a link to the doc that explains the "incomplete" 

QUSRBRM.BACKUP_STATUS view SQL service - IBM Documentation

As far as "what to do" - nothing if you don't care about it :-) 

if you have recent saves that are showing incomplete - might need to refer to the job log of the backup to see why the backup is not able to save all objects. (i.e - object locks, commits, etc)

------------------------------
Rich Malloy
------------------------------

Took a Teams meeting to get this resolved.  Some of the old entries were due to the way we migrated VTL devices some years ago.  We got that all cleaned up.

There is still one Incomplete backup due to other reasons.  The backup was from 2023-02-09.  The tapes were expired a year later.  And even though the tapes have since been reused, etc, it will keep this record of Incomplete backup for a year after the tapes expired from this backup. So, roughly 2025-02-09.  Seems odd, but as the one guy explained, some LUG customer explained their need for such retention.  To me, that just gets you numb to "Incomplete backups".

------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
------------------------------

Original Message:
Sent: Fri January 17, 2025 03:57 PM
From: Robert Berendt
Subject: GUI: Incomplete backups

Incompletes show up as *QUAL on PRTRPTBRM.  Some of those entries are quite dated.  One run with *QUAL is over a decade old and the media is gone (we changed VTL models since then).

IBM/Fortra is saying this:

• When using PRTRPTBRM TYPE(*CTLGRPSTAT) the following entries change:

  • Entries with a Save Status of *NOERR or *QUAL are removed one year after the backup history expires, even if the media has been reused.

  • Entries with a Save Status of *ACT are changed to *ERROR if the job no longer exists.

  • Entries with a Save Status of *ERROR or *CANCL are removed after 30 days.

    That doesn't seem to be happening.  I'm still working with them on this.

    https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/165642258/Backup+Control+Group+Status+Report

------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
------------------------------


Original Message:
Sent: Fri January 17, 2025 03:46 PM
From: Rich Malloy
Subject: GUI: Incomplete backups

I wonder what your log retention is set to.....in any event - here's a link to the doc that explains the "incomplete" 

QUSRBRM.BACKUP_STATUS view SQL service - IBM Documentation

As far as "what to do" - nothing if you don't care about it :-) 

if you have recent saves that are showing incomplete - might need to refer to the job log of the backup to see why the backup is not able to save all objects. (i.e - object locks, commits, etc)

------------------------------
Rich Malloy