ADSM-L

Re: Caching migrated files

1996-08-28 08:39:00
Subject: Re: Caching migrated files
From: Digest Info Refcard <Dan.Crouse AT MAILPORT.DELTA-AIR DOT COM>
Date: Wed, 28 Aug 1996 08:39:00 -0400
Tom,

Enabling caching for a disk pool can decrease your backup throughput. When
caching is enabled, the server has to delete the database records associated
with cached files to "free" the storage space.  The server then must then
add database records for the files being backed up.  You are essentially
double-dipping during the time that a backup(s) is running.  If backup speed
is a critical factor, running without caching enabled should be faster.

DanC
=============================================
Daniel G. Crouse
Software Information Services, Inc.
Email:  Dan.Crouse AT MAILPORT.DELTA-AIR DOT COM
Vmail:  800-233-6838
Voice:  404-714-5754
=============================================

> Date:    Fri, 23 Aug 1996 14:47:19 -0400
> From:    Tom Denier <tom AT STAFF.UDC.UPENN DOT EDU>
> Subject: Caching migrated files
>
> 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?
<Prev in Thread] Current Thread [Next in Thread>