IBM i Global

IBM i 

A space for professionals working with IBM’s integrated OS for Power systems to exchange ideas, ask questions, and share expertise on topics like RPG and COBOL development, application modernization, open source integration, system administration, and business continuity.


#Power


#IBMi
#Power
 View Only
Back to discussions
Expand all | Collapse all

BRMS - Network - data synchronisation update / Question.

  • 1.  BRMS - Network - data synchronisation update / Question.

    Posted Wed January 22, 2025 09:18 AM

    All,

    Having an environment (PowerHA with iASP + Flashcopy), which I have to move with a full system save/ restore process ...

    I have my source lpar with IASP, my target lpar (to switch to), and I have my FC lpar within a cluster env, and as well all 3 integrated in a BRMS network.

    On the FC lpar, I'm using the BRMS function HSTUPDSYN (CALL QBRM/Q1AOLD PARM('HSTUPDSYNC' '*ADD' 'SYSTEM' 'NETWORK ID' 'IASPNAME' '*CHGSYSNAM')) to arrange the backup data from the FC lpar gets well synchronized to the Source Lpar, and BRMS will generate save history owned by the source lpar, while in fact the FC lpar executed the backup operation. 

    With this setup ... my full recovery with STRRCYBRM can restore sysbase & iasp libraries / Dir ... without requiring an IP-connection to the FC lpar (where the backup was executed, and who owns still the volume). In fact, it looks like this backup of the IASP was done on the source lpar....

    A few questions regarding this BRMS feature ...

    • Using /implementing this HSTUPDSYN feature with *CHGSYSNAM now ...
      • this approach will be applied with the next synchronisation (new backup data...) ?
      • Existing save history (and already synchronized) will not be updated ?
    • Executing the sysbase save operation on the source lpar, and afterwards (or in parallel) the FC save operation through the FC lpar
      • Afterwards, the BRMS data (qusrbrm) on the source lpar needs to be updated with the last save operations of my FC Lpar. In fact, the save history of the FC lpar needs to be synchronized towards the Source lpar
        • so, after these save operations I have to re-open these servers to allow this BRMS data synchronisation.
        • Any process, through which I can validate that the whole save history of the FC lpar is well synchronized to the source lpar ?
          • or should I validate by checking some libraries on the source lpar  (WRKMEDIBRM  LIB(xxxx)  SYSTEM (*LCL)  and the last FC save operation should be well presented.
        • Of course, this requires on the source lpar that I make a new backup of the QUSRBRM library to catch all backup information. (probably on source & FC lpar ?) to be used in my full system recovery process . Is my view right ?

    Kind regards,

    Jos



    ------------------------------
    Jos (Jozef) Thijs
    Kyndryl Belgium
    ------------------------------


Related Content