3

With an Incrementally Updated Image File Backup the same script handles both the initial image backups, and the incremental backups that can be applied to the images to bring them up to date. Is there a way to change a parameter or modify this script so that the image files get created in one location and the incrementals get created in another?

A partial solution is to do the inital image file backups, move them to the alternate location and then re-catalog them there. The next run will then create the incremental backup in the original location, but update the image files in the new location. The problem comes when a new datafile is created. The backup will recognize that it doesn't have an image for it and create one, but in the same location as the incrementals. Aside from repeating the move and re-catalog is there a way to have things happen as desired from the start?

If you're wondering why this would be useful, consider that the image backup volume could be snapped and cloned to a new volume on another server for fast refreshes of lower environments. Having the incrementals and images in separate locations reduces the space requirements for the snap/clone.

Backup Command:

BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'MyImageBackup' DATABASE;
  • Yes. Just run this command before your backup and point the level 0 backups to one directory and the level 1 backups to a different directory. "configure channel device type disk format '<backup_dir_path>/%d_%Y_%M_%D_%t_%s_%c_%p" – Gandolf989 Feb 28 '17 at 17:03
  • @Gandolf989 I'm unclear how changing the configuration like this would cause one backup command to behave differently for level 0 than for level 1 backups. Remember that an incremental level 1 with no level 0 does an implicit level 0, so there is only one backup command that is doing both level 1 and level 0 backups. – Leigh Riffel Feb 28 '17 at 18:47
  • I answered this question. "Is there a way to change a parameter or modify this script so that the image files get created in one location and the incrementals get created in another?" If you do a level 1, point it to one directory, otherwise point to a different directory. Your premise is false though. You can send all backups to the same directory, then the "backup volume could be snapped and cloned to a new volume on another server for fast refreshes of lower environments." As long as you have a block change tracking file, the incremental level 1's should be small compared to the level 0. – Gandolf989 Feb 28 '17 at 19:58
  • @Gandolf989 See the definition of Incrementally Updating Backups - docs.oracle.com/cd/E11882_01/backup.112/e10642/… Level 1's are significantly smaller than the image files themselves, but not insignificant, which is why I want to exclude them from the snap/clone. – Leigh Riffel Feb 28 '17 at 21:16
  • Doc ID 831223.1 might be useful for you. – JSapkota Mar 1 '17 at 4:43
1

No, it is not possible to have this single backup command do the level 0 to a different location than the level 1. It is possible to change the script to determine which files don't have level zero backups and do a separate backup just for those datafiles before running the existing command to the incremental location.

  • Obviously this isn't the desired answer. Thanks to @Gandolf989 and JSapkota who both essentially said this. – Leigh Riffel Mar 3 '17 at 13:55
  • @JSapkota (to get a ping) – Leigh Riffel Mar 3 '17 at 13:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.