Backup size is big due to huge size of archive logs
733607Nov 11 2009 — edited Nov 13 2009Hi,
We are usiong Oracle 10.2.0.3. We take online backup incremental 0 level (full) backup using RMAN. We use following comamnds to take backup.
run {
ALLOCATE CHANNEL C1 TYPE DISK;
delete noprompt archivelog all completed before 'sysdate-5';
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP INCREMENTAL LEVEL=0 CUMULATIVE format '$dir/level0_%u' DATABASE include curre
nt controlfile for standby force;
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP ARCHIVELOG ALL format '$dir/archivelogs_%s_%t' FORCE;
BACKUP CURRENT CONTROLFILE format '$dir/control_primary' FORCE;
}
As above we already removing older than 5 days archive logs and then we take backup of datafiles, archive logs and control file in order.
On customer system, there were lot of activities going on and due to that there are archive logs which are within 6 days but the size of each archive log is ~93M. Our redo log size is 100M. Like this there were 160 files. So in total it took 14GB size of partition.
As above we take all archivelogs in backup that's why size of backup keep increasing and where we put backup is not sufficient and that's why backup was failing.
Now could you please guide me on following points.
1. Can we take only new archive logs generated after one backup using following command?
backup archivelog all not backed up 1 times;
Will it be safe if we want to restore and recover older backup due to some problem because of media or Oracle instance?
2. Is there any way we can plan so that so much archive logs are not backed up? Can we reduce archive log retension policy to keep only 3 days of logs?
Any other suggestions to improve backup of archive logs that reduce usage of disk size.
Thanks for reply.
Regards,
Shardul