Ron Pavan wrote:
> example in my env:
> all server side option sets for "excludes" are set with override = no
> all server side option sets for "includes" are set with override = yes
>
[etc]
While we're on this topic, can someone give an example of the syntax (3.7.3
on Solaris) to specify an inclu
TSM doesn't do compression on the server side other then what the tape
drives themselves are capable of. And in that case the compression (and
decompression) is done by the hardware on the tape drives and therefore has
no impact on your TSM server. Thus points 1 and 2 below aren't valid..
Points
Here's another peculiar event sequence that's showed up since upgrading the server for
backups that do not occuring thier window:
1). Backup occurs past the window time (o.k.)
2). Just as the backup is completeing a second session appears to attempt to start.
3). The original sessions completes r
H..
Well, if your drive use isn't limited, perhaps it's your randomization setting.
Unlikely, but worth a check:
For client nodes that use the client polling mode, the server uses this setting to
distribute the start times for clients over the percentage of the duration starting
with t
Check the "Maximum Size Threshold" in your disk pool as well. TSM will go
straight to the next storage pool if the file size exceeds what this value
is. I don't recall what the default value for this parameter is offhand.
Gerald Wichmann
RS Engineer
Sansia System Solutions
408-844-8893 work
408-8
