Show TOC

util_vol_unitLocate this document in the navigation structure

This parameter defines the smallest disk storage unit to be considered as a disk volume for backups with util_vol.

util_vol_unit = disk_vol|sap_data|all_data|all_dbf
         

Possible values:

  • disk_vol: specifies that the smallest unit is a logical volume, file system, raw disk , or disk drive. This value is used when a snapshot or clone is created at logical-volume level, and the volumes are mounted on the subdirectories of the sapdata directories, as in the following example:

    Example

    /oracle/SID/sapdata5/fact_1/fact.data1

    is located on a separate file system, which is mounted on:

    /oracle/SID/sapdata5/fact_1

    Caution

    This is allowed but does not conform to SAP conventions.

  • sap_data: specifies that the smallest unit is a sapdata, sapraw, origlog, or mirrlog directory This value is used when a snapshot or clone is created at logical-volume or volume-group level, and the volumes are mounted on sapdata, origlog, or mirrlog. This means that the disk configuration is such that all the directories sapdata, origlog, or mirrlog are mount points that can be separately and independently split. If the split is done on volume-group level, only one logical volume can be created for each volume group.

  • all_data: specifies that the smallest unit is all sapdata, sapraw, all origlog, or all mirrlog directories. This value is used when many or all sapdata directories are located on logical volumes belonging to the same volume group and the split can only be performed at volume group level. With this configuration, origlog and mirrlog directories must be on separate volume groups. Therefore, in this category there are at least three volume groups.

  • all_dbf: specifies that the smallest unit is all database files. This value is used when all sapdata and all origlog and mirrlog directories are located on a single volume group and the volume group as a whole can be split. This means that there is only one split for all database files.

    Caution

    This is allowed but does not conform to SAP conventions because it contradicts the SAP recommendation on the separation of data files and redo log files.