Oracle Database Administration from Zero to Hero - Practice - Configuring RMAN Persistent Settings

This video tutorial covers the configuration of RMAN persistent settings, focusing on setting the retention policy and modifying the default format of RMAN backups. The tutorial demonstrates how to configure the retention policy to redundancy 2, take multiple backups, and manage obsolete backup files. It also explains how to change the default backup location for disk channels and verify the changes. The session concludes with a summary of the practices performed.

What is the default RMAN retention policy setting?

• Redundancy 4

• Redundancy 1

• Redundancy 2

• Redundancy 3

What happens to backups that exceed the RMAN retention policy?

• They are moved to a different location

• They are archived

• They are marked for deletion

• They are compressed

How many times should the user tablespace be backed up to test the new retention policy?

• Three times

• Once

• Twice

• Four times

What is the effect of changing the default format of disk channels?

• It changes the backup location

• It compresses the backup files

• It encrypts the backup files

• It changes the format of SPT device channels

Where are backup files saved after clearing the persistent setting?

• In the cloud storage

• In the shared folder

• In the FRA

• In the local disk

What does the run block do in the context of RMAN?

• It encrypts the backup files

• It compresses the backup files

• It deletes all backup files

• It allocates a channel and sets its format

What should be done as a cleanup after executing the run block?

• Encrypt the backup files

• Delete the produced backup set files

• Compress the backup files

• Move the backup files to a different location