RMAN backup and restore to a specific point in time -> getting RMAN-06025 errors about docker-images

[saurabhuja]

Keeping backup inside container is generally not a good idea as when container is removed, your backups are lost.

If both the containers are in same host machine, i am thinking why not add another docker volume mapping to both rac containers while creating and take backup over there? However i am not sure whether to go with single shared volume for both containers or have dedicated volume for each? I think it would depend upon your customer if he wants some isolation between two disk or ok with shared one?

docker volume create oracle_backup_vol
docker run -d <> -v oracle_backup_vol:/home/oracle/backup
After backup we can check backed up data in ls /var/lib/docker/volumes/oracle_backup_vol/_data​

Will also try and update you.

[saurabhuja]

Discussed in email to you, i am not rman expert, but you can use rman consistent backup location everytime you connect to rman. may be add that as docker volume as well

--volume rman_backup_volume:/u01/backup:rw \

docker volume create rman_backup_volume

docker exec -it racnode1 bash
chown oracle:racdba /u01/backup

docker exec -it racnode2 bash
chown oracle:racdba /u01/backup

RMAN>
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u01/backup/%U';
--then do backup and point in time recovery---

Can also validate backup in location in host machine-

ls -lrt /var/lib/docker/volumes/rman_backup_volume/_data/

[yanivharpaz]

by using ASM as the only location for the archive logs, it was resolved.
thank you Saurabh and thank you Jyoti :-)

sqlplus "/ as sysdba"
alter system set db_recovery_file_dest='+DATA' scope=spfile;
alter system set db_recovery_file_dest_size=100G scope=spfile;

alter system set log_archive_dest_1='location=USE_DB_RECOVERY_FILE_DEST';