-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The answer to this particular question is probably not all that
informative. Whether or not your are running a "typical" scenario
is less important than whether you are running a scenario that
works best for your business.
The question that most needs answering is what is your target
time to recover? If the following schedule allows you to recover
a downed production database within your given time frame, then
yes, your proposed schedule is a good one. If, however, the
proposed scenario would mean a 12 hour recovery window, and your
managerrs have determined that a 2 hour window is all that is
allowable, then you will have to rethink your strategy.
Work the problem from the recovery end, rather than the backup
end. Figure out how long you have to recover, then consider the
backup alternatives that will all you to recover your database
within that time frame.
-- Tom
Thomas A. La Porte
DreamWorks SKG
[EMAIL PROTECTED]
On Tue, 13 Mar 2001, Jane Doe wrote:
>Given the following scenario,
>Full DB backup on SAT
>Incremental backup on Sun-Fri
>
>If I have a huge database, say 2 TB, Is this a typical scenario as far as
>schedules are concerned?
>
>
>
>
>
>_______________________________________________________
>Send a cool gift with your E-Card
>http://www.bluemountain.com/giftcenter/
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6rrMe+XzOe82U4SIRAkpfAJ4h/U8Xm6Spby2AB6VHONDgH9QoFwCdEJ1C
6/4mUQbakPv9NwJ4D+0rRoI=
=9e8B
-----END PGP SIGNATURE-----
