DEF STG CACHE=Yes.
So you can quick restore today's/yesterday's backups from the cache. I do
not assume your DISK pool is big enough to keep all client's data there.
If it is and you are using tapes only for archives and backupsets you can
go two ways:
have no arrays and hope only that at least one stgpool (primary or copy)
volume will stay alive.
implement arrays with redundancy.

If you have LOWMIG higher than 0% then we can predict which files will
still be there but unless you fall in DISK-BACKUP scenario for larger
restores you still will be forced to mount tapes.


Zlatko Krastev
IT Consultant





"Stephen A. Cochran" <Stephen.A.Cochran AT CAHIR DOT NET> on 10.09.2001 09:50:46
Please respond to Stephen.A.Cochran AT Cahir DOT net
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: New Server and Disk Pools

--- Mark Stapleton wrote:
I wouldn't bother with *any* kind of array. Save yourself the expense
I wouldn't bother with *any* kind of array. Save yourself the expense
and administrative overhead of an array. Just cache the disk pool and
spill it over into tape daily. Easy-peezy.
--- end of quote ---
But then you loose the quick restore from disk, and the client has to wait
But then you loose the quick restore from disk, and the client has to wait
for a
tape mount if you flush the entire disk cache to tape. Or am I missing
something?

Steve Cochran