RE: RMAN Strategy - Need some input
- From: "Yasin Baskan" <yasin.baskan@xxxxxxxxxxxxxxxx>
- To: <Chris.Taylor@xxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 12 Nov 2007 17:07:36 +0200
Maybe instead of "archivelog all delete input" you can use something
like:
RMAN> backup archivelog all not backed up 1 times;
delete noprompt archivelog until time 'sysdate -2' backed up 1
times;
As used in Metalink note 361182.1.
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Taylor, Chris David
Sent: Monday, November 12, 2007 3:49 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RMAN Strategy - Need some input
Ok guys & gals, I need some input/thoughts/suggestions etc.
Lets say we have approximately 10 databases across multiple servers.
We have a catalog database on a central server on local storage.
The other 10 databases use a SAN for their storage.
In the other 10 databases we write the archivelogs to the C:\ drive
(along with a controlfile and members of redo logs)
We take full RMAN backups nightly and write them to the SAN and delete
the backed up archivelogs.
So this is what happened. Thursday evening I take an RMAN backup and
write it to the SAN and delete the archive logs from the C\ drive.
Thursday evening before those backups are written to tape we lost our
SAN. Had to reinitialize the whole SAN. So now, I have Wednesday
nights full backup with no archivelogs since I deleted them when
Thursday nights backup ran.
We have used Grid Control to create the RMAN jobs. (Script is below).
My question are these:
Can we tell RMAN to delete archivelogs that are older than 'x' date?
Instead of deleting all the archivelogs when the backups run? Or do we
have to that with a script? We are using 10.2 RMAN and some 9.2.
I don't want to leave a bunch of archivelogs on the c:\ drive due to the
space usage.
Here's the script: (replaced database name with ORCL)
run {
allocate channel oem_backup_disk1 type disk format
'F:\DBABACKUP\CURRENT\ORCL\%U';
allocate channel oem_backup_disk2 type disk format
'F:\DBABACKUP\CURRENT\ORCL\%U';
backup force noexclude as COMPRESSED BACKUPSET tag '%TAG' database
include current controlfile;
backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up
delete all input;
release channel oem_backup_disk1;
release channel oem_backup_disk2;
}
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor@xxxxxxxxxxxxxxx
Bu mesaj ve onunla iletilen tum ekler gonderildigi kisi ya da kuruma ozel ve
Bankalar Kanunu geregince, gizlilik yukumlulugu tasiyor olabilir. Bu mesaj,
hicbir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para
karsiligi satilamaz; mesajin yetkili alicisi veya alicisina iletmekten sorumlu
kisi degilseniz, mesaj icerigini ya da eklerini kopyalamayiniz, yayinlamayiniz,
baska kisilere yonlendirmeyiniz ve mesaji gonderen kisiyi derhal uyararak bu
mesaji siliniz. Bu mesajin iceriginde ya da eklerinde yer alan bilgilerin
dogrulugu, butunlugu ve guncelligi Bankamiz tarafindan garanti edilmemektedir
ve bilinen viruslere karsi kontrolleri yapilmis olarak yollanan mesajin
sisteminizde yaratabilecegi zararlardan Bankamiz sorumlu tutulamaz.
This message and the files attached to it are under the privacy liability in
accordance with the Banking Law and confidential to the use of the individual
or entity to whom they are addressed. This message cannot be copied, disclosed
or sold monetary consideration for any purpose. If you are not the intended
recipient of this message, you should not copy, distribute, disclose or forward
the information that exists in the content and in the attachments of this
message; please notify the sender immediately and delete all copies of this
message. Our Bank does not warrant the accuracy, integrity and currency of the
information transmitted with this message. This message has been detected for
all known computer viruses thence our Bank is not liable for the occurrence of
any system corruption caused by this message
Other related posts:
