Storage Management Foundation (SMF) Software
HP Storage Management Foundation (SMF) software manages many of the functions with regard to disk volumes and storage tasks. Managing storage pools can include the following tasks :
Changing the physical location of a file on a disk
Coping with disks that are full
Installing and populating new disk volumes
Making disk names independent of physical names
Determining efficient file placement for maximum performance
Once a virtual disk or volume is created, SMF software is transparent to the user .
AP-ADVICE-SMF-01 The SMF configuration and the management of SMF pools should only be performed by the SMF manager.
SMF accomplishes these tasks using the following concepts:
Location-Independent Naming
Location-independent naming means that a distinction now exists between a file's logical name and its physical name on HP NonStop servers. Previously, the file name has always indicated its physical location; that is, the name of each file indicated the node and physical volume on which the file was located. For example, the file name :
\NODEB.$DATA1.MYAPP.TOLLRDF identifies a file (TOLLRDF) that resides on a node named \NODEB, on a volume named $DATA1, on a sub- volume named MYAPP.
With SMF software, the file \NODEB.$DATA1.MYAPP.TOLLRDF can reside on any physical volume. With the exception of the node name, the name of a file managed by SMF software is independent of its location. SMF software controls the mapping of the logical name to the physical name. This strategy allows the physical name, which identifies the file's physical location, to change when a file is moved to a different location, while the logical name remains the same to applications and users.
Virtual Disks and Physical Volumes
A virtual disk appears to application programs to be a physical volume in almost all respects. The key difference between virtual disks and physical volumes is that, unlike a physical volume, a virtual disk does not correspond to a physical device.
Any number of virtual disks can be associated with any number of physical volumes. Files on virtual disks are not necessarily placed by SMF software on a single physical volume.
RISK Virtual disks can be changed or made unavailable more easily than a physical drive. They need to be actively managed to ensure that they are available as defined for applications and users.
AP-ADVICE-SMF-01 Virtual disks need to be actively managed to ensure that they are available as defined for applications and users.
Virtual disks can increase the performance of database access. Partitioning files across virtual disks can take advantage of certain performance enhancements of partitioned files.
Storage Pools
A storage pool is a collection of physical disk volumes managed by SMF software. All of the physical disks in a storage pool must be on the same system. Up to 6,144 physical disk volumes may be placed in a pool.
| Caution | A physical disk volume can be in only one storage pool at any given time. |
There is no fixed limit to the number of storage pools that can be created on a system. As the need arises, new storage pools can be created dynamically.
Mapping Virtual Files
Virtual disk files reside on a physical disk volume. SMF software maps the file labels. The physical tables are mapped from subvolumes residing on the physical disk using the naming convention ZYS<nnnnn>.
$DOC1.JAMES.PURGME 23 Jun 2003, 8:28 ENSCRIBE PHYSICAL FILENAME: $DATAE.ZYS00000.A0000DWK $DOC1 JAMES 92> fup info $DATAE.ZYS00000.A0000DWK $DOC1 JAMES 92 CODE EOF LAST MODIF OWNER RWEP TYPE REC $DATAE.ZYS00000 A0000DWK 101 108 08:27 222,230 NCNC
RISK Virtual files cannot be accessed from the physical disk file name, except from FUP for informational review only. Files can only be accessed using the virtual file name.
The components of SMF software are:
Master Process
Pool Process
SMF Catalogs
SMS Utilities
Virtual Disk Process
Master Process
The SMF master process manages a catalog of information required to coordinate SMF storage pools and virtual disks. The fixed name of the master process is $ZSMS.
Pool Process
Pool processes are responsible for collection and distributing information about physical volumes associated with a pool of virtual disks. Pool processes also keep statistical information about the pool.
SMF Catalog
SMF software maintains a catalog of information about pools.
SMF Utilities
The following utility programs can be used by the SMF manager:
| Utility Name: | Function: |
|---|---|
| RELOCSRV | Relocation utility to perform offline relocation |
| SMFIXUP | A powerful tool to perform maintenance tasks not otherwise easily performed. |
| SMREVERT | Component of SMFIXUP |
| SMREPAIR | Component of SMFIXUP |
RISK The SMF utilities should only be used by the SMF manager. Someactions may not be able to be recovered.
Virtual Disk Process
Virtual disks use a different disk process than physical disks. When virtual disk volumes are created by the operating system, the operating system starts a virtual disk process, $SYSTEM.SYSnn.OVDP, for each virtual volume. The name of this process is the disk name. See Gazette section on Disk Processes for more information.
Securing SMF Components
BP-PROCESS-OMP-01 $ZSMS process should be running.
BP-FILE-SMF-01 OMP should be secured "UUCU".
BP-OPSYS-LICENSE-01 OMP must be LICENSED.
BP-OPSYS-OWNER-01 OMP should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-01 OMP must reside in $SYSTEM.SYSnn.
BP-PROCESS-OPP-01 $POOLnn processes should be running.
BP-FILE-SMF-02 OPP should be secured "UUCU".
BP-OPSYS-LICENSE-01 OPP must be LICENSED.
BP-OPSYS-OWNER-01 OPP should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-01 OPP must reside in $SYSTEM.SYSnn.
BP-FILE-SMF-03 RELOCSRV should be secured "UUCU".
BP-OPSYS-LICENSE-02 RELOCSRV must be LICENSED.
BP-OPSYS-OWNER-02 RELOCSRV should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 RELOCSRV must reside in $SYSTEM.SYSTEM.
BP-FILE-SMF-04 SMFIXUP should be secured "UUCU".
BP-OPSYS-LICENSE-02 SMFIXUP must be LICENSED.
BP-OPSYS-OWNER-02 SMFIXUP should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SMFIXUP must reside in $SYSTEM.SYSTEM.
BP-FILE-SMF-05 SMREVERT should be secured "UUCU".
BP-OPSYS-LICENSE-02 SMREVERT must be LICENSED.
BP-OPSYS-OWNER-02 SMREVERT should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SMREVERT must reside in $SYSTEM.SYSTEM.
BP-FILE-SMF-06 SMREPAIR should be secured "UUCU".
BP-OPSYS-LICENSE-02 SMREPAIR must be LICENSED.
BP-OPSYS-OWNER-02 SMREPAIR should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SMREPAIR must reside in $SYSTEM.SYSTEM.
BP-PROCESS-TZSTO-01 $ZZSTO process should be running.
BP-FILE-SMF-07 TZSTO should be secured "UUCU".
BP-OPSYS-OWNER-01 TZSTO should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-01 TZSTO must reside in $SYSTEM.SYSnn.
BP-FILE-SMF-08 SMF Catalog files should be secured "NUUU".
BP-OPSYS-OWNER-03 SMF Catalog files should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-03 SMF Catalog files resides in $SYSTEM.<ZSMSPnn>.
If available, use Safeguard software or a third party object security product to grant access to the SMF subsystem files only to users who require access in order to perform their jobs.
BP-SAFE-SMF-01 Add a Safeguard Protection Record to grant appropriate access to the OMP object file.
BP-SAFE-SMF-02 Add a Safeguard Protection Record to grant appropriate access to the SMFIXUP object file.
| Discovery Questions | Look here: | |
|---|---|---|
| FILE-POLICY | Is SMF software used on the system? | Policy |
| PROCESS-OMP-01 | Is the $ZSMS process running? | Status |
| PROCESS-OPP-01 | Are the $POOLnn processes running? | Status |
| PROCESS-TZSTO-01 | Is the $ZZSTO process running? | Status |
| OPSYS-OWNER-01 | Who owns the OMP object file? | Fileinfo |
| OPSYS-OWNER-01 | Who owns the OPP object file? | Fileinfo |
| OPSYS-OWNER-01 | Who owns the TZSTO object file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the RELOCSRV object file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the SMFIXUP object file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the SMREVERT object file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the SMREPAIR object file? | Fileinfo |
| OPSYS-OWNER-03 | Who owns the SMF catalog and database? | Fileinfo |
| OPSYS-LICENSE-01 | Is the OMP object file licensed? | Fileinfo |
| OPSYS-LICENSE-01 | Is the OPP object file licensed? | Fileinfo |
| OPSYS-LICENSE-02 | Is the RELOCSRV object file licensed? | Fileinfo |
| OPSYS-LICENSE-02 | Is the SMFIXUP object file licensed? | Fileinfo |
| OPSYS-LICENSE-02 | Is the SMREVERT object file licensed? | Fileinfo |
| OPSYS-LICENSE-02 | Is the SMREPAIR object file licensed? | Fileinfo |
| FILE-POLICY | Who is allowed to manage SMF volumes on the system? | Policy |
| FILE-POLICY | Where is the SMF Catalog? | Policy |
| FILE-SMF-01 | Is the OMP object file correctly secured with the Guardian or Safeguard system? | Fileinfo Safecom |
| FILE-SMF-02 | Is the OPP object file secured correctly? | Fileinfo |
| FILE-SMF-03 | Is the RELOCSRV object file secured correctly? | Fileinfo |
| FILE-SMF-04 | Is the SMFIXUP object file correctly secured with the Guardian or Safeguard system? | Fileinfo Safecom |
| FILE-SMF-05 | Is the SMREVERT object file secured correctly? | Fileinfo |
| FILE-SMF-06 | Is the SMREPAIR object file secured correctly? | Fileinfo |
| FILE-SMF-07 | Is the TZSTO object file secured correctly? | Fileinfo |
| FILE-SMF-08 | Is the SMF catalog and database secured correctly? | Fileinfo |
Related Topics
Disk Processes
Securing Applications
SQLCI
