This has been a long thread (interesting, but long)...I can't help but throw
my 2 cents in. The bottom line is not whether a hot backup strategy or a
cold backup strategy is better. They are both equally as good as the other.
What should dictate which you should use is the business needs. Each
business is different and therefore has different requirements. Your backup
strategy should be tailored to these requirements. As Andrew states below,
each business has a budget which may also come into play as to which is the
best backup strategy. Every business does not the luxury of having all the
hardware required to put a standby database in place or the option of
shutting down the database. I use both cold and hot backups depending on
the business requirements imposed on each particular database. I also use
exports for the same reason Andrew uses them. While exports don't really
play a role in database recovery, they come in very handy when a single
table may have had rows accidentally removed or updated.

-- Gary Orr
DBA OCP, System Services

-----Original Message-----
From: Kerber Andrew
[mailto:oracledba-ezmlmshield-x80387004.[Email address protected]
Sent: Tuesday, March 29, 2005 9:46 AM
To: LazyDBA Discussion
Subject: RE: Re[4]: JUST CURIOUS WHAT ANSWERS I WILL GET ...

Yes, it would be great to have a standby database, just sitting there.
Unfortunately, our budget doesnt allow for it. Nor can we wait a day until
we apply transactions. It would also be nice to be able to keep data from
being changed once it is entered in the system. However, my users get testy
about not being able to change their own data. We need the exports probably
once every three months, or even less often. However, when we do need them,
there is no real substitute.

When the time came to make the tradeoff between accessibility and data
protection, we obviously went more to the accessibility side than you did.

-----Original Message-----
From: Paul Murgatroyd
[mailto:oracledba-ezmlmshield-x35129396.[Email address protected]
Sent: Tuesday, March 29, 2005 08:22
To: LazyDBA Discussion
Subject: Re[4]: JUST CURIOUS WHAT ANSWERS I WILL GET ...


If your main use for recovery is because data is being changed or deleted
accidently, I would say that you have more serious issues than a backup
strategy :-)

Your application should really not be allowing people to do anything
"accidently". Backups should primarly be for recovery from media failure or
site failure. Protecting the system from your users is a secondary function
(in my view), and I would be looking to find out why this is your most
common reason for needing backups.

Sounds like a better solution for your current situation would be to run a
standby database with a 1 day delay on applying transactions.

Regards,

Paul

*********** ORIGINAL MESSAGE ***********

On 29/03/2005 at 8:00 AM Kerber Andrew wrote:

We use a combination of both hot backups and exports. We are not in a RAC
environment. To restore data from backup typically you take the users off.
We dont like to do this since we have a large number of users using many
different applications. Our most common recovery need is restoring data
that has been changed or deleted accidently. We can use daily exports to
selectively reload tables from the previous day while still maintaining
maximum availability.




--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html



--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html


Oracle LazyDBA home page