Re: preventing backup of large files
2001-04-05 09:12:38
You can use the MAXSIZE parameter on your storage pool definition. If
you do not have a next storage pool defined for the pool the file will
not be backed up. Try HELP UPD STGP at a command line prompt. Look at
this partial output below:
UPDATE STGPOOL -- Primary Sequential Access
Use this command to update a primary sequential access storage pool.
Privilege Class
To issue this command, you must have system privilege, unrestricted
storage
privilege, or restricted storage privilege for the storage pool to be
updated.
Syntax
>>-UPDate STGpool---pool_name----------------------------------->
>-----+------------------------------+-------------------------->
'-DESCription--=--description--'
>-----+-----------------------------+--------------------------->
'-ACCess--=--+-READWrite---+--'
+-READOnly----+
'-UNAVailable-'
>-----+------------------------------------+-------------------->
'-MAXSIze--=--+-maximum_file_size-+--'
'-NOLimit-----------'
>-----+----------------------------+---+----------------------+->
'-NEXTstgpool--=--pool_name--' '-HIghmig--=--percent--'
>-----+---------------------+---+----------------------+-------->
'-LOwmig--=--percent--' '-REClaim--=--percent--'
>-----+-------------------------------+------------------------->
'-RECLAIMSTGpool--=--pool_name--'
>-----+------------------------------+-------------------------->
'-COLlocate--=--+-No--------+--'
+-Yes-------+
'-FILespace-'
>-----+------------------------+---+----------------------+----->
'-MAXSCRatch--=--number--' '-REUsedelay--=--days--'
>-----+--------------------+---+--------------------------+----><
'-MIGDelay--=--days--' '-MIGContinue--=--+-No--+--'
'-Yes-'
maxfilesize
Limits the maximum physical file size. Specify an integer from
1
to 999999, followed by a scale factor. For example, MAXSIZE=5G
specifies that the maximum file size for this storage pool is
5
gigabytes. Scale factors are:
Scale factorMeaning
K kilobyte
M megabyte
G gigabyte
T terabyte
If a file exceeds the maximum size and no pool is specified as the
next
storage pool in the hierarchy, the server does not store the file.
If a
file exceeds the maximum size and a pool is specified as the next
storage pool, the server stores the file in the next storage pool
that
can accept the file size. If you specify the next storage pool
parameter, at least one storage pool in your hierarchy should have
no
limit on the maximum size of a file. By having no limit on the size
for
at least one pool, you ensure that no matter what its size, the
server
can store the file.
For logical files that are part of an aggregate, the server
considers
the size of the aggregate to be the file size. Therefore, the
server
does not store logical files that are smaller than the maximum size
limit if the files are part of an aggregate that is larger than the
maximum size limit.
Note:This size limit applies only when the server is storing files
during a session with a client. The limit does not apply when
you move data from one pool to another, either manually or
automatically through storage pool migration.
Alan Davenport
Selective Insurance
alan.davenport AT selective DOT com
glee AT bsu DOT edu wrote:
>
> From: GLEE AT BSU DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: Thu, 5 Apr 2001 07:52:35 -0500
> Subject: preventing backup of large files
>
> Tsm server 3.7 on os/390,
> client v4.1 windows nt.
>
> I have a need to prevent the backup of large "rendered" video files. I
> know that the best way to do this is through an incl/excl list and not
> back up the directories where these should be stored. However, this is
> a student lab and the little darlings will probably find a way to store
> them in the "wrong" place.
>
> Is there a way to exclude from backup all files of size "x" or greater?
>
> Thanks in advance.
>
> Gary Lee
> Senior Operating Systems Analyst
> Ball State University
> phone 765-285-1310
|
|
|