RE: Backup VLDB's
- From: hrishy <hrishys@xxxxxxxxxxx>
- To: A Ebadi <ebadi01@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>, "Mark W. Farnham" <mwf@xxxxxxxx>, Nizar Ahmed <gnahmed.c@xxxxxxxxxx>
- Date: Mon, 23 Nov 2009 07:20:58 +0000 (GMT)
incremental merges to copy is feature available in 10g.Just For your info
--- On Sat, 21/11/09, Nizar Ahmed <gnahmed.c@xxxxxxxxxx> wrote:
From: Nizar Ahmed <gnahmed.c@xxxxxxxxxx>
Subject: RE: Backup VLDB's
To: "A Ebadi" <ebadi01@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx"
<oracle-l@xxxxxxxxxxxxx>, "Mark W. Farnham" <mwf@xxxxxxxx>,
"hrishys@xxxxxxxxxxx" <hrishys@xxxxxxxxxxx>
Date: Saturday, 21 November, 2009, 7:17
Thanks Abdul but the nature of my application is not a DWH but an ODS –
operational data store. There are more writes with a 6 month retention.
Incremental merges to a copy of backup is a 11g feature right?
Thanks,
G. Nizar A. Baig
From: A Ebadi [mailto:ebadi01@xxxxxxxxx]
Sent: Thursday, November 19, 2009 9:48 PM
To: Nizar Ahmed; oracle-l@xxxxxxxxxxxxx; Mark W. Farnham; hrishys@xxxxxxxxxxx
Subject: RE: Backup VLDB's
What about focusing on setting as much of the data as you can readonly so you
backup a much smaller subset! We have a 60TB data warehouse and have been
lucky enough to set most of the data readonly. Only 15TB of the entire DB is
read/write allowing us to not only back it up today via RMAN, but also scale
into the future!
FYI, we are also utilizing compression within the DB…
Thanks,
Abdul
--- On Tue, 11/10/09, hrishy <hrishys@xxxxxxxxxxx> wrote:
From: hrishy <hrishys@xxxxxxxxxxx>
Subject: RE: Backup VLDB's
To: "'Nizar Ahmed'" <gnahmed.c@xxxxxxxxxx>, oracle-l@xxxxxxxxxxxxx, "Mark W.
Farnham" <mwf@xxxxxxxx>
Date: Tuesday, November 10, 2009, 10:24 PM
Hi
what's the fastest way to backup" is because I need read response time in
seconds on these huge tables. I do not want the RMAN backup window to run for
most of the day thereby putting a load on the overall system performance. We do
use block change tracking and run a differential incremental on weekdays to
keep the sizes of the backup small.
You basically have 2-3 options
a)Do incremental merges to a copy of the backup as i mentioned earlier as i
guess this is the path of least resistance since from your signature i can see
you are a telecom company this link might be helpful (http://bit.ly/8SCjg) you
might be able to convince your management easily.
b)EMC split mirror option if you decide to go that route
c)if you do not do nologging operations then use a physical standby and run
your backups from there but in order to take full advantage like block change
tracking file incremental merges etc you need to be on 11g.
reading this mail chain at thsi point of time my choice is a)
Not in choice you if things go wrong you dont restore from backup you switch to
the copy .
Choice a is not absolute but you need to do some testing and see if it meets
your specific requirements.
The information in this email may contain confidential material and it is
intended solely for the addresses. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, please delete the email
and destroy any copies of it, any disclosure, copying, distribution is
prohibited and may be considered unlawful. Contents of this email and any
attachments may be altered, Statement and opinions expressed in this email are
those of the sender, and do not necessarily reflect those of Saudi
Telecommunications Company (STC).
قد يحتوي هذا البريد الالكتروني على معلومات سرية موجهة إلى الأشخاص المرسلة لهم
فقط ولا يصرح لأي شخص آخر الاطلاع عليها، وفي حال استلام هذا البريد الالكتروني
بشكل خاطئ فإنه يجب حذفه وإبلاغ المرسل بشكل مباشر. وأي تسريب لتلك المعلومات أو
نسخها أو نشرها يعد أمراً مخالفاً وقد يؤدي إلى المسائلة القانونية، كما أن الآراء
المذكورة بهذا البريد تمثل رأي مرسلها ولا تعبر بالضرورة عن رأي شركة الاتصالات
السعودية
Other related posts:
