Re: Setting Client Environmental variables-3.7.3 AIX client

[Michel Engels]

The two options you have to specify in the dsm.sys are:
Errorlogname  /admin/local/logs/dsmerror.log
Schedlogname  /admin/local/logs/dsmerror.log

Another thing you can specify is de retention period of the messages:
Errorlogretention   30 D
Schedlogretention   30 D

Hope this helps,

Michel Engels
TSM Consultant
Devoteam Belgium





Ken Sedlacek <[EMAIL PROTECTED]> on 07/23/2001 05:21:28 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: Michel Engels/BE/Devoteam)

Subject:  Setting Client Environmental variables-3.7.3 AIX client



I have pored over the TSM "Installing The Clients 3.7 manual"  on this
question, and it is unclear as to the actual practice.

My AIX client (AIX 4.3.3, TSM 3.7.3 client) observation:
At times , the dsmsched.log files are in the / directory. At other times,
they seem to move to the /usr/tivoli/tsm/client/ba/bin directory (I know it
sounds strange, but it has happened).

Question:
How do you specify where the "dsmsched.log" is located?

"Installing The Clients 3.7 manual" Answer:
Put the environmental variable DSM_LOG into either dsm.sys or dsm.opt file
and put the path where the .log file should go.

My dsm.sys & dsm.opt files don't specify the DSM_LOG variable.

I don't know whether to chance putting the DSM_LOG in there and see what
happens or what.

What I need is some advice from you!

Do you use the DSM_LOG variable in your dsm.sys or dsm.opt file?
or how do you specify where the dsmsched.log file goes??


TIA

Ken Sedlacek
Kyrus Corporation
Office: 864-322-4260; Cell: 864-444-8375
Text Page: 864-444-7243, follow prompts
[EMAIL PROTECTED]

Kyrus IT Support  (Internal: 4399)   (Greenville: 864-322-4399)
(Toll-Free: 888-413-4399)

Joseph M Marchesani/NYM/Equitable is out of the office.

[Joseph Marchesani]

I will be out of the office from 07/23/2001 until 08/06/2001.

I will respond to your message when I return., In my absence forward all
Tsm requests to Jim Healy

Setting Client Environmental variables-3.7.3 AIX client

[Ken Sedlacek]

I have pored over the TSM "Installing The Clients 3.7 manual"  on this
question, and it is unclear as to the actual practice.

My AIX client (AIX 4.3.3, TSM 3.7.3 client) observation:
At times , the dsmsched.log files are in the / directory. At other times,
they seem to move to the /usr/tivoli/tsm/client/ba/bin directory (I know it
sounds strange, but it has happened).

Question:
How do you specify where the "dsmsched.log" is located?

"Installing The Clients 3.7 manual" Answer:
Put the environmental variable DSM_LOG into either dsm.sys or dsm.opt file
and put the path where the .log file should go.

My dsm.sys & dsm.opt files don't specify the DSM_LOG variable.

I don't know whether to chance putting the DSM_LOG in there and see what
happens or what.

What I need is some advice from you!

Do you use the DSM_LOG variable in your dsm.sys or dsm.opt file?
or how do you specify where the dsmsched.log file goes??


TIA

Ken Sedlacek
Kyrus Corporation
Office: 864-322-4260; Cell: 864-444-8375
Text Page: 864-444-7243, follow prompts
[EMAIL PROTECTED]

Kyrus IT Support  (Internal: 4399)   (Greenville: 864-322-4399)
(Toll-Free: 888-413-4399)

TSM Versions

[Doug McLauchlan]

Hi all, Is there a table/chart/grid anywhere that will show which
versions of TSM client/server that you can run together. I have a TSM Server
at 3.7.2 and we have a trial version of HSM which is at 4.2 which also needs
the BA Client at 4.2. Can I have a version 4 client running with a 3.7
server ???


Thanks  Doug McLauchlan
DISCLAIMER: "The information in this email and in any attachments is confidential and 
intended solely for the attention and use of the addressee(s). If this email is not 
intended for you, you must not use, read, distribute or copy it. If you have received 
this email by mistake please call the sender immediately on 64-9-2620772 and erase the 
email and any attachments, and any copies of the same. Internet communications are not 
secure and therefore Woolworths (NZ) Ltd does not accept legal responsibility for the 
contents of this message. Any views or opinions expressed are solely those of the 
author and do not necessarily represent those of Woolworths (NZ) Ltd unless 
specifically stated."

Re: Automated monitoring of backup

[Steve Harris]

Geoff,

I use an appropriate postshedulecommand to ftp or scp the dsmched.log files from each 
node back to a central directory.

Once daily I run a perl script that makes three checks

1. q event
2. Is there a log file from this node for today (I only have one node that doesn't 
back up daily)
3. Parses each log file looking for failures.

Results are emailed to me


HTH

Steve Harris
AIX and TSM admin
Queensland Health
Brisbane Australia

>>> "Gill, Geoffrey L." <[EMAIL PROTECTED]> 21/07/2001 2:12:05 >>>
To all,

I'm wondering how others are monitoring their nightly backups for
completion. Currently our operations people use the web interface to monitor
backups. I've been asked to find a way to help work this out so information
is fed somewhere from somewhere automatically. I am not a programmer or dba
so my expertise is limited, actually probably non existent, as it relates to
making this happen on my own.

Do any of you have some suggestions as to how to make this work? Can you
pass along any scripts that would help me? Would this be done from the TSM
server and sent out or is it possible to run this from one computer by
pulling the data from TSM and sending it to a different computer?

If I have to re-invent the wheel it probably won't come out round.
Thanks,

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   [EMAIL PROTECTED] 
Phone:  (858) 826-4062
Pager:   (888) 997-9614

Re: AW: Include Exclude Problem

[John Freeman]

Thanks...it worked

- Original Message -
From: "Rupp Thomas (Illwerke)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 22, 2001 5:46 PM
Subject: AW: Include Exclude Problem


> Hi John,
>
> the problem is that TSM reads the include/exclude list from bottom to top.
> You could code:
>
> DOMAIN D:
>
> EXCLUDE "d:\...\*"
> INCLUDE "d:\data\...\*"
>
> This excludes drive C: completely (data files and directories).
> The INCLUDE/EXCLUDE list (read from bottom to top) means:
> include all files in d:\data and all subdirectories
> exclude all other files in d:\ and all subdirectories. The directory
> structure
> of d: is still backed up completely.
> If you want to exclude the directories as well you have to use EXCLUDE.DIR
> in addition.
>
> HTH
> Thomas
>
>
>
> --

> Dieses eMail wurde auf Viren geprueft.
>
> Vorarlberger Illwerke AG
> --

Re: Include Exclude Problem

[s frederic johanson]

The list works from bottom to top.  I think your second version is what
you want if you switch the two lines.



On Sun, 22 Jul 2001, John Freeman wrote:

> Fellow TSM's
>
> As a TSM newbie I am having some difficulty configuring an incl excl list.
>
> (Windows Client 4.1.3 to Windows Server 4.1.0)
>
> I want to backup a single directory on the D drive of a client and want to exclude 
>everything else on both C and D drives.
>
> My incl_excl file looks as follows:
>
> include "d:\data\*"
> exclude "c:\*"
>
> I have also tried the following:
>
> include "d:\data\*"
> exclude "*"
>
> The first combination backs up everything and the second one backs up nothing.
>
> Some help would be greatly appreciated.
>
> Rgds
> John
>

AW: Include Exclude Problem

[Rupp Thomas (Illwerke)]

Hi John,

the problem is that TSM reads the include/exclude list from bottom to top.
You could code:

DOMAIN D:

EXCLUDE "d:\...\*"
INCLUDE "d:\data\...\*"

This excludes drive C: completely (data files and directories).
The INCLUDE/EXCLUDE list (read from bottom to top) means:
include all files in d:\data and all subdirectories
exclude all other files in d:\ and all subdirectories. The directory
structure
of d: is still backed up completely.
If you want to exclude the directories as well you have to use EXCLUDE.DIR
in addition.

HTH
Thomas



--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Include Exclude Problem

[John Freeman]

Fellow TSM's

As a TSM newbie I am having some difficulty configuring an incl excl list.

(Windows Client 4.1.3 to Windows Server 4.1.0)

I want to backup a single directory on the D drive of a client and want to exclude 
everything else on both C and D drives.

My incl_excl file looks as follows:

include "d:\data\*"
exclude "c:\*"

I have also tried the following:

include "d:\data\*"
exclude "*"

The first combination backs up everything and the second one backs up nothing.

Some help would be greatly appreciated.

Rgds
John

TIVsm-BA-4.2.0-1 and passwordaccess generate on Linux

[Mike Berkley]

I've recently installed a machine running Linux Mandrake 8.0 with
TIVsm-BA-4.2.0-1.  I've been using ADSM clients under Linux for a few
years, but now I cannot get "PASSWORDACCESS GENERATE" to actually
generate a password.  I cannot even get "dsmc inc -password=" to
work without prompting for a password.

Has anybody noticed something like this, or perhaps know of a
workaround?  Do I require particular permissions on the PASSWORDDIR
directory?

Thanks.

MediaW slows restore significantly

[Suad Musovich]

Has anyone noticed when doing a restore from tape it almost grinds down
to a halt when another process/session requests the same tape?

We had this happen when an impatient client decided to run 2 restores, where
the data on the 2nd restore was on the same tape. The restore slowed from
5MB/s to 30kB/s. When I killed the 2nd restore session it speed up.

Similarly, later that evening, the system decided to migrate data to that
same volume and it did the same thing.

Bug/feature?

Cheers, Suad
--

Re: LTO Devices

[Suad Musovich]

Your questions on the drive don't make sense unless you are talking about a
LTO library as most physical interactions with drives usually rely on a couple
of buttons(and maybe a lever).

Competing with DLT they do well as they are a newer, faster, more economical tape
format, but they do have their weak points:
- Long seek times
- Long unload times.
- Worse start/stop characteristics

Don't let the above comments put you off. I can make a longer, more profanic, list
of problems with DLT tapes.
Look at your backup requirements, if you have a need for volume data with a
relative budget, it's for you.

If I was to repeat the exercise of choosing from scratch again, I would pick
LTO. We can't afford 3590 and we have lost confidence in DLT.

Cheers, Suad
--


On Thu, Jul 19, 2001 at 10:07:02AM -0400, Bill Wheeler wrote:
> Hello All,
>
> I have seen over the list that there are a group of people that use
> LTO tape drives.   We are looking into purchasing one to work with our
> system.  I was wondering what type of feedback there is about these drives.
> Are they easy to work with, worth purchasing, making life easier for all...
> Any information would be helpful.
>
>
> Thanks in Advance,
>
> Bill Wheeler
> AIX Administrator
> La-Z-Boy Incorporated
> [EMAIL PROTECTED]