Re: Help - backups go to tape instead of disc pool, from DB2

[William Sherrill/Lexington/Contr/IBM]

Rene,

Check the size of your DB2 database with the size of your disk storage
pool.  If *sm sees that it doesn't have enough space in its target pool, it
will then go to the next storage pool.  I have seen this with DB2, the
database exceeded the amount of space in the disk pool so it then asked for
a tape to be mounted which was defined to the next storage pool.

Bill Sherrill
Analyst International


"Lambelet,Rene,VEVEY,FC-SIL/INF." <[EMAIL PROTECTED]>@VM.MARIST.EDU>
on 10/05/2000 12:04:20 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:
Subject:  Re: Help - backups go to tape instead of disc pool, from DB2



We use no agent, backup code is included within DB2. The client Plateform
comes as R3DB2UDB in the node definition.

Our disc pools have Caching enabled NO.

What else could I check ?

Thanks,

René Lambelet
Nestec S.A. / Informatique du Centre
55, av. Nestlé  CH-1800 Vevey (Switzerland)
*+41(021) 924 3543  7 +41 (021) 924 4589  * B 133
Visit our site: http://www.nestle.com

        This message is intended only for the use of the addressee and
        may contain information that is privileged and confidential.



> -----Original Message-----
> From: Rupp Thomas (Illwerke) [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 5:57 PM
> To:   [EMAIL PROTECTED]
> Subject:      AW: Help - backups go to tape instead of disc pool, from
DB2
>
> Do you backup the DB files as flat files or do you use a TDP agent?
>
> We use the TDP agent to backup our ORACLE DB an we had to be careful
> when setting the DSMO_AVG_SIZE environment variable.
> We have caching enabled for the disk storage pools so they are always
> "full".
> When TDP tries to write to disk it acquires n megabytes (as defined with
> DSMO_AVG_SIZE)
> and therefore clears n megabytes of disk space (or maybe more as complete
> filespaces are
> removed). When the first n megabytes aren't enough TDP tries to acquire n
> more megabytes.
> Unfortunately this time cached space isn't released. As TDP now cannot
> find
> the required
> space on disk the backup data is sent to tape.
>
> This is how I was told - now we backup directly to tape
>
> Hope this helps
>
> Kind regards
> Thomas Rupp
> Vorarlberger Illwerke AG
> MAIL:   [EMAIL PROTECTED]
> TEL:    ++43/5574/4991-251
> FAX:    ++43/5574/4991-820-8251
>
> > -----Ursprüngliche Nachricht-----
> > Von:  Lambelet,Rene,VEVEY,FC-SIL/INF. [SMTP:[EMAIL PROTECTED]]
> > Gesendet am:  Donnerstag, 05. Oktober 2000 17:38
> > An:   [EMAIL PROTECTED]
> > Betreff:      Help - backups go to tape instead of disc pool, from DB2
> >
> > Hello,
> > we run adsm server 3.1.2.50, base client 3.7.2.0 and DB2 6.1.1 on AIX
> > 4.3.3
> >
> > All DB backups start and immediately ask for mount of 1 tape / session.
> > They
> > should go to the disc storage pool !
> >
> > Why? I checked disc pools ( all have NO SIZE LIMIT), I checked all
> backup
> > and archive copy groups, no one has a tape pool as destination pool.
> >
> > Please give me any clue about why these backups want to mount tapes...
> >
> > Tanks a lot,
> >
> > René Lambelet
> > Nestec S.A. / Informatique du Centre
> > 55, av. Nestlé  CH-1800 Vevey (Switzerland)
> > *+41(021) 924 3543  7 +41 (021) 924 4589  * B 133
> > Visit our site: http://www.nestle.com
> >
> >         This message is intended only for the use of the addressee and
> >         may contain information that is privileged and confidential.
> >
> >