IBM Support

Unmount User-Defined File Systems in BRMS

Troubleshooting


Problem

This document discusses the option to unmount user-defined file systems (UDFS) within a BRMS control group.

Resolving The Problem

The unmount user-defined file systems option can be viewed in the BRMS control group attributes; however, it can only be changed using the BRMS GUI plug-in (iNavigator or Web Director). The available settings are *YES or *NO. Changes can be made using the GUI by right-clicking on the control group, selecting Properties, and then selecting the What tab. At the bottom of the screen will be a checkbox:

Unmount UDFS option within BRMS GUI.

Check the box for *YES; uncheck the box for *NO.

This option enables you to unmount user-defined file systems (UDFS) before the control group runs. You must unmount the UDFS in order to save the objects in the directories upon which these file systems are mounted. If you do not unmount a UDFS, the objects in the UDFS are saved as if they are in the directory upon which it is mounted, and the objects actually in the mounted over directory are not saved. For example, the mount over directory for the UDFS is /UDFSname. When the UDFS is unmounted, objs /UDFSname/a, /UDFSname/b, etc. are seen. When you mount the UDFS over directory /UDFSname, objects a and b are no longer able to be accessed or saved. You also lose all information about the UDFS and the disk pool in which it is stored. If you select this option and there are no backup items that include directories, no unmount will occur.

Notes:
  1. In IBM i 6.1 and above, if the Unmount user-defined file systems field is set to *YES for a control group, after a backup finishes BRMS will attempt to re-mount any file systems that were unmounted before the backup began.
  2. This setting will be ignored if no IFS backup items exist within the control group.
  3. The unmount will occur directly before the IFS backup item.

How this option affects iASPs and user ASPs

By setting this option to *YES, BRMS will unmount all file systems including the UDFS on the iASP and any user ASPs.  Because BRMS will not remount when the save completes, this causes the IFS mount point to be deleted, and objects in the UDFS on the iASP or user ASP are not viewable from WRKLNK '/<asp>' even if the iASP is in a varied on state.  A remount following the save completion is required to access the objects in the UDFS on the iASP or user ASP.  Here is an example mount command for iASP or user ASP:

MOUNT TYPE(*UDFS) MFS('/dev/<asp>/QDEFAULT.UDFS') MNTOVRDIR('/<asp>')

The above MOUNT command must be executed after the IFS portion of the save (*LINK or *LNK list). A simple approach is to add the MOUNT command to the last *EXIT of the control group.

Additional information:
If you have added the MOUNT as a BRMS *EXIT or you have issued the MOUNT from the command line, you should review the JOBLOG to verify that the MOUNT completed successfully. If the MOUNT failed to complete or if you neglected to save the JOBLOG, you may consider a VARY OFF and VARY ON of the iASP. If after the MOUNT, the data is not accessible using the WRKLNK or other command provided by a software vendor, the also consider a VARY OFF/VARY ON of the iASP. If none of this resolves the problem, you should consider contacting the appropriate support team (in other words, FLASHCOPY, iASP, or IFS).

Also for more information see the BRMS Wiki Backup of integrated file system objects
NOTE:  At V7R2 and V7R3 see the link below for options to change the unmount attribute settings from the green screen. 
Change GUI Only Control Groups Attributes

At V7R4 you can change the unmount settings in the green screen control group attributes.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CN8AAM","label":"Backup Recovery Install Migration->Install or Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0"}]

Historical Number

589368223

Document Information

Modified date:
28 March 2022

UID

nas8N1011723