You can reduce long backup times by dividing the backup of the entire database into several partial backups.
Advantages
The partial backups can be carried out daily without time problems.
The database can be recovered at any time if the corresponding redo log entries exist. It is also possible to restore the entire database and then recover it.
Recovery after a media error (crash of individual hard disks) can be done quickly as only the files of the affected hard disks must be restored.
Disadvantages
Restoring the entire database takes as long as the total of all of the partial backups. This situation only normally occurs with logical errors (for example program errors or user errors). There is, however, a low probability of this happening.
It must be ensured that all database files were saved in a cycle of the partial backups. This is the responsibility of the database administrator. Backup at tablespace level (not at database file level, which is, in principle, possible), as BRBACKUP can then ensure that all files from a tablespace are backed up. Splitting extremely large tablespaces into several smaller tablespaces can be useful in this case (for example, extremely large tables could be put into separate tablespaces, and then backed up separately at tablespace level).
Partial Backups 