During the backup, SnapDrive will attempt to quiesce the file systems and LUNs to acheive a consistent state for the snapshot. In the event that it is not able to do this within the timeout period, SnapDrive will then create individual snapshots on the volumes. This is why you see three snapshots for the same volume. The "p" refers to partial, as it is a partial backup of the database. The "f" is for full.
This happens because you have invalid storage layout, (e.g.. LUNs with various Oracle files in the same volume) which is forcing SMSAP to create several snapshots for the same volume.
You can verify that by selecting the hot-backup in SMSAP GUI , selecting "override" mode (to force so called "fast restore via snapshots") and then doing restore. It is going to probably to fail rendering your SAP enviorniment useless, but you might have chance to do the default SMSAP restore, but then it is going to be long (AKA file-based copy restore).
Customer is using brbackup and brarchive to do the backup.
For the f_h_* related snapshots, in the TR3823, SnapManger for SAP 3.0 Best Practices, on page 25, there is the explanation about those two snapshots.
The following example shows two Snapshot copy names created for the datafiles volume and the control files volume. The second Snapshot copy listed has “_f_h_1_“ in the middle of its name. The "1" indicates that it is the first Snapshot copy created in the backup set. The first Snapshot copy listed is the most recent and has a "2," which means it is the second Snapshot copy created. The "1" Snapshot copy includes the datafiles; the "2" Snapshot copy includes the control files. Because the control file Snapshot copy must be created after the datafile Snapshot copy, two Snapshot copies are required.
Those three p_h_* snapshots should be generated by brarchive, but why there are 3 snapshots? Anybody knows that?
I can't say exactly why there were three snapshots created. I think Jakub is correct that the storage layout may not be in line with best practices, which can make it difficult for SDU to quiesce the file systems within the window necessary to create a consistent backup. As a result, it defaults to doing partial backups of the volume and quiescing only a portion of the file systems each time.
Please review the documents I mentioned in an earlier reply to see if your storage layout could be the culprit.