Over LAN Free, it flies approx 60MBs.
Still have performance problems over IP. The backup threads run at around
15 MBs, but a restore thread runs at 4MBs. Using virtualfsmapping means
the volume can be broken down into multiple threads. However, it is still
clear that per thread the performance es
How large are you making the max size of your virtual tapes? Why?
I let my TS7520 emulating 3592E tapes default to a max size of 460GB but I'm
starting to think a smaller size would make more sense. The median size of
occupancy for my nodes is around 40GB so I'm thinking that might be a better
David,
Your question is a good one. On our EMC Disk Libraries we
emulate LTO1 tape drives, with 50GB maximum tapes. I believe this
improves overall disk utilization for just the reason you mention. You
can reclaim the smaller tapes sooner. TSM won't have to wait until
~250GB of data, wh
Here is my response to an earlier question on sizing a VTL. I have been
using a 10GB tape volume size for a couple of years and have not seen a
reason to change. I originally chose 10GB because ISM recommended that
size when using sequential file devices.
Yes that is an approach that will work.
David,
I originally set my TS7510 to the default 300GB vtape size with
dynamic allocation where only 5GB is initially allocated and the space
is grown as data is written. I found out that once data is written to a
vtape, the vtape will retain that size until it is scratched AND THEN
written to
I agree with John. We are currently using 100Gb. volumes in out DL700,
but I'm frequently called by user who's restore seems to hang.
In most cases the tape is in use by another restore or in use by a
backup storagepool/reclamation which first has to finish the file it's
backing up or reclaiming.
K
Our desktop support unit has a user that wants a new retention policy on
their file share. The admin added this to the dsm.opt:
INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget Office\*"
LONGADMIN
INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
Office\*.*" LONGADMIN
On Nov 29, 2007, at 3:23 PM, Fred Johanson wrote:
Our desktop support unit has a user that wants a new retention
policy on
their file share. The admin added this to the dsm.opt:
INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
Office\*"
LONGADMIN
INCLUDE "F:\NSIT\FieldSupport\Uni
"Does not work", his term, which means the files show up on the gui as
being in the default management class.
The new management class does not show up in "Q inclexcl".
The new management class shows up on the active policy set.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:
Nothing wrong per se, although the second INCLUDE appears redundant.
The first place to start with these kinds of issues is to use "dsmc query
inclexcl" to makes sure those files aren't being picked up by an earlier
filter.
Also make sure the updated policy was activated.
Regards,
Andy
Andy Ra
Andy,
His additions are at the bottom of his dsm.opt file. There is also a
client optionset that has:
Include ?:* FILESERVER
Fred Johanson
TSM Administrator
University of Chicago
773-702-8464
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
An
The options defined in server client optins have precidence
>From page 353 in the server guide V5.4
Any include-exclude statements in the server client option set have
priority over the include-exclude statements in the local client options
file. The server include-exclude statements are always e
There are no 'INCLUDE' lines in the option set other than the initial
one.
This is the dsm.opt:
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
EXCLUDE.BACKUP "*:\...\EA DATA. SF"
EXCLUDE.BACKUP "*:\IBMBIO.COM"
EXCLUDE.BACKUP "*:\IBMDOS.COM"
EX
Yes, but it's not position in the dsm.opt file that matters when client
option sets are at issue. Use "dsmc query inclexcl" to see the final list
that TSM actually uses.
I suspect it is that client option set that is overriding the dsm.opt
file.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tiv
OK, the Q INCLEXCL output is what we're interested in.
You read the Q INCLEXCL from the top down (opposite of the dsm.opt file).
Notice that all the dir excludes (EXCLUDE.DIR) are at the top, since those
are always filtered first, regardless of how they are positioned.
So starting from the top do
Fred, I cannot give you a definitive to answer your question since I do
not know your shop, its policies, service level agreement, etc., For
example, it could be your shop policy that the INCLUDE *:\...\* is
deliberate to prevent users from overriding via dsm.opt settings.
Having said that: removi
So how does he get what he wants. The option set is to set a management class
for a number of clients. The new management class applies to 1 of the 10.
Will setting the OVERRIDE=yes have the desired effect?
From: ADSM: Dist Stor Manager on behalf of Andrew Ra
Thanks Andy,
I'll try to make this brief. I had thought of making a special cloptset for
this client, but the machine admin figures that once this special exception
becomes known, the other 15 to 20 users of the box will want their own
exceptions. Being a nice guy, he figures I've got better
Hi Fred,
FORCE has no effect on INCLEXCL, so that's a nonstarter.
Try this: remove the INCLUDE statement from the dsm.opt file and instead
add it to the client option set on the server. But instead of using the
drive letter, use the UNC name, e.g.:
define clientopt inclexcl 'include
"\\machname
19 matches
Mail list logo
