Re: Caching migrated files
1996-08-26 11:33:10
Subject: |
Re: Caching migrated files |
From: |
Dwight Cook <decook AT AMOCO DOT COM> |
Date: |
Mon, 26 Aug 1996 10:33:10 -0500 |
caching requires more DB space (and the associated overhead) I've
always run with caching on... I keep it on in case our production
machine crashes and the potential loss is in the millions of dollars
per hour that production is down.... plus the fact that we only have
two tape drives in our atl... but I'm in the process of fixing that
currently... ;-)
______________________________ Reply Separator _________________________________
Subject: Caching migrated files
Author: ADSM-L at unix,mime/dd.RFC-822=ADSM-L\@VM\.MARIST\.EDU
Date: 8/23/96 2:47 PM
By default, disk storage pools are defined with caching of migrated files
enabled. This means that files migrated to tape are not deleted from the
disk storage pool until the space they occupy is needed to accomodate
newly arrived files. If a client requests a restore of a cached file
the restore can be done with no tape mount. I recently inherited
responsibility for an ADSM server whose disk storage pools have
caching of migrated files disabled. Is there any conceivable reason
why I would not want to enable caching for these storage pools?
|
|
|