Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 1/59 RMAN ENHANCEMENTS

Transcription

1 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 1/59 RMAN ENHANCEMENTS

2 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 2/59 CONNEXION A RMAN RMAN target userid/password@base cible et non plus RCVCAT défaut nocatalog catalog nocatalog userid/password@base rcv log filename append filname

3 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 3/59 OBSOLESCENCE ET EXPIRABILITE Backup dit expiré si non trouvé suite à croscheck Backup dit obsolète si non désiré vis à vis des retention policy mises en oeuvre avec CONFIGURE RETENTION POLICY... obsolete NOMBRE DE JOURS : CONFIGURE RETENTION POLICY RECOVERY WINDOW OF n DAYS Par là, le DBA indique le point de retour dans le temps le plus ancien quil accepte. SYSDATE - (SELECT CHECKPOINT_TIME FROM V$DATAFILE) >= n Ce paramètre ne pose pas comme obsolète tout backup créé antérieurement à cette date Ce paramètre pose comme obsolète tout backup QUI NE SERVIRAIT PLUS A REVENIR A -n JOURS ( obligatoirement antérieur à cette date). Le FULL BACKUP IMMEDIATEMENT ANTERIEUR à date -n est donc de-facto NON OBSOLETE, ainsi que TOUTES LES ARCHIVES PRODUITES DEPUIS ce backup. obsolete REDUNDANCY : CONFIGURE RETENTION POLICY RENDUNDANCY n Par là, le DBA indique le nombre de versions de backup les plus récentes de chaque datafile, à considérer désirées. Cette valeur est prise en compte par loption de la commande BACKUP : optimization on qui neffectue le BACKUP que sil existe MOINS de n+1 backups IDENTIQUEs pour ce même device type.

4 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 4/59 LIST, CROSSCHECK, DELETE EXPIRED & CHANGE

5 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 5/59 CONFIGURE/ REPORT/ DELETE Désormais, il est possible de fixer des paramètres de configuration grace à configure retention policy to recovery window of nb days redundancy nbrecent Ces valeurs sont stockées dans le controlfile Les commandes report obsolete, report need backup peuvent se réduire à leur plus simple expression puisquil y a adoption des paramètres configurés de façon pérenne. Une nouvelle commande permet de supprimer physiquement les fichiers obsoletes, DELETE, QUI SE BASE SUR LES MEMES PARAMETRES QUE REPORT OBSOLETE. report obsolete subit quelques modifications : dans la syntaxe : recovery window of dans la couverture : affiche TOUS LES SUPPORTS DE SECOURS Backups datafiles Backup copies Archive logs Backups darchive logs

6 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 6/59 PREETABLIR LES PARAMETRES DE FONCTIONNEMENT DE RMAN : COMMANDE CONFIGURE Purpose To configure persistent settings affecting RMAN backup, restore, duplication, and maintenance jobs. These configurations are in effect for any RMAN session until the configuration is cleared or changed. Use CONFIGURE to set the following: An ongoing retention policy that automatically determines which backups and copies are eligible for deletion because they are no longer needed The device type (for example, DISK or sbt) for RMAN jobs The default number of channels of each device type that RMAN should allocate for automated backup and restore jobs The settings for automatic channels for a specified device type The maximum size of backup pieces and sets created on automatic channels Backup optimization either ON or OFF The exclusion policy for tablespaces in whole database backups The filename of the snapshot control file Filenames for files in an auxiliary database The control file autobackup feature to ON or OFF The default format for the control file autobackup output files RMAN uses default settings for CONFIGURE options. You can return to the default value for any CONFIGURE command by running the same command with the CLEAR option. Restrictions and Usage Notes Execute this command at the RMAN prompt. The target database must be mounted or open. Channels allocated with ALLOCATE CHANNEL override any configured automatic channels. RMAN does not simultaneously allocate automatic channels for multiple device types in BACKUP and COPY jobs. To direct backups or restores to specific channels, use the RMAN-generated channel names. If you specify channel numbers in the CONFIGURE CHANNEL command, then RMAN uses the same numbers in the system-generated channel names. If you configure channels by using the nondefault CONNECT or PARMS options to create backups or copies, then you must either use the same configured

7 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 7/59 COMMANDE SHOW POUR SE RENSEIGNER SUR LES VALEURS DE CONFIGURATION SHOW retention policy An ongoing retention policy that automatically determines which backups and copies are eligible for deletion because they are no longer needed device type The device type (for example, DISK or sbt) for RMAN jobs default device type The settings for automatic channels for a specified device type maxsetsize The maximum size of backup pieces and sets created on automatic channels auxname Filenames for files in an auxiliary database archivelog backup copies The default number of channels of each device type that RMAN should allocate for automated backup and restore jobs datafile backup optimization Backup optimization either ON or OFF snapshot controlfile name The filename of the snapshot control file exclude The exclusion policy for tablespaces in whole database backups controlfile autobackup The control file autobackup feature to ON or OFF ALL All parameters above

8 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 8/59 PREETABLIR LES PARAMETRES DE FONCTIONNEMENT DE RMAN : COMMANDE CONFIGURE CONFIGURE RETENTION POLICY CLEAR TO recovery window of redundancy none Nb Nbrecents days Défaut : redundancy 1 REPORT REPORT DELETE OBSOLETE NEED BACKUP OBSOLETE SAVOIR : retention policy préçise quel backup pourra être conservé pour combien de temps Si CONFIGURE est exécuté avec loption NONE, les commandes REPORT doivent spécifier tous les paramètres, sinon, il y a ERREUR.

9 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 9/59 RETENTION POLICY Specifies a persistent, ongoing policy for datafile and control file backups and copies that RMAN marks as obsolete, that is, not needed and eligible for deletion. As time passes, RMAN marks backups and copies as obsolete according to the criteria you specify in the retention policy. RMAN does not automatically delete any backups or copies: manually run the DELETE OBSOLETE command to remove obsolete files. By default, RETENTION POLICY is configured to REDUNDANCY 1. For backups, the basic unit of the retention policy is a backup set, not a backup piece. For example, BACKUP COPIES 4 TABLESPACE users generates a single backup set that is duplexed into four identical backup pieces. The retention policy considers this as one backup, not four separate backups. RECOVERY WINDOW OF integerdays Specifies a time window in which RMAN should be able to recover the database. The window stretches from the current time (SYSDATE) to the point of recoverability, which is the earliest date to which you want to recover. The point of recoverability is SYSDATE - integer days in the past. REDUNDANCY integer NONE CLEAR Specifies that RMAN should retain integer backups or copies of each datafile and control file. If more than integer backups or copies exist, RMAN marks these extra files as obsolete. Then, RMAN determines the oldest of the retained backups and copies, and marks all archived logs and log backups older than this backup or copy as obsolete. The DELETE OBSOLETE command removes obsolete backups and copies as well as archived log backups and copies. Disables the retention policy feature. RMAN does not consider any backups or copies as obsolete. Resets the retention policy to its default (REDUNDANCY = 1).

10 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 10/59 COMPORTEMENT REPORT OBSOLETE SANS ET AVEC LES DEFAUTS DE CONFIGURE REPORT OBSOLETE RECOVERY WINDOW OF Nb days BACKUP ou COPY obsolète si ne permet pas de REVENIR DANS CETTE PERIODE DE Nbjours ante REDUNDANCY Nbrecent BACKUP ou COPY obsolète si il existe AU MONS Nb backups ou copies plus récentes ORPHAN BACKUP ou COPY obsolete si appartient à des incarnations qui ne sont pas des ANCETRES DIRECTS de lincarnation actuelle IMPORTANT : RECOVERY WINDOW OF préçise une exigence de recovery dans cette période. IL DOIT DONC TOUJOURS EXISTER AU MOINS UN BACKUP DE CHAQUE DATAFILE, PLUS ANCIEN QUE LA PERIODE. Sont considérés comme obsolètes, tous les backups plus anciens que celui là. SAVOIR : Désormais, REPORT OBSOLETE présente TOUS LES FICHIERS : FILE BACKUPS FILE COPIES ARCHIVE LOGS BACKUP ARCHIVE LOGS. Il fournit aussi le moyen de LES SUP PRIMER (commande DELETE). OU CONFIGURE CLEAR RECOVERY WINDOW OF Nb days RETENTION POLICY TO REDUNDANCY Nbrecent NONE REPORT REPORT REPORT REPORT OBSOLETE OBSOLETE OBSOLETE OBSOLETE

11 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 11/59 DELETE OBSOLETE DELETE OBSOLETE RECOVERY WINDOW OF Nb days BACKUP ou COPY obsolète si NE PEUT ETRE UTILISE POUR REVENIR DANS LA PERIODE DE NB JOURS PASSES REDUNDANCY Nbrecent BACKUP ou COPY obsolète si il existe AU MONS NB BACKUPS ou COPIES PLUS RECENTS du même fichier ORPHAN BACKUP ou COPY obsolete si appartient à des incarnations qui ne sont pas des ANCETRES DIRECTS de lincarnation actuelle sbt DEVICE TYPE disk

12 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 12/59 COMPORTEMENT REPORT NEED BACKUP SANS ET AVEC DEFAUTS DE CONFIGURE REPORT NEED BACKUP DAYS Nbjours DATAFILE requier BACKUP si nécessite un Nombre de JOURS DE LOGS supérieur à cette valeur INCREMENTAL Nbversions DATAFILE requier FULL BACKUP si le nombre de BACKUPS INCREMENTAUX à appliquer est supérieur à cette valeur. RECOVERY WINDOW OF Nb days DATAFILE requier BACKUP si RMAN ne peut pas recouvrer la base durant cette période REDUNDANCY Nbrecent DATAFILE requier BACKUP si le nombre de BACKUPS ou COPIES PLUS RECENTS est inférieur à cette valeur. DATABASE TABLESPACE DATAFILE TSName Filename OU CONFIGURE CLEAR RECOVERY WINDOW OF Nb DAYS RETENTION POLICY TO REDUNDANCY Nbrecent NONE REPORT REPORT REPORT REPORT NEED BACKUP NEED BACKUP NEED BACKUP NEED BACKUP

13 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 13/59 Reporting Obsolete Backups and Copies: Example The following example reports obsolete backups and copies with a redundancy of 1: REPORT OBSOLETE; Report of obsolete backups and copies Type Key Completion Time Filename/Handle Backup Set 1 OCT :54:56 Backup Piece 1 OCT :54:56 /oracle/dbs/01d7t0t9_1_1 Archive Log 1 OCT :52:17 /oracle/oradata/trgt/arch/archive1_21.dbf

14 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 14/59 This example reports all datafiles in the database that require the application of five or more incremental backups to be recovered to their current state: REPORT NEED BACKUP INCREMENTAL 5 DATABASE; Report of files that need more than 5 incrementals during recovery File Incrementals Name /oracle/oradata/trgt/undotbs01.dbf 3 9 /oracle/oradata/trgt/cwmlite01.dbf 4 9 /oracle/oradata/trgt/drsys01.dbf reports of all datafiles from tablespace SYSTEM that will need more than two days of archived redo logs to be applied during recovery after being restored from the most recent backup: REPORT NEED BACKUP DAYS 2 TABLESPACE SYSTEM; Report of files whose recovery needs more than 2 days of archived logs File Days Name /oracle/oradata/trgt/drsys01.dbf.f

15 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 15/59 LIST/CROSSCHECK/DELETE EXPIRED/CHANGE Ces quatre commandes RMAN de maintenance du catalogue, ont été unifiées au niveau de la syntaxe. En effet, on DESIGNE GENERIQUEMENT des BACKUP ou des COPIES ou des ARCHIVES (BACKUP OF, COPY OFF, ARCHIVE LOG) avec différents critères. il nexiste plus quune seule forme syntaxique pour les ordres : LIST CHANGE CROSSCHECK affiche sauvegardes et incarnations connues met à jour le status dobjets ds catalogue vérifie la validité physique des sauvegardes available unavailable uncatalog DELETE (EXPIRED) Supprime du catalogue, les objets de sauvegarde qui ne sont plus physiquement trouvés. change delete remplacé par delete change crosscheck remplacé par crosscheck change all validate remplacé par xxxxx validate et validate Examine a backup set and report whether its data is intact. RMAN scans all of the backup pieces in the specified backup sets and looks at the checksums to verify that the contents can be successfully restored.

16 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 16/59 COMMANDES UNIFIEES LIST, DELETE EXPIRED, CHANGE et CROSSCHECK CROSSCHECK DELETE EXPIRED uncatalog unavailable CHANGE available delete remplacé par commande DELETE LIST all validate crosschec k remplacé par commande CROSSCHECK remplacé par commande CROSSCHECK INCARNATION OF DATABASE EXPIRED DEVICE TYPE sbt disk

17 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 17/59 Les patterns disk sbt_tape SPFILE spfile backuppiece tablespace backup piece backup piece BACKUP SET DATAFILE backup piece backup piece BACKUP SET ARCHIVE LOG backupset datafile COPIE datafilecopy datafile datafile datafile datafile ctlfile controlfile COPIE ctlfile controlfilecopy ctlfile ctlfile database SCN n deb SCN n fin SCN n deb SCN n fin SCN o deb SCN o fin SCN o deb SCN o fin archivelog archive archive archive archive

18 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 18/59 PATTERN DE DESIGNATION DOBJETS DE SAUVEGARDE SELON DENOMINATION SERVEUR ListBackupOpti on BY backup BY BACKUP Lists backup sets, then the contents of each backup set (pieces and files), and then proxy copies. This is the default option for LIST BACKUP. If you specify the SUMMARY option, then this command is equivalent to LIST BACKUP SUMMARY. VERBOSE Gives detailed description of contents of each backup set (default). SUMMARY Gives a one-line summary for each datafile (when using BY FILE) or backup (when using BY BACKUP). BY FILE Lists a datafile, then its backup sets (including recovery action info), and then proxy copies. file summary verbose BACKUP COPY OF datafile tablespace database filname tsname ARCHIVELOG ALL LIKE SQLlike pattern controlfile spfile ListObjectS pec from time from scn from sequence from time date scndep seqdep until time until scn until sequence scnfin seqfin date from scn BIEN VOIR : Ce Pattern permet de désigner les OBJETS SAUVEGARDES datafiles et archive logs selon le mécanisme de sauvegarde (backup, copy, archive) le type dobjet physique sauvegardé (database/ tablespace/datafile) Remarquer quarchivelog représente à la fois un mécanisme et un objet from sequence time between scn between sequence between date scndep seqdep and and and thread scnfin seqfin date threadnumber

19 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 19/59 PATTERN DE DESIGNATION DOBJETS DE SAUVEGARDE SELON EVENEMENTS RMAN SUBIS MaintQualifi er TAG tagnam e LIKE pattern sbt BACKED UP nbbackup TIMES TO DEVICE TYPE disk completed between completed before completed after date date date and date CompletedTimeSp ec BIEN VOIR : Ce Pattern permet de désigner les OBJETS DE SAUVEGARDE datafiles et archive logs selon les EVENEMENTS RMAN LES AYANT PRODUITS, OU DES CRITERES LIKE SUR LE NOM.

20 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 20/59 PATTERN DE DESIGNATION DOBJETS DE SAUVEGARDE SELON DENOMINATION RMAN (catalog) BACKUPPIECE PROXY Mediahandle primkey tagnam e sequence BACKUPSET CONTROLFILECOPY primkey primkey filname RecordS pec DATAFILECOPY primkey filname tagnam e ARCHIVELOG primkey filname BIEN VOIR : Ce Pattern permet de désigner les OBJETS DE SAUVEGARDE selon leur dénomination CATALOGUE

21 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 21/59 COMMANDE LIST : EXEMPLES RMAN> LIST BACKUP; BS Key Type LV Size Device Type Elapsed Time Completion Time Full 122M DISK 00:00:30 OCT :10:23 BP Key: 1293 Status: AVAILABLE Tag: TAG T Piece Name: /oracle/dbs/lvd6dtk1_1_1 Controlfile Included: Ckp SCN: Ckp time: OCT :09:53 SPFILE Included: Modification time: OCT :09:53 List of Datafiles in backup set 699 File LV Type Ckp SCN Ckp Time Name Full OCT :09:56 /oracle/oradata/trgt/system01.dbf 2 Full OCT :09:56 /oracle/oradata/trgt/undotbs01.dbf 3 Full OCT :09:56 /oracle/oradata/trgt/cwmlite01.dbf 4 Full OCT :09:56 /oracle/oradata/trgt/drsys01.dbf 5 Full OCT :09:56 /oracle/oradata/trgt/example01.dbf 6 Full OCT :09:56 /oracle/oradata/trgt/indx01.dbf 7 Full OCT :09:56 /oracle/oradata/trgt/tools01.dbf 8 Full OCT :09:56 /oracle/oradata/trgt/users01.dbf Listing Copies: Example This example lists image copies of datafile?/oradata/trgt/users01.dbf made before September 27, 2001: LIST COPY OF DATAFILE?/oradata/trgt/users01.dbf COMPLETED BEFORE 27-SEP-01; LIST COPY OF DATABASE ARCHIVELOG ALL; List of Archived Log Copies Key Thrd Seq S Low Time Name A 14-SEP-01 /oracle/oradata/trgt/arch/archive1_30.dbf A 14-SEP-01 /oracle/oradata/trgt/arch/archive1_31.dbf To display information about backup sets, proxy copies, and image copies recorded in the repository. The LIST command displays the files against which you can CROSSCHECK and DELETE commands. Use this command to list: Backups and copies that do not have the status AVAILABLE in the RMAN repository Backups and copies of datafiles that are available and can possibly be used in a restore operation Specified archived logs, backup sets, backup pieces, control file copies, datafile copies, and proxy copies Backups and copies restricted by tag, completion time, recoverability, or device Incarnations of a specified database or of all databases known to the catalog RMAN records the output to either standard output or the message log, but not to at the same time. You can control how the output is organized (BY BACKUP or BY FILE) as well as the level of detail in the output (VERBOSE or SUMMARY). run both

22 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 22/59 COMMANDE CHANGE : EXEMPLES Updating Backups to Status UNAVAILABLE: Example This example changes the status of backup set 100 as well as all backups of server parameter files created more than one day ago to UNAVAILABLE. You do not need to allocate a maintenance channel: CHANGE BACKUPSET 100 UNAVAILABLE; CHANGE BACKUP OF SPFILE COMPLETED BEFORE SYSDATE-1 UNAVAILABLE; Uncataloging and Cataloging Archived Logs: Example In this example, you first move all archived logs to a temporary directory and then uncatalog them: HOST mv $ORACLE_HOME/oradata/trgt/arch/* /tmp/arch; CHANGE COPY OF ARCHIVELOG ALL UNCATALOG; EXIT; From the UNIX command shell you use Perl to create a command file that contains a CATALOG command for each archived log: % perl5 foreach (@files) \? {print "CATALOG ARCHIVELOG $_\;\n";} > $HOME/rman.cmd Finally, you start RMAN and run the command file to catalog the relocated logs: % rman TARGET Changing the Retention Status of a Backup Set: Example This example, which requires a recovery catalog, changes an ordinary backup into a long-term backup: CHANGE BACKUP TAG consistent_db_bkup KEEP FOREVER NOLOGS;

23 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 23/59 COMMANDE CROSSCHECK : RAPPEL USAGE Sometimes backups and copies disappear from disk, or tapes in the media management library become unavailable. For example, someone may inadvertently delete backup pieces from disk, or one of the tapes used by the media manager may become corrupted. To ensure that data about backup sets and image copies in the recovery catalog or control file is synchronized with actual files on disk or in the media management catalog, perform a crosscheck. The CROSSCHECK command operates only on files that are recorded in the RMAN repository. Figure 7 2 illustrates a crosscheck of the media manager. RMAN queries the repository (recovery catalog or target database control file) for the names and locations of the four backup sets to be checked. RMAN sends this information to the target database server, which queries the media management software about the backups. The media management software then checks its media catalog and reports back to the server that backup set 3 is missing. RMAN updates the status of backup set 3 to EXPIRED in the repository. The record for backup set 3 will now be deleted if you run DELETE EXPIRED. Crosschecks are useful because they can Update outdated information about backups and copies that disappeared from disk or tape or became corrupted Update the repository if you delete archived redo logs or other files using operating system commands Use the crosscheck feature to check the status of a backup or copy on disk or tape. If the backup or copy is on disk, then CROSSCHECK checks whether the header of the file is valid. If a backup is on tape, then the command checks that the backups exist. Backup sets, backup pieces, and copies can have the status AVAILABLE, EXPIRED, or UNAVAILABLE. You can view the status information in the output of the LIST command and the recovery catalog views. Note that you can issue the DELETE EXPIRED command to delete all expired backups and copies. RMAN removes the record for the expired file from the repository. If for some reason the file still exists on the media, then RMAN issues warnings and lists the mismatched objects that cannot be deleted.

24 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 24/59 CHANNELS Deux possibilités dallocation de channels : Manuellement allocate channel... Automatiquement configure channel... dans allocate channel : Il ny a plus doption for delete apparition de allocate channel for maintenance device type. qui peut être suivi de lordre delete Les channels définis dans CONFIGURE nont plus à être alloués dans les jobs RMAN qui effectuent des backup, restore ou recovery.

25 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 25/59 OMF : PRISE EN CHARGE OMF, SPFILE et MULTIBLOCK SIZES RMAN supporte le nouveau dispositif OMF en permettant la restauration des datafiles, directement en noms de fichiers OMF. SPFILE RMAN permet la sauvegarde et la restauration des fichiers pfile (cf chapitre sur spfile et export utilisé par rman). Ces fichiers sont directement stockés dans la base catalogue et restaurables sur demande. Seulement une seule copie autorisée MULTIPLE BLOCK SIZE : RMAN supporte les datafiles de TS de block size différents, en les discriminant sur des backup-set différenciés.

26 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 26/59 AUTOMATIC CHANNEL ALLOCATION FEATURE Rappel : Un channel est une identification de device(s) accompagnée de format de nommage à appliquer lors des backups, paramètres de communication spécifiques au device. Jusquen8i, il devait y avoir allocation des channels à employer, dans la même session RMAN qui effectuait les backups ou les copies. LAutomatic channel allocation feature sapplique aux opérations de BACKUP, COPY et RESTORE et est mis en oeuvre si le DBA ne préçise pas dallocate channel en préalable de ces opérations. Mise en oeuvre : DRESSER STRUCTURE DE PREDEFINITIONS DALLOCATION 3 NIVEAUX: channels device type sappuie sur channels default device type sappuie sur device types 1 OUTIL : CONFIGURE Prédéfinir tous les channels possibles 1 exec par channel configure channel num... device type devt (équivalent ALLOCATE avec numéro dordrecomme identifiant) Prédéfinir tous les device types possibles 1 exec par device type configure device type devt parallelism nb (nb adopte les nb premiers channels choisis en fonction de leur num). Si devt = sbt, déclarer nb avec le nombre de tapes physiques Prédéfinir le device type par défaut 1 exec configure default device type defdevt Une fois cette hiérarchie définie, RMAN allouera, pour les opérations de BACKUP, COPY ou RESTORE En labsence dordre ALLOCATE les channels de defdevt, en nombre nb en les nommant ora_defdevt_num ce qui donne en équivalent allocate : allocate channel ora_defdevt_num... device type defdevt

27 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 27/59 AUTOMATIC CHANNEL ALLOCATION FEATURE Mise en oeuvre : EFFACER PREDEFINITIONS DALLOCATION : Le paramètre CLEAR est associé à chaque niveau et permet de revenir aux défauts. Possibilités offertes : Le numéro de channel num nest pas obligatoire : sil nest pas défini, les paramètres portent sur TOUS LES CHANNELS. on le nomme channel générique pour le device type. BACKUP, COPY et RESTORE peuvent préçiser la clause device type devt, différente de la "default device type". Il nest donc pas obligatoire dengager un configure default device type, mais chaque ordre backup/copy/restore devra préçiser la clause device type devt pour que RMAN puisse retrouver les channels appropriés, aux fins dallocation. Suivi : 1 commande RMAN : voir toutes prédéfinitions voir les channels prédéfinis voir les device type prédéfinis voir le default device type SHOW ALL CHANNEL DEVICE TYPE DEFAULT DEVICE TYPE

28 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 28/59 COMMANDE ALLOCATE POUR LALLOCATION MANUELLE DE CHANNELS ALLOCATE channel ident device type sbt RMAN > connect target... RMAN > exit disk format string %p %s %d %n %t %u num backuppiece dans backupset num backupset dans controlfile dbd cible name dbd cible padded name sur 4 octets : timestamp %s et %t concaténés si // SERVER connect chaîne connect db cible which instance performs the operation maxpiecesize Taille max bckpiece Set limits on the size of backup pieces maxsetsize Taille max bckset Set limits on the size of backup sets MANUALLY ALLOCATED CHANN ELS si type # disk maxopenfiles send parms rate NbOpenficssimult commande device params device sizeperread limits on the number of concurrently open files Send vendor-specific commands to the media manager vendors specific parameters maximum number of bytes that RMAN reads on this channel. BIEN VOIR : Lobjectif est dallouer manuellement un channel, EN PREPARATION DOPERATIONS CHANGE DELETE CROSSCHECK. SAVOIR : Si CONFIGURE a été passé, il ny a pas besoin dallouer même ce type de channel, manuellement.

29 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 29/59 RAPPEL SIGNIFICATIONS DES PARAMETRES maxpiecesiz e backup backup piece piece maxsetsize Prise en compte parallel server (noeuds clusterisés parallel server Oracle) backup piece BACKUP SET Limite de perturbation avec applis OLTP par contrainte du nombre de lectures par seconde et par fichier secondes limite OS paramétrage RMAN OS secondes rate secondes maxopenfile s Contournement des limitations OS pour le nombre de fichiers ouverts simultanément

30 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 30/59 COMMANDE CONFIGURE POUR LE PREETABLISSEMENTDES CHANNELS CONFIGURE sbt CHANNEL num device type CLEAR disk string DEFINIT TOUS LES CHANNELS format %p %s %d %n %t %u ctlfile connect chaîne connect db cible ctlfile AUTOMATIC ALLOCATED CHANNE LS DEFINIT LES CHANNELS POUR CHAQUE DEVICE TYPE maxpiecesize maxsetsize maxopenfiles send parms Taille max bckpiece Taille max bckset NbOpenficssimult commande device params device rate sizeperread sbt DEVICE TYPE parallelism nb disk INDIQUE LE DEVICE TYPE UTILISE PAR DEFAUT POUR LES BACKUPS ou les COPY CLEAR CLEAR sbt DEFAULT DEVICE TYPE TO disk

31 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 31/59 PREDEFINIR TOUS LES CHANNELS SUSCEPTIBLES DETRE UTILISES, EN LEUR ATTRIBUANT UN NUMERO DORDRE PREDEFINIR TOUS LES DEVICES TYPES ET LE CHOIX DES CHANNELS QUI LEUR SERONT ASSOCIES, EN FONCTION DE LEUR NUMERO DORDRE ADOPTER UN DEVICE TYPE PAR DEFAUT

32 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 32/59 CONFIGURE channel 1 / device type Repert_1 disk 2 / device type Repert_1 disk 3 / device type Repert_1 disk device type 2 device type sbt device type sbt device type sbt sbt Repert_1_1 ora_disk_1 Repert_1_1 ora_disk_1 Repert_1_1 ora_disk_1 ora_disk_2 ora_disk_2 ora_disk_2 Repert_2 Repert_2 Repert_2 format string %p %s %d %n %t %u format string %p %s %d %n %t %u format string %p %s %d %n %t %u CONFIGURE device type disk parallelism 2 CONFIGURE device type sbt_tape sbt parallelism 3 disk CONFIGURE default device type TO sbt

33 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 33/59 Configuring Automatic Disk and Tape Channels: This example configures generic DISK and sbt channels, sets the default device type to sbt, and sets PARALLELISM to 3: CONFIGURE CHANNEL DEVICE TYPE DISK RATE 5M; CONFIGURE CHANNEL DEVICE TYPE sbt PARMS ENV=(NSR_SERVER=bksrv1); CONFIGURE DEFAULT DEVICE TYPE TO sbt; CONFIGURE DEVICE TYPE sbt PARALLELISM 3; Pas de numéro de channel mais un seul channel par device type Overriding the Default Device Type: This example configures the default device type to sbt, backs up the archived logs on the default sbt channel, and then backs up the database to disk on the default disk channel: CONFIGURE CHANNEL DEVICE TYPE sbt PARMS ENV=(NSR_SERVER=bksrv1); CONFIGURE DEFAULT DEVICE TYPE TO sbt; BACKUP ARCHIVELOG ALL; BACKUP DEVICE TYPE DISK DATABASE; Pas de numéro de channel Configuring Automatic Channels Across File Systems: This example configures automatic disk channels across three file systems: CONFIGURE DEVICE TYPE DISK PARALLELISM 3; CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT /disk1/backup/%u; CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT /disk2/backup/%u; CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT /disk3/backup/%u; BACKUP DEVICE TYPE DISK DATABASE PLUS ARCHIVELOG; Configuring Automatic Channels in an Oracle Real Application Clusters Configuration: This example allocates automatic sbt channels for two nodes of an Oracle Real Application Clusters database: CONFIGURE DEVICE TYPE sbt PARALLELISM 2; CONFIGURE DEFAULT DEVICE TYPE TO sbt; CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT SYS/change_on_install@node1 PARMS ENV=(NSR_SERVER=bkserv1); CONFIGURE CHANNEL 2 DEVICE TYPE sbt CONNECT SYS/change_on_install@node2 PARMS ENV=(NSR_SERVER=bkserv2); Clearing Automatic Channels: This example clears manually numbered DISK channels 2 and 3 and the generic sbt channel: CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR; CONFIGURE CHANNEL 3 DEVICE TYPE DISK CLEAR; CONFIGURE CHANNEL DEVICE TYPE sbt CLEAR; Configuring and Clearing Parallelism: This example sets DISK parallelism to 2, then changes it to 3, then returns it to the default parallelism of 1: CONFIGURE DEVICE TYPE DISK PARALLELISM 2; CONFIGURE DEVICE TYPE DISK PARALLELISM 3; CONFIGURE DEVICE TYPE DISK CLEAR;

34 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 34/59 The following example configures the default device to sbt and runs a SHOW command: RMAN> CONFIGURE DEFAULT DEVICE TYPE TO sbt; new RMAN configuration parameters: CONFIGURE DEFAULT DEVICE TYPE TO sbt; new RMAN configuration parameters are successfully stored RMAN> SHOW DEVICE TYPE; RMAN configuration parameters are: CONFIGURE DEVICE TYPE SBT PARALLELISM 1; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default After connecting to the target database and recovery catalog (if you use one), run the SHOW DEFAULT DEVICE TYPE command. For example, enter: SHOW DEFAULT DEVICE TYPE; # shows the CONFIGURE DEFAULT DEVICE TYPE setting RMAN configuration parameters are: CONFIGURE DEFAULT DEVICE TYPE TO SBT; Issue the SHOW CHANNEL command to display the settings for all automatically allocated channels. To show the automatic channel settings: SHOW CHANNEL; # shows the CONFIGURE setting for the automatic channels RMAN configuration parameters are: CONFIGURE CHANNEL DEVICE TYPE SBT RATE 1500K; Each CONFIGURE command removes the user-entered settings and returns the configuration to its default value. To see the default configuration settings, run the SHOW ALL command before entering any configurations of your own. The defaults are prefixed with a number sign (#). After connecting to the target database and recovery catalog (if you use one), run the SHOW ALL command. For example, enter the following: SHOW ALL; # shows all CONFIGURE settings, both user-entered and default RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO SBT; CONFIGURE DEVICE TYPE SBT PARALLELISM 1; CONFIGURE DEVICE TYPE DISK PARALLELISM 2; CONFIGURE DATAFILE BACKUP COPIES FOR DISK TO 2; CONFIGURE DATAFILE BACKUP COPIES FOR SBT TO 1; #default CONFIGURE ARCHIVELOG BACKUP COPIES FOR SBT TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DISK TO 1; # default CONFIGURE MAXSETSIZE TO 3072K; CONFIGURE SNAPSHOT CONTROLFILE NAME TO /oracle/dbs/cf_snap.f; CONFIGURE EXCLUDE FOR TABLESPACE example;

35 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 35/59 Backups exempts de retention policy Rappel : BACKUP ENHANCEMENTS une rétention policy fixe les critères de validité des backups vis à vis de leur utilité à revenir à une période antérieure de -n days du fait que la relève en backups plus jeunes est assurée, à concurrence de n backups plus récents. REPORT OBSOLETE donnent les backups qui nont plus de nécessité vis à vis de lune ou lautre de ces exigences DELETE OBSOLETE DETRUIT PHYSIQUEMENT CES BACKUPS Problème : configure retention pilcy est applicable sur TOUS LES BACKUPS comment fabriquer des backups QUE LON VEUT CONSERVER SPECIFIQUEMENT SUR DES CRITERES DIFFERENTS DE CEUX FIXES DANS RETENTION POLICY, cest à dire des backups qui ne passent obsolètes que lorsquils dépassent leurs critères propres introduits au lancement de la commande BACKUP? Solution : BACKUP Obéïr à la retention policy A garder non obsolète jusquà... A garder non obsolète à jamais Garder toutes les archives relatives à ce backup : PITR = nimporte quand depuis backup Ne pas garder toutes les archives relatives à ce backup : PITR = moment du backup NOKEEP KEEP UNTIL TIME "date" KEEP FOREVER LOG NOLOG Ces options ne peuvent être introduites QUE SI ON UTILISE LE RECOVERY CATALOGUE, qui ne présente pas ses propres règles de rétention comme le control file (CONTROL_FILE_RECORD_KEEP_TIME).

36 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 36/59 COMMANDE CONFIGURE POUR LE PREETABLISSEMENT DES PARAMETRES DE BACKUP CONFIGURE ARCHIVELOG overidable par SET BACKUP COPIES sbt DATAFILE BACKUP COPIES FOR DEVICE TYPE disk Nb copies identiques pour ce devtyp, de chaque backup CLEAR TO Nb MAXSETSIZE CLEAR TO Nb K M G ctlfile unlimited ctlfile BACKUP OPTIMIZATION CLEAR ON OFF Pas de backup si backup identique existe (même fichier)déjà sur le même device type EXCLUDE FOR TABLESPACE tsname Si backup database, exclue de façon permanente des tablespaces (pa ex, read only ou offline TS)

37 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 37/59 COMMANDE CONFIGURE POUR LE PREETABLISSEMENT DES PARAMETRES DE BACKUP CONFIGURE ctlfile snapshot controlfile name ctlfile CLEAR TO Filename Filename auxname for datafile Filenum AUXNAME FOR DATAFILE datafilespec TO filename Configures the auxiliary filename for the specified target datafile to filename. For example, you can set the auxiliary name for datafile 2 to /df2.f, and t hen unspecify this auxiliary name by running CONFIGURE AUXNAME FOR DATAFILE 2 NULL. If you are performing TSPITR or running the DUPLICATE command, then by setting AUXNAME you can preconfigure the filenames for use on the auxiliary database wit hout manually specifying the auxiliary filenames during the procedure. For example, use this command during TSPITR if the datafiles are on raw disk and you need to restore auxiliary datafiles to raw disk for performance reasons. T ypically, you set the AUXNAME parameter in TSPITR for the datafiles of the SYSTEM tablespace and the tablespaces containing rollback segments. Do not overlay files which are in use by the production database and can be discarded after TSPITR completes. In essence, the AUXNAME of a datafile is the location where TSPITR can create a temporary copy of it. When renaming files with the DUPLICATE command, CONFIGURE AUXNAME is an alternative to SET NEWNAME. The difference is that after you set the AUXNAME the first time, you do not need to reset the filename when you issue another DUPLICATE command: the AUXNAME setting remains in effect until you issue CONFIGURE AUXNAME... CLE AR. In contrast, you must reissue the SET NEWNAME command every time you rename files. SNAPSHOT CONTROLFILE NAME TO filename Configures the snapshot control file filename to filename. If you run CONFIGURE SNAPSHOT CONTROLFILE NAME CLEAR, then RMAN sets the snapshot control file na me to its default. The default value for the snapshot control file name is platform-specific and dependent on the Oracle home. For example, the default on some UNIX system is?/d bs/snapcf_@.f. If you clear the control file name, and you change the Oracle home, then the default location of the snapshot control file changes as well. set snapshot control file REMPLACE LES ANCIENNES COMMANDES : set auxname

38 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 38/59 RAPPEL COMMANDE BACKUP backupset key BACKUP database ALL tablespace datafile current controlfile controlfilecopy datafilecopy,, Tsname Filname ctlfilname tag,, Filname Tagname completed between completed before completed after date date date and date CompletedTime Spec ARCHIVELOG include current controlfile device type sbt ALL LIKE SQLlike pattern filesperset n channel chname delete input format skip offline readonly disk string %p %s %d %n %t %u from time from scn from sequence from time from scn date scndep seqdep until until time until scn sequence scnfin seqfin date inaccessible from sequence tag=tagname full time between scn between date scndep and and scnfin date cumulative incremental level sequence between seqdep thread and threadnumber seqfin

39 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 39/59 OPTIONS DE BACKUP PLACANT DANS OU HORS CONTEXTE DE RETENTION POLICY (REGLES DOBSOLESCENCE PARTICULIERES) sequence CHANGE BACKUP NOKEEP NON OBSOLETE jusquà... LE BACKUP SORT DES RETENTION POLICY KEEP UNTIL TIME FOREVER Date NON OBSOLETE POUR TOUJOURS LOGS Toutes archives requises pour recover de ce backup doivent survivre avec le backup (LOGS) ne survivent pas avec le backup (NOLOGS) NOLOGS Making a Long-Term Backup: Example This example makes a long-term backup of the database and specifies that it should never become obsolete and that the logs required to recover it should not be retained: SHUTDOWN IMMEDIATE; STARTUP MOUNT; BACKUP DATABASE KEEP FOREVER NOLOGS; ALTER DATABASE OPEN; Changing the Status of a Copy: Example This example specifies that any long-term copies of datafiles and control files should lose their exempt status and so become eligible to be obsolete according to the existing retention policy: CHANGE COPY OF DATABASE CONTROLFILE NOKEEP;

40 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 40/59 DUPPLEXED BACKUP COPIES (MULTI FORMAT) BACKUP COPIES Nbcopies string string string FORMAT %p %s %d %n %t, %p %s %d %n %t, %p %s %d %n %t %u %u %u SAVOIR : copie 1 copie 2 copie n DUPPLEX activé par COPIES=nbcopies si nbcopies < nombre de formats, extras formats non utilisés si nbcopies > nombre de formats, réutilisation cyclique des formats. Duplexing a Backup Set: This example duplexes a backup of datafile 1 (which includes the current control file and server parameter file) to separate disks: BACKUP DEVICE TYPE DISK COPIES 2 DATAFILE 1 FORMAT /disk1/df1_%u, /disk2/df1_%u; To duplex a backup with CONFIGURE BACKUP COPIES: 1. Configure the number of copies on the desired device type for datafiles and archived redo logs on the desired device types. This example configures duplexin g for datafiles and archived logs on tape as well as duplexing for datafiles (but not archived logs) on disk: CONFIGURE DEVICE TYPE sbt PARALLELISM 1; CONFIGURE DEFAULT DEVICE TYPE TO sbt; CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT /save1/%u, /save2/%u; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE sbt TO 2; CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE sbt TO 2; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2; 2. Duplex the backup. The following command backs up the database and archived logs to tape, making two copies of each datafile and archived redo log: BACKUP DATABASE PLUS ARCHIVELOG; # uses default sbt channel

41 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 41/59 SKIP BACKUP (OPTIMIZATION) CONFIGURE backup optimization CLEAR ON OFF Pas de backup si backup identique existe (même fichier)déjà sur le même device type BACKUP datafile Same DBID, checkpoint SCN, and RESETLOGS SCN and time. The datafile must be offline-normal, read-only, or closed normally. backupset Same backup set recid and stamp. ARCHIVELOG Same thread, sequence number, and RESETLOGS SCN and time. Backup Optimization You can configure RMAN to skip backups of files that have already been backed up. In this way, you can avoid making multiple backups of unchanging files such as archived logs. You can override this functionality with the FORCE option of the BACKUP command. LE SKIP DE BACKUP NE CHANGE EN RIEN LE COMPORTEMENT DE RMAN. SI DELETE INPUT A ETE POSITIONNE POUR LE BACKUP, LES FICHIERS DE BASE SERONT SUPPRIMES, MEME SI TOUS LES BACKUPS ONT ETE SKIPPES... MAIS CELA NE DEVRAIT PAS POSER DE PROBLEMES PUISQUE CEST RMAN LUI MEME QUI A VERIFIE LIDENTITE DUN BACKUP CLONE DEJA EXISTANT!.

42 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 42/59 COMPORTEMENT DE BACKUP "BACKUPSET/ARCHIVELOG ALL" avec RETENTION POLICY à RECOVERY WINDOW et DEVICE TYPE à SBT CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF Nb DAYS BACKUP BACKUPSET ALL device type sbt_tape sbt ARCHIVELOG ALL SAVOIR : Si la "retention policy" est basée sur "recovery window", RMAN backupe toujours tous fichiers dont le plus récent backup est plus ancien que la fenêtre de recovery. Cette optimisation provoque certains comportements dans le cas où le device type nest pas DISK. BACKUP ARCHIVELOG ALL backupe toutes les logs qui nexistent pas déjà sur bande BACKUP BACKUPSET ALL copie tous les backupset qui nexistent pas déjà sur bande Les datafiles en read only ou placés proprement offline sont backupés une seule fois par fenêtre de recovery Les datafiles online ne sont pas sautés

43 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 43/59 RESUMABLE BACKUP FEATURE : DETECTION ET BACKUP DES FICHIERS non backupés "n fois" ou "depuis tant de temps" CONFIGURE BACKUP device type default device type NOT BACKED UP sbt disk TO sbt disk Nb SINCE TIME TIMES date BACKUP ARCHIVED LOGs ON DIFFERENT MEDIA RESUME PREVIOUS ABNORMALY ENDED BACKUP BACKUP NEW FILES AFTER ADDING THEN TO DATABASE DEFAUT : TOUT FICHIER NON BACKUPE. BIEN VOIR : BACKUP nanalyse la présence de backup, QUE SUR LE "DEVICE TYPE" COURANT (celui de CONFIGURE ou celui de BACKUP donc) Ce dispositif est un OUTIL DE PREMIER ORDRE permettant de lancer des backups sur des médias alternatifs lancer des backups sur un ensemble de nouveaux fichiers de la database, sans les préçiser reprendre des backups précédant sétant anormalement terminés. NOT BACKED UP Backs up only those files (of the files specified on the command) that RMAN has never backed up. This option is a convenient way to back up new files after adding them to the database. SINCE TIME =date_string Specifies the date after which RMAN should back up files that have no backups. The date_string is either a date in the current NLS_DATE_FORMAT, or a SQL date expression such as SYSDATE-1. When calculating the number of backups for a file, RMAN only considers backups created on the same device type as the current backup. This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKUP UP SINCE TIME clause and avoid backing up those files that you already backed up. This feature is only useful if RMAN generates multiple backup sets during the backup. Thus, set the FILESPERSET parameter to a low value so that RMAN generates multiple backup sets. (rappel, filesperset fixe le nombre de fichiers backupés contenus dans chaque backup set. Mettre une valeur faible à filesperset (par exemple, 1) se traduira par un plus grand nombre de backupsets (par exemple, autant de backupsets que de fichiers backupés). Il semble dit que ce dispositif de "resume" nest utile que si, à lorigine, on discriminait bien les backupsets ==> resume détecte les backupsets corrects et reprend aux backupsets incorrectement constitués. A lextrême, si filesperset avait une valeur égale au nombre de fichiers backupés (==> 1 seul backupset en sortie), une reprise se traduirait par un recommencement complet du backupset). When determining whether a file has been backed up, the SINCE date is compared with the completion time of the most recent backup. The completion time for a file in a backup set is the completion time of the entire backup set. In other words, all files in the same backup set have the same completion time. integertimes Backs up only those archived logs that have not been backed up at least integer times. When calculating the number of backups for a file, RMAN only considers backups created on the same device type as the current backup. This option is a convenient way to back up archived logs on a specified media (for example, you want to keep at least three copies of each log on tape).

44 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 44/59 RESUMABLE BACKUP FEATURE : DETECTION ET BACKUP DES FICHIERS non backupés "n fois" ou "depuis tant de temps" BACKUP NOT BACKED UP Nb SINCE TIME TIMES date BACKUP NOT BACKED UP BIEN VOIR : La date introduite dans la clause SINCE TIME est comparée à la COMPLETION TIME du plus récent BACKUP SET EXISTANT POUR CE FICHIER. Le backup de chaque fichier est analysé sous langle du completion time de son backup set. Le completion time dun fichier appartenant à un backupset, EST LE COMPLETION TIME DU BACKUP SET Tous les fichiers du même backupset ont le même completion time, qui est celui de ce backupset. COMPLETION TIME OF BACK UPSET ctlfile ctlfile SCN n deb SCN n fin +1 SCN o deb SCN o fin backup piece backup piece datafile datafile backup piece backup piece SCN n deb SCN n fin archive archive +1 SCN o deb SCN o fin archive archive DATAFILE backup BACKUP SET piece backup piece BACKUP SET

45 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 45/59 ADJONCTION DES ARCHIVES LOG NON BACKUPES, A UN BACKUP DE DATAFILES BACKUP database tablespace, Tsname datafile, Filname Pour ne prendre que le DELTA de backup archives backup optimization CLEAR ON OFF plus archivelog Défaut si device type différent de "disk" SI SAVOIR : Le but de ce nouveau service est de SAUVEGARDER les ENREGISTREMENTS REDO LES PLUS RECENTS AVEC LA SAUVEGARDE DE DATAFILES. Mise en oeuvre : Sauvegarder les enregistrements redo en archive : alter system archive log current déclencher un backup archivelog all. si backup optimization on, seules les nouvelles archives seront prises, donc, les nouvellement constituées. backup archivelog all Effectuer le backup régulier de datafiles backup régulier Pour le cas de nouveaux enregs redo, sauvegarde à nouveau des redo alter system archive log current redéclencher un backup archivelog all backup archivelog all BIEN VOIR Les archives de log vont dans des backup set différentiés. plus archivelog peut être suivi des spécifications de backup. En aucun cas, les backupset de datafil e contiennent les blocs darchives : ce service effectue seulement une synchro intègre des opérations de backup datafile ET archive. The BACKUP... PLUS ARCHIVELOG command switches out of and archives the current online log, backs up archived logs, then performs another log switch and backs up remaining logs. This operation guarantees that the backed up datafiles can be recovered to a consistent state. When you specify PLUS ARCHIVELOG, RMAN performs these steps: 1. Runs an ALTER SYSTEM ARCHIVE LOG CURRENT statement. 2. Runs the BACKUP ARCHIVELOG ALL command. Note that if backup optimization is enabled, then RMAN only backs up logs that have not yet been backed up. 3. Backs up the files specified in the BACKUP command. 4. Runs an ALTER SYSTEM ARCHIVE LOG CURRENT statement. 5. Backs up any remaining archived redo logs.

46 Oracle upg adm 9i Claude DA COSTA Chap 4 RMAN Enhcts Page 46/59 GERER LES FICHIERS BACKUP SUR DISQUE ET BANDE BACKUP ALL backupset completed between date and date device type delete input SBT DISK completed before completed after date date CompletedTimeSp ec BIEN VOIR : La désignation des backup set a été élargie avec le pattern CompletedTimeSpec. Désormais, on peut désigner des backupsets selon des critères de temps relatif ( sysdate - n). Lancer Backup Backupset provoque une dupplication des backupset. Si la clause delete input est rajoutée, on opère un mouvement. Si le backupset est situé sur disque, il peut être dirigé, soit sur disque (device type DISK) soit sur cassette (device type SBT) Exemple : Mouvementer sur bande tous les backupset de plus de 7 jours mouvementer (delete input) sur bande (device type SBT) tous les backupset (backupset) de plus de 7 jours (completed before sysdate-7) RMAN> BACKUP DEVICE TYPE SBT BACKUPSET COMPLETED BEFORE SYSDATE-7 DELETE INPUT