New answers tagged rman
Yes, it is. BACKUP ARCHIVELOG ALL DELETE ALL INPUT; See: Deleting Archived Redo Logs After Backups in non-CDBs Or you can use FRA and configure an archivelog deletion policy: CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DEVICE TYPE DISK'; This way when the FRA is getting full, the database will automatically delete already backed up ...
No. The rman command 'BACKUP FULL ...' makes a backup of the datafiles but does not backup any archivelogs. If you want to backup archivlogs you have to make an archivlog backup too. This can be done by adding the 'PLUS ARCHIVLOG' clause to the 'BACKUP FULL' command or by issuing a 'BACKUP ARCHIVELOG' command after the 'BACKUP FULL' command. Online ...
RMAN uses backupsets by default. The following commands will create a backup to a backupset: RMAN> backup database; RMAN> backup database plus archivelog; This is assuming that you haven't changed the default RMAN parameters: RMAN> SHOW ALL; ... CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP ...
I suppose that you looked at the Oracle site (http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmquick.htm)? If not then look here: http://www.thegeekstuff.com/2013/08/oracle-rman-backup/.
The method you describe is ok. This method was the backup method used before Oracle introduced RMAN and is still valid. It is still used by tools that do snapshot backups (like Netapp's backup tool for Oracle) and I often use this in similar situations. You also should make a controlfile backup if all the controlfiles are on these disks.
If you can create a snapshot of everything at the same time, you do not even need backup mode. Backup mode (User Managed Backup) is not deprecated, but RMAN is the preferred tool for making backups.
I would do a shutdown of the database to be sure that really nothing is written on the filesystem of the SAN. Do you have your archivelogs on the same filesystem? Restart it after you have made the snapshot. The alter database begin backup; is in the 11g documentation so it must be still valid (have not checked it for 12c). Do you make full backups with ...
As per compatibility matrix, the target and the RMAN client version has to be the same. The workaround is connect to the catalog database from the target database ( whose version is lower than that of the RMAN client) and register the database in the catalog. Thanks!
You must use the RMAN executable that is in the classpath that is used to run (or how would you say that) your database. That is the one from 11g. Just do .oraenv <database> to set the correct path and then execute rman.
Top 50 recent answers are included