ADSM-L

FW: Advisibility of disk pools as "landing pads" only?

1998-03-20 08:23:18
Subject: FW: Advisibility of disk pools as "landing pads" only?
From: "Nichols, Linnea" <lnichols AT FFXEX01.CO.FAIRFAX.VA DOT US>
Date: Fri, 20 Mar 1998 08:23:18 -0500
> -----Original Message-----
> From: Nichols, Linnea
> Sent: Friday, March 20, 1998 5:20 AM
> To:   IBM-Main (E-mail)
> Subject:      FW: Advisibility of disk pools as "landing pads" only?
>
> Are you doing BACKUP STGPOOL to create copy storage pools?
> If you are, you might want to keep your disk pools big enough to
> get your BACKUP STGPOOL done before you migrate them.
> Otherwise you incur lots of tape mounts to get the BACKUP
> STGPOOL done.
>
> I try to make my disk storage pools big enough to hold one
> nights worth of backups (although I have one client with a
> large database that never makes it). I then do my BACKUP
> STGPOOL in the morning, and then migrate the disk pool
> to tape in the afternoon so that it's empty to start the next
> nights backups.
>
> -----Original Message-----
> From: Allen S. Rout [SMTP:asr AT CORNPONE.NERDC.UFL DOT EDU]
> Sent: Thursday, March 19, 1998 7:07 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Advisibility of disk pools as "landing pads" only?
>
> Greetings, all.
>
> I'm getting ready to define a set of disk storage volumes for my ADSM
> setup,
> with the intent that I would be using them as a more-or-less "landing
> pad";
> i.e. they can accept data more efficiently than the optical or tape,
> and I can
> run more simultaneous sessions against them, but I don't really plan
> to keep
> data on them for long:  my nightly incrementals might regularly exceed
> the
> size of the disk pool.
>
> Someone here noted today "but that might cause migration, which I
> would want
> to avoid during the backup window".  Is there a reason to avoid that,
> _other_
> than simply losing access to the migrating volume during the migration
> period?
>
> Is this a dumb idea for some other reason?  I plan to have rather a
> lot of
> fairly small spindles for disk pool: I won't lose a lot if a few of
> them go
> into migration during a session, and I can migrate _all_ the data off
> gradually during the day, so I can have a clean slate for the next
> night.
>
> Any input, or references to Fine Manuals that I might Read, would be
> welcome.
>
>
> -Allen S. Rout
<Prev in Thread] Current Thread [Next in Thread>