× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is long so please bear with me.  We have 500 directories that store
all of our documents.  They are backed up with 5 separate control
groups, each one called by the previous one.  These have been running
for over a year.

These backups are started with this command:

 ===> SBMJOB CMD(STRBKUBRM CTLGRP(IFS100)) JOB(IFS100) JOBQ(TECH)
USER(QSYSOPR) CURLIB(*USRPRF) INLLIBL(*JOBD) LOG(4 00 *SECLVL)
LOGCLPGM(*YES) SCDDATE(021205) SCDTIME(0100)

             
WRKCTLGBRM shows:

Group . . . . . . . . . . : IFS100

Default activity  . . . . : FFFFFFF

Text  . . . . . . . . . . : (100) Image Documents on Shark DASD

 

                        Auxiliary   Weekly    Retain  Save      
      Backup      List  Storage     Activity  Object  While     
Seq   Items       Type  Pool Device SMTWTFS   Detail  Active    
  10  IFS100      *LNK  *ALLAVL     *DFTACT   *NO     *YES      
  20  *EXIT                         *DFTACT


And the EXIT is:
   Command . . . . . . . . . . SBMJOB CMD(STRBKUBRM CTLGRP(IFS200)) 
JOB(IFS200) JOBQ(TECH) USER(QSYSOPR) CURLIB(*USRPRF) INLLIBL(*JOBD) 
LOG(4 00 *SECLVL) LOGCLPGM(*YES)                          

===================================================================

Etc. through IFS500.  The Backup policy is APPEND(*NO) so each control
group uses a fresh tape.

===================================================================


WRKMEDIBRM LIB(IFS100) shows:

Saved                            Save   Volume       File    Expiration

Item             Date     Time   Type   Serial     Sequence     Date

IFS100          2/07/05  7:51:39 *FULL  603140 +          1    4/03/05

        (missing entries for all of January and 2/12/05.)

WRKMEDIBRM for IFS200, IFS300 and IFS500 shows the correct data

WRKMEDIBRM LIB(IFS400) shows:

Saved                            Save   Volume       File    Expiration 
Item             Date     Time   Type   Serial     Sequence     Date    
IFS400          1/01/05 16:26:21 *FULL  603037 +          1    2/25/05  
IFS400          1/08/05 16:53:32 *FULL  603180 +          1    3/04/05  
IFS400          1/15/05 17:10:27 *FULL  603077 +          1    3/11/05  
IFS400          1/23/05  7:48:50 *FULL  603117 +          1    3/19/05  
IFS400          1/29/05 22:24:40 *FULL  603068 +          1    3/26/05  
IFS400          2/12/05 22:37:07 *FULL  603008 +          1    4/09/05  
        (missing entry for 2/07/05.)

WRKMEDIBRM SLTDATE(021205 021205) shows:

Saved                            Save   Volume       File    Expiration 
Item             Date     Time   Type   Serial     Sequence     Date    
*LABEL          2/12/05  1:02:12 *FILE  603182 +          1    4/08/05  
QUSRBRM         2/12/05  8:11:15 *QBRM  603070            2    4/08/05  
IFS200          2/12/05  8:11:35 *FULL  603130 +          1    4/08/05  
QUSRBRM         2/12/05 15:08:57 *QBRM  603153            2    4/08/05  
IFS300          2/12/05 15:09:17 *FULL  603006 +          1    4/08/05  
QUSRBRM         2/12/05 22:36:23 *QBRM  603009            2    4/09/05  
IFS400          2/12/05 22:37:07 *FULL  603008 +          1    4/09/05  

The save on Serials 603182 and 603070 has a label of SAV20050212, DSPTAP
shows the same label, the joblog shows that control group IFS100 used
these tapes (and that the backup completed successfully.) 

On 2/07/05 I see the same thing for IFS400, Serials 603046 and 603053
have a label of SAV20050207, DSPTAP shows the same label, the joblog
shows that control group IFS400 used these tapes (and that the backup
completed successfully.) 

I called SupportLine and was told that "BRMS does not support running
BRMS commands from exits.  Unpredictable results may occur."  I pointed
out that these exits are actually doing a SBMJOB, but they were not sure
if that mattered.

This doesn't just affect WRKMEDBRM, my Recovery Reports from the week of
2/12 show the correct tapes for groups 200-500 but the 100 group tapes
on the report are from 2/07/2005.  My question/conundrum/rant is: If
BRMS does not know what it has on it's own backups how am I supposed to
use it for D/R?

Has anyone seen or heard of similar results from BRMS?

Regards,

Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.