Optimization with a Logical Volume Manager 

If a Logical Volume Manager (LVM) is used, BRBACKUP can only save all files from a hard disk to tape if the logical volumes are not unnecessarily distributed over several hard disks (see configuration A).

Configuration A:

Each logical volume exactly corresponds to one hard disk (for example logical volume 1 = disk 1, logical volume 2 = disk 2, logical volume 3 = disk 3).

Configuration B:

Each logical volume is set up so that it covers areas of all the hard disks (for example logical volume 1 = area1.disk1+area1.disk2+area1.disk3, logical volume 2 = area2.disk1+area2.disk2+area2.disk3, logical volume 3 = area3.disk1+area3.disk2+area3.disk3).

Configuration A is more efficient than configuration B with respect to database backup. Configuration B, however, can provide a better performance for online operation of the SAP system.

If you plan the configuration of logical volumes for large databases, you should find a compromise for the options which meets your requirements. You should consider which is more important: a more effective backup or higher performance of the online operation of the SAP system.

Some notes on this point:

Disadvantages of using an LVM: performance loss through management overhead and possible (configuration B) deterioration of optimization through BRBACKUP