Re: backup policy

Posted by ErmanArslansOracleBlog on Jun 19, 2017; 7:40am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/backup-policy-tp2809p2812.html

Hi Arsala,

Seems okay.

5 things, I can recommend;

1)You should also backup the archivelogs. You can use PLUS ARCHIVELOG argument for that.

2) Your script and rman configurations are ready for deleting the obsolete backup, but as for archivelogs (not back up archivelogs, I mean), you have the delete archivelog commands in your script. This is acceptable
However, you can always consider to use delete input command as well.. (you are backing up the database everyday, so you can delete the archivelogs while you are generating archivelog backups)
Ex: backup database plus archivelog delete all input;

3) connect to a catalog (if you have one)

4)consider more parallelism, if your resources are available. (ofcourse test it, it can increase the cpu usage)

5)consider backup compression, if you have space problems. (ofcourse test it, it can increase the backup duration and increase the cpu usage)