If you do create an archivelog deletion policy, they can be deleted after you meet the requirements in the policy. Or the logs are obsolete according to the backup retention policy. You can define your archivelog deletion policy in RMAN. If there is no archived redo log deletion policy in RMAN, the files can be deleted when backed up at least once to disk or SBT. You do not need 3500 GB for each instance. So, in this case, you would use a maximum of 3500 GB on the +RECO disk group for the database. You can check the configuration by looking at two parameters. How much archivelog do you want to keep on disk?.How do you want to use flashback database?.How long do you need to keep your backups?.
#Dbz space drop rates windows#
Flash Recovery Area needsīefore you start configuring your FRA sizing, you need to define your own needs for the recovery windows and retention time. The FRA size is set with only one parameter for all file types together, but we can do some calculations on the size needed for individual file types. Main file types are archivelog, flashback log, backups, as well as mirrors for your control files and redo log files.Īll files in the FRA are Oracle-managed files. Using a Flash Recovery Area simplifies the administration of your database by automatically retaining them for as long as they are needed for restore and recovery activities, and deleting them when they are no longer needed, because the space is needed for another backup and recovery-related purpose. In the Oracle database, the Flash Recovery Area or FRA is a location on disk where the database can create and manage several kinds of backup and recovery-related files.
0 kommentar(er)
