ADSM-L

Re: determining which files will be copied to copy stgpool

2004-09-01 15:41:58
Subject: Re: determining which files will be copied to copy stgpool
From: "Levi, Ralph" <RLevi AT HESS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 1 Sep 2004 15:43:08 -0400
Rick,

You might want to check your Maximum Size Threshold on your disk storage
pools.  If files are larger than the max, they will go directly to your
primary sequential pool and bypass the disk pool (and therefore not get
to the copy tape pool until the tape to tape runs).

Ralph

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Rhodes
Sent: September 01, 2004 3:34 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: determining which files will be copied to copy stgpool


We've got a strange problem.  We run the normal tsm processes . . . .
- run backup stgpool for  primary disk pool to copy tape pool
- run migration
- run backup stgpool of the primary tape pool to the copy tape pool

For some reason after we do this, we start to get lots of files that are
in
the primary tape pool but not in the copy pool.  It's as if someone is
doing backups straight into the primary tape pool.  We've check, this
is not the problem.

So . . .I'm trying to figure out what these files are and where they
come
from.

The "backup stgpool <primarytapepool> <copytapepool> preview=yes"  cmd
tells
me how much data needs to be copies and the tape vols, but I also want
the
nodes
and the files for the nodes that need copied.

Q)   How can you tell the nodes and files that need to be copied from a
primary tape
pool to a copy tape pool?

Thanks

Rick


-----------------------------------------
The information contained in this message is intended only for the
personal
and confidential use of the recipient(s) named above. If the reader of
this
message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that
you
have received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately,
and delete the original message.