You can set some Oracle database-related settings and backup policies. For example, you can set the concurrent data streams transmitted to the disk drive. You can set the degree of parallelism for disk backup Based on the CPU configuration of the database server. If there are several CPUs, You can appropriately improve the degree of parallelism; if you do not want Oracle to use the quick recovery zone as the disk backup location, you can set it to tell Oracle to place the backup in the specified disk backup location. You can select from three disk backup types: backup sets (an Oracle backup file format that inserts multiple backup files into one output file to achieve more effective backup) and compress backup sets (an Oracle backup set, the data is compressed to reduce the size) and the image copy (the database file can be restored as is ).
You can go to the Oracle backup configuration page from the "Backup Settings" tab under the "availability" tab of EM: Where, in disk settings or tape settings, the default degree of parallelism is 1, however, if the CPU resources of the local server are sufficient, you can increase the value of parallelism so that multiple CPUs can work at the same time, so as to concurrently transmit the backup to the storage media. Disk backup includes three backup types: Backup set, compression backup set, and image file. There are two backup types in tape backup: Backup set and compression backup set. BACKUP set and Image File: the BACKUP set is the logical entity generated by the BACKUP command. This command can generate BACKUP sets on disks or other storage media. Each backup set contains multiple physical files called backup pieces ). The backup slice uses the compressed RMAN format to store data. One of the advantages of backup sets is to save disk space for backup data files by compressing unused data blocks. The backup set only includes data blocks used in data files. The size of a backup slice is limited. If there is no size limit, the backup set is composed of only one backup slice. The size of the backup file cannot exceed the maximum file length supported by the file system. Image backup copies independent files (data files, archive logs, and control files), similar to file replication at the operating system level. The image backup records are created by RMAN or written to the RMAN database through Enterprise Manager, so that RMAN can use these copies during database backup and recovery. As long as the file is recorded in the RMAN database, you can restore it. RMAN can only back up images on disks. When you use the restore database statement to RESTORE data, RMAN uses the records in the DATABASE to select the backup data required for the Restoration Operation. The RMAN database is mainly stored in the control file of the database. Therefore, it is critical for RMAN to protect the control file. You can specify a copy of The RMAN database, which is stored in a solution called recovery catalog. The recovery catalog solution is located in an independent database, which can store metadata for multiple other databases. Oracle Em, When configuring backup and recovery, you need to call the resources of the local server. Therefore, you need to enter the authentication username and password of the local server's operating system to provide host identity authentication. Set the backup policy as follows: open "policy" under "Backup Settings" under "availability" in "EM" and automatically backup control files and server parameter files (spfiles) as each backup and database structure changes) this option can be selected, because the DATABASE Control file and the server parameter file SPFILE are very important for RMAN. When you use the restore database command to RESTORE the DATABASE, RMAN uses the records in the database to select the backup data required for the Restoration lock. The RMAN database is mainly stored in the control file of the database, therefore, Database Control Files and server parameter files are very important for RMAN and must be protected.