Re: TSM testing

2005-09-30 Thread Stapleton, Mark
Telnet, ftp, and ping all use their own TCP ports, as does ssh. You need
to talk to your network people to see if port 1500 (the default TSM
client-server communication port) is available between the two machines.


--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
 Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Berbee Information Networks
Office 262.521.5627

 

>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
>Behalf Of Aaron Becar
>Sent: Friday, September 30, 2005 7:36 PM
>To: ADSM-L@VM.MARIST.EDU
>Subject: Re: TSM testing
>
>Mark,
>
>I can remote into the box from the TSM server, I can ping the box from
>the TSM server, and can telnet the box from the TSM Server, 
>but I cannot
>ssh into the TSM server from the client, http to the TSM 
>server from the
>client, Administrate the TSM server from 1580 from the client, BUT...I
>can ping the TSM server from the client.  Any ideas?
>
>Thanks!
>
>Aaron
>
[EMAIL PROTECTED] 09/30 12:57 pm >>>
>[Please respond to the list.]
>
>Are you sure that TCP port 1500 open between the server and client?
>
>--
>Mark Stapleton ([EMAIL PROTECTED])
>IBM Certified Advanced Deployment Professional
>Tivoli Storage Management Solutions 2005
>IBM Certified Advanced Technical Expert (CATE) AIX
>Berbee Information Networks
>Office 262.521.5627
>
>
>
>>-Original Message-
>>From: Aaron Becar [mailto:[EMAIL PROTECTED]
>>Sent: Friday, September 30, 2005 6:24 PM
>>To: Stapleton, Mark
>>Subject: TSM testing
>>
>>Mark,
>>
>>Thanks, however, this is a new client on Windows 2003 and when
>>I first open the client it asks what would you like to do, and
>>i choose the first one, configure backup archive client.  It
>>then asks the name of the Node, and then the server, and the
>>port number.  When I click finish, it reports a TCP/IP error.
>>I can ping the server, but I cannot connect to the TSM server.
>>Thanks!
>>
>>Aaron
>>
>


Re: TSM testing

2005-09-30 Thread Aaron Becar
Mark,

I can remote into the box from the TSM server, I can ping the box from
the TSM server, and can telnet the box from the TSM Server, but I cannot
ssh into the TSM server from the client, http to the TSM server from the
client, Administrate the TSM server from 1580 from the client, BUT...I
can ping the TSM server from the client.  Any ideas?

Thanks!

Aaron

>>>[EMAIL PROTECTED] 09/30 12:57 pm >>>
[Please respond to the list.]

Are you sure that TCP port 1500 open between the server and client?

--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Berbee Information Networks
Office 262.521.5627



>-Original Message-
>From: Aaron Becar [mailto:[EMAIL PROTECTED]
>Sent: Friday, September 30, 2005 6:24 PM
>To: Stapleton, Mark
>Subject: TSM testing
>
>Mark,
>
>Thanks, however, this is a new client on Windows 2003 and when
>I first open the client it asks what would you like to do, and
>i choose the first one, configure backup archive client.  It
>then asks the name of the Node, and then the server, and the
>port number.  When I click finish, it reports a TCP/IP error.
>I can ping the server, but I cannot connect to the TSM server.
>Thanks!
>
>Aaron
>


Re: TSM testing

2005-09-30 Thread Stapleton, Mark
[Please respond to the list.]

Are you sure that TCP port 1500 open between the server and client?

--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
 Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Berbee Information Networks
Office 262.521.5627

 

>-Original Message-
>From: Aaron Becar [mailto:[EMAIL PROTECTED] 
>Sent: Friday, September 30, 2005 6:24 PM
>To: Stapleton, Mark
>Subject: TSM testing
>
>Mark, 
> 
>Thanks, however, this is a new client on Windows 2003 and when 
>I first open the client it asks what would you like to do, and 
>i choose the first one, configure backup archive client.  It 
>then asks the name of the Node, and then the server, and the 
>port number.  When I click finish, it reports a TCP/IP error.  
>I can ping the server, but I cannot connect to the TSM server. 
> Thanks! 
> 
>Aaron 
>


Re: Initial Testing and Node Registration

2005-09-30 Thread Stapleton, Mark
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Aaron Becar
>Currently running TSM 5.2 on Fedore Core 3
>
>The server starts up fine, and the server webclient works fine, only
>when working on the server itself.
>
>When I try to connect to the server from a Client Node, a Windows 2003
>Advanced Server, I get a TCP/IP error.
>I have configured the port to 1521 and I make sure to put that
>information in.

No, it is not a Windows problem. You have to make the TCPPORT match on
both the client and the server. Add

TCPPORT 1521

to the dsm.opt file on the client, and your situation should improve.

--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
 Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Berbee Information Networks
Office 262.521.5627


Re: Initial Testing and Node Registration

2005-09-30 Thread Aaron Becar
To all:

We are currently in our testing phase, and are new to TSM.  Here is our
configuration

Currently running TSM 5.2 on Fedore Core 3

The server starts up fine, and the server webclient works fine, only
when working on the server itself.

When I try to connect to the server from a Client Node, a Windows 2003
Advanced Server, I get a TCP/IP error.
I have configured the port to 1521 and I make sure to put that
information in.

Here is our server .opt file, and the startup screne.  Remeber, this is
not a robust or ideal enviornment, but I believe it should work?
Thanks!

server opt file
---
*** IBM TSM Server options file
*** Refer to dsmserv.opt.smp for other options

COMMMETHOD TCPIP
COMMMETHOD HTTP

TCPPORT 1521
HTTPPort 1580

TCPWindowsize 16

DEVCONFIG devcnfg.out

--END--


Server Startup Information
---
[EMAIL PROTECTED] bin]# ./dsmserv

Tivoli Storage Manager for Linux/i386
Version 5, Release 2, Level 2.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2003. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure

restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR7800I DSMSERV generated at 08:54:48 on Dec 16 2003.
ANR7801I Subsystem process ID is 4091.
ANR0900I Processing options file dsmserv.opt.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 8 megabytes.
ANR0201I Database assigned capacity is 16 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR0354I Recovery log redo pass in progress.
ANR0355I Recovery log undo pass in progress.
ANR0352I Transaction recovery complete.
ANR1635I The server machine GUID,
24.ae.03.65.26.31.da.11.91.23.00.0f.1f.7f.80.e2, has initialized.
ANR2100I Activity log process has started.
ANR4726I The NAS-NDMP support module has been loaded.
ANR1305I Disk volume /opt/tivoli/tsm/server/bin/backup.dsm varied
online.
ANR1305I Disk volume /opt/tivoli/tsm/server/bin/archive.dsm varied
online.
ANR0984I Process 1 for EXPIRATION started in the BACKGROUND at 12:28:35
PM.
ANR0811I Inventory client file expiration started as process 1.
ANR2803I License manager started.
ANR8200I TCP/IP driver ready for connection with clients on port 1521.
ANR8226I TCP/IP administrative driver ready for connection with clients
on port 1500.
ANR8190I HTTP driver ready for connection with clients on port 1580.
ANR0812I Inventory file expiration process 1 completed: examined 0
objects, deleting 0 backup objects, 0 archive objects, 0
DB backup volumes, and 0 recovery plan files. 0 errors were encountered.

ANR0985I Process 1 for EXPIRATION running in the BACKGROUND completed
with completion state SUCCESS at 12:28:35 PM.
ANR0993I Server initialization complete.
ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for
use.
ANR2560I Schedule manager started.
TSM:MYTSMSERVER>
ANR0440W Protocol error on session 9 for node  () - invalid verb header
received.
ANR0406I Session 10 started for node TSMSERVER (Linux86) (Tcp/Ip
tsmserver(32887)).
ANR0422W Session 10 for node TSMSERVER (Linux86) refused - node name not
registered.
ANR0403I Session 10 ended for node TSMSERVER (Linux86).
ANR0407I Session 20 started for administrator ADMIN (WebBrowser) (HTTP
tsmserver(32898)).
ANR0405I Session 20 ended for administrator ADMIN (WebBrowser).
ANR2017I Administrator ADMIN issued command: REGISTER NODE
TSMServerBackup ?***? CONTACT=Aaron Becar DOMAIN=HI_CRIT
COMPRESSION=CLIENT AUTOFSRENAME=NO ARCHDELETE=YES BACKDELETE=NO
FORCEPWRESET=NO TYPE=CLIENT KEEPMP=NO MAXNUMMP=2 URL=http:/
/10.5.226.136:1581 VALIDATEPROTOCOL=NO TXNGROUPMAX=0 DATAWRITEPATH=ANY
DATAREADPATH=ANY SESSIONINIT=CLIENTORSERVER
ANR0406I Session 91 started for node TSMSERVER (Linux86) (Tcp/Ip
tsmserver(32969)).
ANR0422W Session 91 for node TSMSERVER (Linux86) refused - node name not
registered.
ANR0403I Session 91 ended for node TSMSERVER (Linux86).
ANR0406I Session 92 started for node TSMSERVER (Linux86) (Tcp/Ip
tsmserver(32970)).
ANR0422W Session 92 for node TSMSERVER (Linux86) refused - node name not
registered.
ANR0403I Session 92 ended for node TSMSERVER (Linux86).
ANR0406I Session 93 started for node TSMSERVER (Linux86) (Tcp/Ip
tsmserver(32971)).
ANR0422W Session 93 for node TSMSERVER (Linux86) refused - node name not
registered.
ANR0403I Session 93 ended for node TSMSERVER (Linux86).
ANR0407I Session 101 started for administrator ADMIN (WebBrowser) (HTTP
tsmserver(32982)).
ANR0405I Session 101 ended for administrator ADMIN (WebBrowser).
ANR2017I Administrator ADMIN issued command: UPDATE NODE TSMSERVERBACKUP
?***? CONTACT=Aaron Becar DOMAIN=HI_CRIT
COMPRESSION=CLIENT AUTOFSRENAME=NO ARCHDELETE=YES BACKDELETE=NO
FORCEPWRESET=NO KEEPMP=NO MAXNUMMP=2 URL=http://10.5.226.13
6:1581 WHEREDOMAIN=HI_CRIT VALIDATEPROTOCOL=NO TXNGROUPMAX=0
DATAWRITEPATH=ANY DATAREADPATH=ANY
ANR0406I Session 131 started for node TSMSERVER (Linux86) (Tcp

Re: Is client upgrading necessary at this time?

2005-09-30 Thread Andrew Raibeck
At a minimum, your main concern should be that your TSM client software
level is supported with your TSM server level. In order to ease migration
to new levels, client and software are supported one release up or down.
By "release", I refer to the first two parts of the version number, e.g.,
5.3 (Version 5, Release 3).

Thus the 5.2 client is supported with a 5.1 and 5.3 server, and a 5.2
server can support a 5.1 or 5.3 client. Other examples: 4.2 server
supported 4.1 and 5.1 clients; 4.2 client was supported with 4.1 and 5.1
server.

The idea is that when you move from a 5.2 to 5.3 server (for example),
your 5.2 clients will still work with the new 5.3 server until you can get
the clients upgraded. Or if you use the 5.2 server and choose to upgrade
your clients first, you can upgrade the clients to 5.3 and they will still
be supported with a 5.2 server until you can get the server upgraded.
While it is likely that a 4.2 (for example) client will function at least
minimally with a 5.2 server, technically it is not supported, so you use
at your own risk. But lots of people continue to use very backleveled
clients, usually because those clients are no longer supported by IBM, but
the user still has them in their environment.

Caveat: 4.1 and 4.2 are no longer in service. Service for 5.1 ends today
(end of September), except for S/390, which I think is in service through
the first week of April, 2006.

Your service agreement for TSM client and server is based on your TSM
server version. The clients are considered a part of the server version
that corresponds to the server that you are running. So if you are
licensed for the TSM 5.1 server on AIX, then when that server goes
end-of-service, so do your clients. If you are licensed for the 5.1 AIX
server, but you are using 5.2 clients on some machines, you will no longer
be able to get technical support from IBM for those clients once your
server version (at 5.1) goes end of service.

With regard to the "one level back" support, you will no longer be able to
get support for the back-leveled component once that component goes
end-of-service, even if your server version is still in service. Thus if
you are licensed for the TSM 5.2 server for Windows, you will not be able
to receive support for your 5.1 clients.

I realize that a lot of this seems pretty complicated, but conceptually
it's fairly simple. The upshot is that IBM supports a one-release
difference between client and server as long as your server and client
versions have not yet reached end-of-service. And *your* support from IBM
is based on the version of the TSM *server* you are running.

Note that there are some exceptions to the above rules. For example, the
TSM 5.2 server shipped support for Windows NT 4.0 clients at the 5.1
client level. Since this client was shipped with the 5.2 server, IBM will
continue to support this client (but not other 5.1 clients) until TSM 5.2
goes out of service. Only 5.2 server licensees will receive support.
Support for NT 4.0 clients will end when 5.2 goes out of service, though
that date has not yet been announced as far as I know.

So having said all of that, you are still encouraged, in general, to get
your client and server versions as up to date as possible, with the client
at the same release as the server. For example, the 5.2 client with 5.3
server is supported primarily for migration purposes; you should be moving
forward with a plan to migrate your clients to the same server version. In
general, I'd advise upgrading your server first, then your clients. Beyond
that, your need to upgrade should be based on the impact of defects that
are fixed in later client fix packs (5.2.2, 5.2.3, etc.) and interim fixes
(5.2.2.1, 5.2.2.4, etc.).

In your case, since your NetWare clients are at 5.2 and your server is at
5.3, I'd recommend getting the most current 5.3 NetWare client. But you do
not need to try to match your client version to the server based on the
third and fourth parts of the version. That is, matching the "5.3" part is
sufficient. You don't need to worry about matching beyond that.

As for client and server requirements, see the URL in my sig, and from
that page (which I recommend bookmarking), and look for the "server
requirements" and "client requirements" links.

I hope this makes some sense... for the most part, it's really not as
complicated as the write-up would make you think. I just provided a bunch
of detail that is applicable for any TSM releases, so next time someone
asks, I can point them to this in the archives. :-)

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy o

Is client upgrading necessary at this time?

2005-09-30 Thread Timothy Hughes
Hello,

We currently have all but 1 novell TSM clients running 5.2.2 all
running fine although one backup is still running slow and needs
tuning is there any reason that I would need to upgrade to a
higher level client? I believe I read in one of the TSM manuals
that is helpful to keep the clients as close as possible to the TSM
server level. Our TSM server is currently at 5.3.1.4, Other than
that if everything is running ok is there any reason to upgrade? Also,
I know there is a minimum requirements for clients page can someone
email me the link.

AIX RS/6000
Novell clients 5.2.2
TSM version 5.3.1.4

Thanks in advance!


Re: TSM Mac Client 5.3

2005-09-30 Thread Andrew Raibeck
The next 5.3 client fix pack (formerly known as "PTF") is currently
targeted for some time in October, and this level will include Mac (OS X
10.3.9+ or 10.4).

When available, you will be able to find it in the usual place on the
ftp.software.ibm.com site, or from the TSM Support page (see my sig).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 2005-09-30
14:25:48:

> When is TSM v5.3 going to be available for the Macintosh client?  And
> where should I look for it.
>
> Thanks much
>
> Dean Winger
> Network Engineer
> University of Wisconsin Madison
> 1025 West Johnson St
> Madison, WI 53717
> Office (608)265-3202


Re: TSM 5.2 Installation Guide

2005-09-30 Thread Julius Martinez
Hi Aaron - the TSM 5.2 (or earlier) publications can be directly accessed
here:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

(Jump down to the "S" section to find the TSM products)

There's also a searchable Information Center here:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp

Note that before version 5.3, the Installation Guides were called Quick
Starts.


- Message from Aaron Becar <[EMAIL PROTECTED]> on Thu, 29 Sep 2005
11:12:24 -1000 -
Subject:
Re: TSM 5.2 Installation Guide
Just a quick question.

I have the 5.3 Install guide, but I cannot find the 5.2 Install guide.
Does anyone have the link?  Thanks!

Aaron

Julius Martinez
IBM Software Group, Tivoli Storage
(520) 799-5472 (tie line 321-5472)
Tucson, Arizona


Re: Invalid verb received causing rc=12

2005-09-30 Thread Levi, Ralph
Thanks.  I have opened a problem with the support center.  Will let you
know what the result is.  IC40841 doesn't seem to really fit this
problem once you look "under the hood".

Ralph 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Stapleton, Mark
Sent: Thursday, September 29, 2005 4:34 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Invalid verb received causing rc=12

Please, please consult the IBM site when seeking answers.

Here's what you get when go to www.ibm.com and search for
"cuGetBackQryResp: Unknown objInfo header":

http://www-1.ibm.com/support/docview.wss?uid=swg1IC40841

It refers to a different level of TSM, but I suspect the problem is much
the same.

--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
 Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Berbee Information Networks
Office 262.521.5627

 

>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
>Behalf Of Levi, Ralph
>Sent: Thursday, September 29, 2005 1:47 PM
>To: ADSM-L@VM.MARIST.EDU
>Subject: Re: Invalid verb received causing rc=12
>
>I just upgraded the client to 5.3.015 and got the same error but with
>this additional info:
>
>ERROR: hl is empty in ExtractSlashHack!
>cuGetBackQryResp: Unknown objInfo header format:2,,FID1
>
>BTW. the client is Windows2003 (not w2k as I was originally told).
>> _ 
>> From:Levi, Ralph  
>> Sent:Thursday, September 29, 2005 10:10 AM
>> To:  'ADSM: Dist Stor Manager'
>> Subject: Invalid verb received  causing rc=12 
>> 
>> Does anyone have an idea what could be causing this error.  I don't
>> see anywhere what the object is that could be causing this problem or
>> and indication of some other issue on the system.
>> 
>> Client - w2k running 5.1.7 
>> Server - AIX 5.2 running 5.2.6 TSM
>> 
>> 
>> 09/29/2005 00:39:33 sessRecvVerb(): Invalid verb received.
>> 09/29/2005 00:39:33 sessRecvVerb(): length=0001, verb=00,magic=00
>> 09/29/2005 00:39:34 ANS1026E Session rejected: 
>Communications protocol
>> error
>> 
>> Thanks,
>> Ralph
>


TSM Mac Client 5.3

2005-09-30 Thread Dean Winger

When is TSM v5.3 going to be available for the Macintosh client?  And
where should I look for it.

Thanks much

Dean Winger
Network Engineer
University of Wisconsin Madison
1025 West Johnson St
Madison, WI 53717
Office (608)265-3202


Re: Backup error ----Email OK.

2005-09-30 Thread Gianluca Mariani1
You probably need to run a Cleanup Backupgroups process.


Cordiali saluti
Gianluca Mariani
Tivoli TSM Global Response Team, Roma
Via Sciangai 53, Roma
 phones : +39(0)659664598
   +393351270554 (mobile)
[EMAIL PROTECTED]

Resembles Life what once was held of Light,
Too ample in itself for human sight ?

An absolute Self--an element ungrounded--
All, that we see, all colours of all shade

By encroach of darkness made ?--

Is very life by consciousness unbounded ?
And all the thoughts, pains, joys of mortal breath,
A war-embrace of wrestling Life and Death ?



Fernando Bozza <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
30/09/2005 09:04
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Backup error Email  OK.






Hi,

I'm having some problems during the backup of windows servers. I've
received the follwing message in the error logs.

09/30/2005 00:07:41 ANS1228E Sending of object
'\\xxx\c$\WINDOWS\system32\zipfldr.dll' failed
09/30/2005 00:07:41 ANS0343E An invalid operation was attempted on a group
leader or group member.
09/30/2005 00:07:41 ANS1228E Sending of object '\\xxx\c$\WINDOWS\WinSxS'
failed
09/30/2005 00:07:41 ANS0343E An invalid operation was attempted on a group
leader or group member.
09/30/2005 00:07:41 ANS1228E Sending of object
'\\xxx\c$\WINDOWS\WinSxS\InstallTemp' failed
09/30/2005 00:07:41 ANS0343E An invalid operation was attempted on a group
leader or group member.

Has anyone seen this problem before? This happened during the backup of
systemstate. I tried to look on the ibm page, but I didn't find anything
that could help me really.

PS. TSM client 5.2.4.4 and TSM server 5.2.4.4.

Thanks,

Fernando


Re: [SPAM: 4.100] [ADSM-L] Locale on Unix

2005-09-30 Thread Loon, E.J. van - SPLXM
Hi Leigh!
LANG=
So it's set to nothing.

Richard, thanks for pointing me to the right IBM doc!
Rainer, thank you very much for your suggestion. I will forward them to the 
Linux administrator.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Leigh Reed [mailto:[EMAIL PROTECTED]
Sent: Friday, September 30, 2005 13:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [SPAM: 4.100] [ADSM-L] Locale on Unix


Eric

What LANG do you have set in your environment variables ?

Leigh

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. 
van - SPLXM
Sent: 30 September 2005 12:23
To: ADSM-L@VM.MARIST.EDU
Subject: [SPAM: 4.100] [ADSM-L] Locale on Unix

Hi *SMers!
On our 5.2.4.0 Linux client, files with special characters are not backed up. 
TSM logs the following error in the dsmerror.log:

09.05.2005 02:02:00 fioScanDirEntry(): Object 
'/usr/share/sane/descripth¤xÃ-extrnal' contains unrecognized symbols for 
current locale, skipping...

It does so for all files with special characters.
Does anybody know how to solve this?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**


Backup error ----Email OK.

2005-09-30 Thread Fernando Bozza
Hi,

I'm having some problems during the backup of windows servers. I've
received the follwing message in the error logs.

09/30/2005 00:07:41 ANS1228E Sending of object
'\\xxx\c$\WINDOWS\system32\zipfldr.dll' failed
09/30/2005 00:07:41 ANS0343E An invalid operation was attempted on a group
leader or group member.
09/30/2005 00:07:41 ANS1228E Sending of object '\\xxx\c$\WINDOWS\WinSxS'
failed
09/30/2005 00:07:41 ANS0343E An invalid operation was attempted on a group
leader or group member.
09/30/2005 00:07:41 ANS1228E Sending of object
'\\xxx\c$\WINDOWS\WinSxS\InstallTemp' failed
09/30/2005 00:07:41 ANS0343E An invalid operation was attempted on a group
leader or group member.

Has anyone seen this problem before? This happened during the backup of
systemstate. I tried to look on the ibm page, but I didn't find anything
that could help me really.

PS. TSM client 5.2.4.4 and TSM server 5.2.4.4.

Thanks,

Fernando


Re: busy rootvg during restarts

2005-09-30 Thread David McClelland

Michael,

I'd think about checking/tuning the
size of your BUFPOOL in TSM; make sure that it isn't so large that it's
requesting lots of RAM which in turn is hitting into your paging space...
As the other guys have said, double check with the AIX perf tools such
as topas and check where your paging space is (lsps -a) etc. 

HTH,



David McClelland

Storage and Systems Management Specialist 
IBM Tivoli Certified Deployment Professional (ITSM 5.2) 
SSO UK Service Delivery – Storage Services 
IBM Global Services – IBM United Kingdom 








"Wheelock, Michael
D" <[EMAIL PROTECTED]> 
Sent by: "ADSM: Dist Stor Manager"

29/09/2005 16:23



Please respond to
"ADSM: Dist Stor Manager"





To
ADSM-L@VM.MARIST.EDU


cc



Subject
[ADSM-L] busy rootvg during
restarts








Hi,

 

Every time I halt and restart my tsm server, the rootvg disk becomes
extraordinarily busy.  I have moved all of the database, and logs
to
another location.  The only file that I know of that is still on rootvg
(besides the normal binaries and config files) is the volhist file.
Does TSM hammer that volhist file on startup?

 

Michael Wheelock

Integris Health

**
This e-mail may contain identifiable health information that is subject
to protection under state and federal law. This information is intended
to be for the use of the individual named above. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
the contents of this information is prohibited and may be punishable by
law. If you have received this electronic transmission in error, please
notify us immediately by electronic mail (reply).



Re: Locale on Unix

2005-09-30 Thread Rainer Schöpf
On Fri, 30 Sep 2005, Loon, E.J. van - SPLXM wrote:

 > Hi *SMers! On our 5.2.4.0 Linux client, files with special characters 
 > are not backed up. TSM logs the following error in the dsmerror.log:
 > 
 > 09.05.2005 02:02:00 fioScanDirEntry(): Object 
 > '/usr/share/sane/descripth¤xÃ-extrnal' contains unrecognized symbols for 
 > current locale, skipping...
 > 
 > It does so for all files with special characters.
 > Does anybody know how to solve this?

Solve, no. Get around, yes.

TSM checks characters in filenames against the current locale. The 
filename quoted looks like UTF-8 to me, so you should set the locale to 
UTF-8 before starting the client.

For example, my startup script for the TSM scheduler contains:

[EMAIL PROTECTED] ; export LC_CTYPE

In your case 

LC_CTYPE=en_US.utf8 ; export LC_CTYPE

might be appropriate, but make sure that this locale is known. "locale -a" 
lists all known locales.

A word of warning: if you have filenames containing characters from 
different locales, you will have a problem anyway. Which is why I find 
this particular TSM design, well, questionable. A Unix filename can 
contain (nearly) every of the 256 possible one byte characters. A backup 
system should accept all of them. In my opinion, the locale is for the 
user interaction, not for system internals.

On the other hand, I think I understand why the TSM client behaves this 
way. The whole locale concept breaks down when you assign meaning to 
filenames, simply because a file called "äöü" in iso-8859-1 will seem to 
have a different name if looked at with locale set to iso-8859-2.

 Regards,
   Rainer Schöpf


Re: [SPAM: 4.100] [ADSM-L] Locale on Unix

2005-09-30 Thread Leigh Reed
Eric

What LANG do you have set in your environment variables ?

Leigh

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. 
van - SPLXM
Sent: 30 September 2005 12:23
To: ADSM-L@VM.MARIST.EDU
Subject: [SPAM: 4.100] [ADSM-L] Locale on Unix

Hi *SMers!
On our 5.2.4.0 Linux client, files with special characters are not backed up. 
TSM logs the following error in the dsmerror.log:

09.05.2005 02:02:00 fioScanDirEntry(): Object 
'/usr/share/sane/descripth¤xÃ-extrnal' contains unrecognized symbols for 
current locale, skipping...

It does so for all files with special characters.
Does anybody know how to solve this?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**


Locale on Unix

2005-09-30 Thread Loon, E.J. van - SPLXM
Hi *SMers!
On our 5.2.4.0 Linux client, files with special characters are not backed up. 
TSM logs the following error in the dsmerror.log:

09.05.2005 02:02:00 fioScanDirEntry(): Object 
'/usr/share/sane/descripth¤xÃ-extrnal' contains unrecognized symbols for 
current locale, skipping...

It does so for all files with special characters.
Does anybody know how to solve this?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**


Re: TSM 5.2 Installation Guide

2005-09-30 Thread Loon, E.J. van - SPLXM
Hi Aaron!
Assuming you are using an AIX server, you can find the server docs here:
http://publib.boulder.ibm.com/tividd/td/IBMStorageManagerforAIX5.2.html
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: Aaron Becar [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005 23:12
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.2 Installation Guide


Just a quick question.

I have the 5.3 Install guide, but I cannot find the 5.2 Install guide.
Does anyone have the link?  Thanks!

Aaron


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**