![]() # now delete from disk all logs that have been backed up to tape at least twice NOT BACKED UP 2 TIMES # back up only logs without 2 backups on tape PARMS 'ENV=(OB_MEDIA_FAMILY=first_copy)' PARMS 'ENV=(OB_MEDIA_FAMILY=second_copy)' # channel goes to both media families "first_copy" and "second_copy" # manually allocate a channel, to specify that the backup run by this After the backup, you want to delete all archived logs that have at least two copies on tape. This scenario assumes that the database is not using a fast recovery area.įirst, perform a one-time configuration as follows: CONFIGURE BACKUP OPTIMIZATION ON ĬONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'ENV=(OB_MEDIA_FAMILY=first_copy) īecause you have optimization enabled, you can run the following command every evening to back up all archived logs to the first_copy media family that have not already been backed up:Įvery Friday evening you create an additional backup of all archived logs in a different media family. You are worried about tape failure, however, so you want to ensure that you have more than one copy of each log sequence number on a separate tape before you perform your weekly deletion of logs from disk. Theįollowing one-time configuration specifies that archived redo logs are eligible for deletionįrom disk if two archived log backups exist on tape: CONFIGURE ARCHIVELOG DELETION POLICYĪssume a more sophisticated scenario in which your goal is to back up the archived logs to tape every day. Then the simplest way to achieve the goal is with an archived redo log deletion policy. If your goal is to delete logs from disk that have been backed up two times to SBT, PARMS 'ENV=(OB_MEDIA_FAMILY=log_family2)' Īfter running the script in this example, you can delete unneeded logs by # Make one more copy of the archived logs and save them to tapes from a PARMS 'ENV=(OB_MEDIA_FAMILY=log_family1)' # first copies are saved to the tapes from the media family "log_family1". # The following command backs up just the logs that are not on tape. With RMAN configured as shown in this example, run the following script at the same timeĮvery night to back up the logs generated during the previous day to two separate mediaįamilies. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.Įxample 10-2 Backing Up Archived Redo Logs to Multiple Media Families If you specify a section size that is larger than the size of the file, then RMAN does not use multisection backup for the file. You must use the DELETE command to delete the partial backup set. RMAN does not consider partial backups for restore and recovery. If a multisection backup is unsuccessful, then the RMAN metadata can contain a record for a partial backup set. If a multisection backup completes successfully, then no backup set generated during the backup contains a partial data file. Backing up a file in separate sections can improve the performance of backups of large data files. RMAN divides the work among multiple channels, with each channel backing up one file section in a file. The purpose of multisection backups is to enable RMAN channels to back up a single large file in parallel. You cannot specify SECTION SIZE with MAXPIECESIZE. RMAN-06182: archive log larger than MAXSETSIZE: thread 1 seq 1 RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = RMAN displays an error stack such as the following: When determining whether MAXSETSIZE is too small, RMAN uses the size of the original data file rather than the file size after compression. In some cases the MAXSETSIZE value may be too small to contain the largest file that you are backing up. If theīackup fails part way through, then you can use the restartableīackup feature to back up only those files that were not backed That the database is divided among multiple backup sets. ![]() You can use BACKUP.MAXSETSIZE to limit the size of backup sets so RMAN attempts to limit all backup sets to this size. The MAXSETSIZE parameter of the BACKUP command specifies a maximum size for a backup set in units of bytes (default), kilobytes, megabytes, or gigabytes.įor example, to limit a backup set to 305 MB, specify MAXSETSIZE 305M.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |