Jim,
 
I have completed the following on the DR box:
1.Set up Media Class-Have copied this from prod as I have to set this up on DR on which prod replicates
2.Set up Media Policy-Have copied this from prod as I have to set this up on DR on which prod replicates
3.HAve copied SAVFULL control group from Prod since business requires full system save of DR every day
4.Set up BRSMAINT to run every day after backup using option 8 against control group SAVFULL and set it to *YES
5.Changed the attributes of SAVFULL on DR and made it similar to Prod
6Using WRKDEVBRM verified the config of Prod and DR are same.

Is there anything else I need to set up to get BRMS going.
 
I would once again like to thank you and Rhishabh for all your efforts in guiding me
 
Darrell

--- On Tue, 7/9/10, Jim Oberholtzer <midrangel@xxxxxxxxxx> wrote:


From: Jim Oberholtzer <midrangel@xxxxxxxxxx>
Subject: Re: Fw: Re: BRMS Set Up
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Tuesday, 7 September, 2010, 1:06 PM


  Darrell:

I just noticed I missed on small step.  On you control group use option
8 to change the the media policy for full and incremental back ups to
use the new one you just created, DAILY in the case cited below.  I
suggest cumulative type to be *CUML and if you use save while active as
in the example below, change the "Sign off interactive users" to *NO.   
Save Access Paths, contents of save files and journaled objects should
all by *YES in my opinion.

Also for my example below, create a message queue in QGPL called
BACKUP.  All the back up messages will go there for save while active
check points etc.

A little time spend in this area of the control group along with getting
the system policy and the back up policies set up properly will pay back
your time spend very quickly the first time you need to do a recovery.

There are a couple of good redbooks out on BRMS and the BRMS manual is
also one of the better ones IBM has put out.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 9/7/2010 7:42 AM, Jim Oberholtzer wrote:
    Darell:

Sorry for the delay, work and holiday.  All answers at V5R4 so they
apply most anywhere.  Some of the options have changed slightly to V6 and V7

1)  Under BRMS main menu, go to Media Management.  Option 1 work with
media classes.  This will set up the density of the tape volumes you are
using.  In my case *ULTRIUM1 (LTO 1 at my home office).  Next back out
and go to Media policies.  (Option 11, then 7 from the main BRMS menu)
Here create or change a media policy.  I use one called DAILY.  I
suggest you set the retention type at 2-Days.  Set the retain media to
one less than the number of days you want the tape rotation to be, so if
the tape rotation is 3 weeks you need to use 21 - 1 = 20.  That way on
the 21st day the tape will have been expired by BRMS maintenance the day
before and it will be ready for use.  Be sure to change the text to
something meaning full, like "3 Week Rotation" or "21 Day rotation".

2)  You can certainly use *SYSTEM control group if you want, that does a
full "21 save" every time it runs, but I think that might be overkill.
Consider doing a *SYSTEM once a month, and use a custom control group
for the balance of your daily saves.  A full save every weekend with an
incremental every day.      Consider creating  control group called
DAILY (notice the same name as my media class and policy) Have it look
like:

Group . . . . . . . . . . : DAILY
    Default activity  . . . . . FIIIIII
    Text  . . . . . . . . . . . Daily (no Domino)

    Type information, press Enter.

                            Auxiliary   Weekly    Retain  Save      SWA
          Backup      List  Storage     Activity  Object  While     Message
    Seq   Items       Type  Pool Device SMTWTFS   Detail  Active    Queue
                                        ·······
      10  *EXIT                         *DFTACT
      20  *SAVSECDTA                    *DFTACT   *NO
      30  *SAVCFG                       *DFTACT   *NO
      40  *ALLUSR           *SYSBAS     *DFTACT   *OBJ    *YES      BACKUP
      50  *LNKOMTLTS        *ALLAVL     *DFTACT   *YES    *YES      BACKUP
      60  *ALLDLO                       *DFTACT   *NO     *NO

    Now you have a full copy of all your user data ever Sunday with an
incremental Monday through Saturday.  ( I hope the formatting stayed in
place, I changed the font so it might)

3)  You can copy the BRMS maintenance job from another partition to this
one, but make sure the BRMS maintenance runs every day after the save is
complete.  One way to do that is use option 8 on your new control group
and scroll down to the bottom of the options.  You will find:
    Run maintenance after backup . . . . . . *NO

Change it to *YES and the maintenance will be submitted for you as soon
as the control group finishes.


Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 9/6/2010 11:53 AM, Darell Wheeler wrote:
  Can anyone please help me with my below request.
 
  Many Thanks
  Darell

  --- On Sat, 4/9/10, Darell Wheeler<darellwheeler@xxxxxxxx>   wrote:


  From: Darell Wheeler<darellwheeler@xxxxxxxx>
  Subject: Re: BRMS Set Up
  To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
  Date: Saturday, 4 September, 2010, 3:38 PM







  Hi Jim,
 
  Please help me with the following:
 
  1.How do I set up the media classes so the expiration dates would work properly?
  2.The daily backup will actually be a full system backup.Does this mean that the System policy and back up policy should be the same as that which exists in the production for which the full system backup is already running.
  3.BRMS Maintenance job runs on other partitions.Can I copy this BRMS Maintenence job and set it up on this partition to run after the backups
 
  Kindly advice
 
  Darell

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.