Re: icon disappeared from upgrading to TSM 5.2.0.3

[Darby, Mark]

Eliza,

If the CAD has not been configured (via dsmcutil or wizard) and started on
the machine in question, then there's no TSM client service to "do" the
listening - and the GUI B/A client does not listen, either.

You can verify with netstat, like Ted said.

The CAD service, when installed via the wizard or dsmcutil is the one that
listens - but only if MANAGEDSERVICES WEBCLIENT is specified in the
associated dsm.opt file.  The wizard does put that statement in the dsm.opt,
by the way, which is why I suggested that you remove it (unless web-based
client access to the machine is desired).

Regards,
Mark

-Original Message-
From: Eliza Lau
To: [EMAIL PROTECTED]
Sent: 10/10/2003 5:39 PM
Subject: Re: icon disappeared from upgrading to TSM 5.2.0.3

Ted,

I just checked my W2k box and 1581 is not listening.  I am running the
5.2.0.3
client.

Eliza

>
> >Is it true that if he doesn't configure the
> >web client or install CAD then port 1581 is not open?
> >Security is on everyone's mind these days.
>
> Hi Eliza,
>
> Does port 1581 show up in netstat -a output like below?  Have you
tried
> connecting to the user's machine with the a web browser pointed at
port
> 1581?  Unless the client configuration has changed to run the client
> acceptor service in webclient mode, I don't think that the user is
exposed.
>
> C:\usr\bin>netstat -a |find /i ":1581"
>TCPsvr0100:1581  svr0100.tsm.customer.com:0  LISTENING
>
>
> Ted Byrne
>

Re: Backup definition

[Steven Pemberton]

On Saturday 11 October 2003 04:15, Helen Tam wrote:
> Hello,
> I'm not clear on creating 2 nodes or 2 client accounts.  Is this for
> the same machine?  How do you define this?  I have a similar situation.  I
> need to backup all files daily and a certain database only on
> weekend.   Please advise.Thanks, Helen Tam

The "dual node" trick is only necessary when you want to retain *backups* of
*the same* data for differing periods.

Normally this is a problem because the obvious (incorrect) solution, of simply
changing management classes for the "special" backup, will cause the entire
history of backup data to rebind to whichever management class is used last,
and rebind back to the "normal" management class on the next "normal" backup.

It doesn't sound appropriate in your example. Why not just use a daily
incremental backup for all files, and exclude the database files. Then use a
separate "archive" schedule, which ignores the backup exclusion, to archive
the database files on the weekend.

Of course, then you will need to coordinate the shutdown of your database with
the archive command, to ensure the database is in a consistent state for
archival (Do not try to do this with "open file" support). Consider running
the "archive" schedule as a command script. The script could then stop,
archive, and restart, the database.

And if you're using a TDP for your database backups, that's a different
story...

Regards,
Steven P.

--
Steven Pemberton
Senior Enterprise Management Consultant
IBK, Senetas Group

Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907
Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia
http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au

Re: icon disappeared from upgrading to TSM 5.2.0.3

[Eliza Lau]

Ted,

I just checked my W2k box and 1581 is not listening.  I am running the 5.2.0.3
client.

Eliza

>
> >Is it true that if he doesn't configure the
> >web client or install CAD then port 1581 is not open?
> >Security is on everyone's mind these days.
>
> Hi Eliza,
>
> Does port 1581 show up in netstat -a output like below?  Have you tried
> connecting to the user's machine with the a web browser pointed at port
> 1581?  Unless the client configuration has changed to run the client
> acceptor service in webclient mode, I don't think that the user is exposed.
>
> C:\usr\bin>netstat -a |find /i ":1581"
>TCPsvr0100:1581  svr0100.tsm.customer.com:0  LISTENING
>
>
> Ted Byrne
>

Re: icon disappeared from upgrading to TSM 5.2.0.3

[Ted Byrne]

Is it true that if he doesn't configure the
web client or install CAD then port 1581 is not open?
Security is on everyone's mind these days.
Hi Eliza,

Does port 1581 show up in netstat -a output like below?  Have you tried
connecting to the user's machine with the a web browser pointed at port
1581?  Unless the client configuration has changed to run the client
acceptor service in webclient mode, I don't think that the user is exposed.
C:\usr\bin>netstat -a |find /i ":1581"
  TCPsvr0100:1581  svr0100.tsm.customer.com:0  LISTENING
Ted Byrne

Re: icon disappeared from upgrading to TSM 5.2.0.3

[Eliza Lau]

Mark,

So is this icon disappearing act a new feature of 5.2 or a bug?  It is not
mentioned in the README.

The user is not using the CAD service to manage the Scheduler. He uses the
Windows scheduler service.  Is it true that if he doesn't configure the
web client or install CAD then port 1581 is not open?
Security is on everyone's mind these days.

I tried to uninstall the Web client but there is no way to do it.
Is this another new feature of 5.2?

Eliza

>
> Hello, Eliza.
>
> Yes, I have also seen this behavior (with the 5.2.0.1 client).
>
> Regarding the Client Acceptor Daemon (CAD) listening on port 1581, after
> running the wizard, I change the MANAGEDSERVICES statement in dsm.opt from
> "WEBCLIENT SCHEDULE" to simply "SCHEDULE" (because, of course, I use the CAD
> service to manage the Scheduler service).  The last time I checked, this
> prevents the CAD from listening on that port.
>
> In addition, by the way, if you "simply install" the LVSA/OFS client code
> (like I have done, intending to use it later - perhaps), you must also
> actually use it (i.e., properly configure and start the LVSA service),
> otherwise the client will emit messages like the following:
>
> ANS1228E Sending of object '\\host\x$' failed
> ANS1377E Unable to perform operation using a point-in-time copy of the
> filesystem on '\\host\x$'. The backup/archive operation will continue
> without snapshot support.
>
> ...not that the last item has any bearing whatsoever on your question, but I
> thought it might be of interest to you.
>
> Regards,
> Mark
>
> -Original Message-
> From: Eliza Lau
> To: [EMAIL PROTECTED]
> Sent: 10/10/2003 4:14 PM
> Subject: icon disappeared from upgrading to TSM 5.2.0.3
>
> Hi TSMers,
>
>  I upgraded the client on my W2K box from 5.1.6.2 to 32bit 5.2.0.3.  The
> icon
>  disappeared from the desktop and wasn't recreated after the upgrade.
> As a
>  test, I removed the client and did a new install.  The icon wasn't
> created.
>  I have to manually make a copy of dsm.exe and moved it to the desktop.
>  Has anyone seen this?
>
>  Also, in the 5.2 W2K client install the option to NOT install the web
> client
>  and the API client is no longer available.  They are always installed.
> A
>  user is concerned that the web client opens up port 1581 on his Windows
>  server even thought he doesn't want to use the web client.
>
>  server: TSM 5.1.1.6 on AIX 5.1
>  client: TSM 5.2.0.3 on W2K SP4
>
>  Eliza Lau
>  Virginia Tech Computing Center
>  1700 Pratt Drive
>  Blacksburg, VA 24060
>  [EMAIL PROTECTED]
>

Re: icon disappeared from upgrading to TSM 5.2.0.3

[Darby, Mark]

Hello, Eliza.

Yes, I have also seen this behavior (with the 5.2.0.1 client).

Regarding the Client Acceptor Daemon (CAD) listening on port 1581, after
running the wizard, I change the MANAGEDSERVICES statement in dsm.opt from
"WEBCLIENT SCHEDULE" to simply "SCHEDULE" (because, of course, I use the CAD
service to manage the Scheduler service).  The last time I checked, this
prevents the CAD from listening on that port.

In addition, by the way, if you "simply install" the LVSA/OFS client code
(like I have done, intending to use it later - perhaps), you must also
actually use it (i.e., properly configure and start the LVSA service),
otherwise the client will emit messages like the following:

ANS1228E Sending of object '\\host\x$' failed
ANS1377E Unable to perform operation using a point-in-time copy of the
filesystem on '\\host\x$'. The backup/archive operation will continue
without snapshot support.

...not that the last item has any bearing whatsoever on your question, but I
thought it might be of interest to you.

Regards,
Mark

-Original Message-
From: Eliza Lau
To: [EMAIL PROTECTED]
Sent: 10/10/2003 4:14 PM
Subject: icon disappeared from upgrading to TSM 5.2.0.3

Hi TSMers,

 I upgraded the client on my W2K box from 5.1.6.2 to 32bit 5.2.0.3.  The
icon
 disappeared from the desktop and wasn't recreated after the upgrade.
As a
 test, I removed the client and did a new install.  The icon wasn't
created.
 I have to manually make a copy of dsm.exe and moved it to the desktop.
 Has anyone seen this?

 Also, in the 5.2 W2K client install the option to NOT install the web
client
 and the API client is no longer available.  They are always installed.
A
 user is concerned that the web client opens up port 1581 on his Windows
 server even thought he doesn't want to use the web client.

 server: TSM 5.1.1.6 on AIX 5.1
 client: TSM 5.2.0.3 on W2K SP4

 Eliza Lau
 Virginia Tech Computing Center
 1700 Pratt Drive
 Blacksburg, VA 24060
 [EMAIL PROTECTED]

icon disappeared from upgrading to TSM 5.2.0.3

[Eliza Lau]

Hi TSMers,

 I upgraded the client on my W2K box from 5.1.6.2 to 32bit 5.2.0.3.  The icon
 disappeared from the desktop and wasn't recreated after the upgrade.  As a
 test, I removed the client and did a new install.  The icon wasn't created.
 I have to manually make a copy of dsm.exe and moved it to the desktop.
 Has anyone seen this?

 Also, in the 5.2 W2K client install the option to NOT install the web client
 and the API client is no longer available.  They are always installed.  A
 user is concerned that the web client opens up port 1581 on his Windows
 server even thought he doesn't want to use the web client.

 server: TSM 5.1.1.6 on AIX 5.1
 client: TSM 5.2.0.3 on W2K SP4

 Eliza Lau
 Virginia Tech Computing Center
 1700 Pratt Drive
 Blacksburg, VA 24060
 [EMAIL PROTECTED]

Re: Checkin libvol

[Marcel J.E. Mol]

On Fri, Oct 10, 2003 at 07:35:43AM -0500, Stapleton, Mark wrote:
> From: Christian Svensson [mailto:[EMAIL PROTECTED]
> >Search=yes is not picking up the media from the Service port.
> I need to use Search=bulk.
> And and it??s still does??nt work.<
>
> If you're loading tapes into the I/O station, you'll have to run the request/reply 
> process to check them. The search=yes parameter is only used when you put tapes into 
> the library manually.

I noticed that too. But isn't entering tapes in empty slots a bit dangerous?
If tsm has loaded a tape from say slot 100 in a drive and you put a new tape
in slot 100 what will happen if tsm wants to return the tape from the drive to
its original slot?

I'm using a script to checkin tapes one by one from the ioslots (3584)
explicitely specifying the volumelabel. TSM then requests me to put
the tape in the upper slot for every tape. I wish that it would support
search=bulk so it scans the ioports for the specific volume...

-Marcel
--
 == Marcel J.E. MolMESA Consulting B.V.
===-ph. +31-(0)6-54724868  P.O. Box 112
===-[EMAIL PROTECTED] 2630 AC  Nootdorp
__ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands 
 They couldn't think of a number,   Linux user 1148  --  counter.li.org
so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com

Re: DRM under Linux

[Patrick Boutilier]

For now. From the README:



2) Features not supported on this release

- DRM
- Generic Tape
- Shared Memory Protocol


Thomas Denier wrote:
We are looking into the possibility of migrating our OS/390 TSM
server to mainframe Linux. I just looked at the "Administrator's
Reference" to find out whether a 'move drmedia' command under Linux
would eject tapes from our library. I was surprised to find 'move
drmedia' absent from the list of administrator commands. Further
checking revealed that 'prepare', the various 'insert' commandss,
and the queries related to DRM were also absent. Did IBM really
decide to omit DRM from the Linux server implementation?

DRM under Linux

[Thomas Denier]

We are looking into the possibility of migrating our OS/390 TSM
server to mainframe Linux. I just looked at the "Administrator's
Reference" to find out whether a 'move drmedia' command under Linux
would eject tapes from our library. I was surprised to find 'move
drmedia' absent from the list of administrator commands. Further
checking revealed that 'prepare', the various 'insert' commandss,
and the queries related to DRM were also absent. Did IBM really
decide to omit DRM from the Linux server implementation?

Re: ADSM with Windows 2003 Server and SFU 3.5

[Remco Post]

Now, this is about the first response that makes sense.

On Friday, Oct 10, 2003, at 20:26 Europe/Amsterdam, Andrew Raibeck 
wrote:

True, TSM (like many other Win32 applications) does not support
case-sensitive file names.
It isn't that we are willing to admit that such files exist; of course
they exist. Nor is that we are "unwilling" to back up files supported 
by
NTFS.

TSM, like any other application, relies on operating system API 
functions
to operate on OS-specific elements (such as NTFS file systems and the
files that reside thereon). NTFS supports the existence of 
case-sensitive
file names, but there are limitations to the degree of support 
afforded by
the OS API functions. Some of the issues involved:

- TSM needs to manage case-sensitive file names is differently than
case-insensitive names (hopefully that is obvious). For non-Unix file
names, NTFS is case-preserving, but case-insensitive. Thus 'README.TXT'
and 'readme.txt' are the same file. TSM must operate on this file so 
that
if the name changes from 'README.TXT' to 'readme.txt' between backup
versions, TSM treats it as the same file. For case-sensitive file 
names,
TSM must treat 'README.TXT' and 'readme.txt' as different files.

What you are saying is that because Windows allows applications to 
behave case-insensitive (basically, like any 20 year old dos app) TSM 
must treat readme.txt as the same file as README.TXT, just because 
there are loads of applications that still behave that way, and 
basically if you open a file giving the wrong case but the right name, 
windows co-operates.

- Most Win32 applications are not case-sensitive with regard to file 
names
(as noted below, there are some Windows API functions that support
case-sensitive file names). Windows also provides a POSIX subsystem 
that
allows POSIX applications to create case-sensitive names.

- Case-sensitive file names can coexist on the same volume with
case-insensitive names. This means that at the NTFS volume level, an
application can not make any blanket assumptions about the
case-sensitivity of all files on the volume.
True. TSM probably (I never checked) restores case as it was backed-up.


-  There is nothing in a file's attributes to indicate the case
sensitivity. Therefore an application can not make any assumptions 
about
the case-sensitivity of a given file.

- While some Windows file I/O functions support case-sensitive file 
names,
others do not. For example, CreateFile(), which is used to open files, 
has
support for case-sensitive file names; on the other hand,
GetFileAttributes() (used to obtain a file's attributes) and
GetFileSecurity() (used to obtain a file's security attributes) do not
support case-sensitive file names. Thus if you have files 'readme.txt' 
and
'README.TXT', we would not be able to obtain file attribute and 
security
information for both files.

which is a major shortcoming of windows, or the particular API TSM 
uses. I guess you are right in saying that this is out of IBMs scope to 
fix.

- Since, as stated above, TSM needs to manage case-sensitive file names
differently than case-insensitive file names, TSM *must* be able to
distinguish case-sensitive names from case-insensitive names. Since 
NTFS
allows the existence of *both*, but provides no functionality to
distinguish them, it is not possible for TSM to distinguish them, 
either.

This only makes sense if the case of a filename is not preserved during 
use. I agree that, with TSMs retention policies, we do want to be able 
to match different versions of one file as close to the useres 
perception as possible. Since the application changes the case in the 
name at more or less random occasion, TSM must indeed not distinguish.

In sum, while NTFS may allow case-sensitive file names to exist, the
Windows operating system itself does not provide the functionality
necessary to fully support these files. In fact, you will find that 
TSM is
not the only application to have difficulty with case-sensitive files. 
For
example, some basic OS functions like DIR or basic applications like
NOTEPAD.EXE do not handle case-sensitive file names, either. Using some
case-sensitive names I generated, the following is output from a sample
session that demonstrates some odd behavior (note that "posix.exe" is a
tool I created to generate case-sensitive file names):

Basically, what you are saying is that, if TSM had the API to properly 
back-up sace-sensitive, you might not want to do so because most 
windows applications are case-insensitive. So basically this boils down 
to a big dilemma, do we want to treat a change in the filename the 
windows way or the unix way? Unfortunately for the few of us unlucky 
enough to suffer sfu, that is about the only case where the unix way is 
better

Now if TSM was like other back-up solutions, and we didn't distinguish 
between old versions of changed files or deleted files, ther would not 
be a problem (apart from the fact that windows sucks...)


==

Re: Backup definition

[Helen Tam]

Hello,
   I'm not clear on creating 2 nodes or 2 client accounts.  Is this for
the same machine?  How do you define this?  I have a similar situation.  I
need to backup all files daily and a certain database only on
weekend.   Please advise.Thanks, Helen Tam
At 04:09 PM 10/11/2003 +1000, you wrote:
On Thursday 09 October 2003 22:13, Bernd Schemmer wrote:
> I want to implement the following backup definitions:
>
> Create a fullbackup every 1st day of each month
> Create an incremental backup every further day of the month
>
> The fullbackup should be stored for 12 month; the incremental backups
> only until the next fullbackup is done.
>
> The fullbackups and incremental backups should go to the same storage pool.
>
> How do I do this?
Before you do this you should ask yourself (or your users) exactly _why_ you
are doing it, and is it necessary for every node, or is it really necessary
at all?
The best answer is probably to educate your users as to how TSM works, and to
design a normal TSM policy that will achieve the data retention they need,
without requiring unnecessary full backups. But, assuming they do have this
need, there are several options:
If you need to retain the monthly "full" backups for an extended period, for
regulatory reasons, or just because "it sounded like a good idea" - but don't
really expect to ever access them (or only access them rarely), then consider
generating a backup set rather than performing a "real" full backup.
Backup sets are great (though slow to produce) as they don't require the
client to resend a full backup. However, it can be costly in tape (and time)
to produce backup sets for a large number of clients. Media management of
backup sets is also a little harder than for storage pool volumes.
Otherwise, if you need regular and quick access to these "long term backups",
consider instead performing a monthly "archive" instead of a backup - but
realise this will add *significantly* to your TSM database size over time.
Also remeber that "archives" usually treat symbolic links differently than
"backups".
Personally I favour creating two client accounts, to separate my "normal" (35
day retention) from my "long term" (365 day retention) backups. Then create
two schedules, and perform *incremental* backups on both nodes, on the
appropriate day/s of the month - sending each node's backup data to a
separate management class with the appropriate retention periods (which could
then go to the same stgpool if desired).
Eg. "nodename" -> mc35 -> diskpool1 -> tapepool1
and
  "nodename_ltb" -> mc365 -> diskpool1 -> tapepool1
On the first day of each month the LTB node will perform an incremental
backup, relative to last month's long term backup. This reduces the "long
term" backup from a "full" to an "incremental", and will result in a much
smaller TSM database relative to monthly archives.
While on every day (or every other, if you wish) of the month, the "normal"
node will perform it's regular incremental backup, releative to yesterday's
backup.
Other questions you should ask your users are:
- Does the entire filesystem need to be retained for such a long period, or
just certain critical files/directories?
- Have you considered the need to keep monthly TDP backups for an extended
period (Eg. MS-Exchange).
- Is the data's native format suitable for "archival", consider exporting data
to CSV or XML format prior to archiving (more important for multi-year
archival).
Regards,
Steven P.
--
Steven Pemberton
Senior Enterprise Management Consultant
IBK, Senetas Group
Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907
Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia
http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au

Re: Administrative tools for Unix or Linux servers

[Michael, Monte]

We are using Tivoli Workload Scheduler to submit all of our TSM backup jobs, and to 
schedule the daily TSM administrative tasks.

...Monte

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
David E Ehresman
Sent: Friday, October 10, 2003 8:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Administrative tools for Unix or Linux servers


>How are people handling the kinds of scheduling and
>monitoring functions described above on other platforms with similar
>tools available, such as Intel Linux or various Unix implementations?

By writing scripts.  The two biggest hurdles to overcome when moving
from a MVS TSM to a Unix TSM is tape monitoring/vaulting and admin
scheduling/monitoring.

David


This communication is for use by the intended recipient and contains
information that may be privileged, confidential or copyrighted under
applicable law.  If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited.  Please notify the sender
by return e-mail and delete this e-mail from your system.  Unless
explicitly and conspicuously designated as "E-Contract Intended",
this e-mail does not constitute a contract offer, a contract amendment,
or an acceptance of a contract offer.  This e-mail does not constitute
a consent to the use of sender's contact information for direct marketing
purposes or for transfers of data to third parties.

 Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean

http://www.DuPont.com/corp/email_disclaimer.html

Re: ADSM with Windows 2003 Server and SFU 3.5

[Andrew Raibeck]

True, TSM (like many other Win32 applications) does not support 
case-sensitive file names.

It isn't that we are willing to admit that such files exist; of course 
they exist. Nor is that we are "unwilling" to back up files supported by 
NTFS.

TSM, like any other application, relies on operating system API functions 
to operate on OS-specific elements (such as NTFS file systems and the 
files that reside thereon). NTFS supports the existence of case-sensitive 
file names, but there are limitations to the degree of support afforded by 
the OS API functions. Some of the issues involved:

- TSM needs to manage case-sensitive file names is differently than 
case-insensitive names (hopefully that is obvious). For non-Unix file 
names, NTFS is case-preserving, but case-insensitive. Thus 'README.TXT' 
and 'readme.txt' are the same file. TSM must operate on this file so that 
if the name changes from 'README.TXT' to 'readme.txt' between backup 
versions, TSM treats it as the same file. For case-sensitive file names, 
TSM must treat 'README.TXT' and 'readme.txt' as different files.

- Most Win32 applications are not case-sensitive with regard to file names 
(as noted below, there are some Windows API functions that support 
case-sensitive file names). Windows also provides a POSIX subsystem that 
allows POSIX applications to create case-sensitive names.

- Case-sensitive file names can coexist on the same volume with 
case-insensitive names. This means that at the NTFS volume level, an 
application can not make any blanket assumptions about the 
case-sensitivity of all files on the volume.

-  There is nothing in a file's attributes to indicate the case 
sensitivity. Therefore an application can not make any assumptions about 
the case-sensitivity of a given file.

- While some Windows file I/O functions support case-sensitive file names, 
others do not. For example, CreateFile(), which is used to open files, has 
support for case-sensitive file names; on the other hand, 
GetFileAttributes() (used to obtain a file's attributes) and 
GetFileSecurity() (used to obtain a file's security attributes) do not 
support case-sensitive file names. Thus if you have files 'readme.txt' and 
'README.TXT', we would not be able to obtain file attribute and security 
information for both files.

- Since, as stated above, TSM needs to manage case-sensitive file names 
differently than case-insensitive file names, TSM *must* be able to 
distinguish case-sensitive names from case-insensitive names. Since NTFS 
allows the existence of *both*, but provides no functionality to 
distinguish them, it is not possible for TSM to distinguish them, either.

In sum, while NTFS may allow case-sensitive file names to exist, the 
Windows operating system itself does not provide the functionality 
necessary to fully support these files. In fact, you will find that TSM is 
not the only application to have difficulty with case-sensitive files. For 
example, some basic OS functions like DIR or basic applications like 
NOTEPAD.EXE do not handle case-sensitive file names, either. Using some 
case-sensitive names I generated, the following is output from a sample 
session that demonstrates some odd behavior (note that "posix.exe" is a 
tool I created to generate case-sensitive file names):

==
C:\POSIX>posix README.TXT ReadMe.txt readme.txt

C:\POSIX>dir
 Volume in drive C is Local Disk
 Volume Serial Number is B022-6D5D

 Directory of C:\POSIX

10/10/2003  10:47 .
10/10/2003  10:47 ..
10/10/2003  10:470 README.TXT
10/10/2003  10:470 ReadMe.txt
10/10/2003  10:470 readme.txt
   3 File(s)  0 bytes
   2 Dir(s)   3,427,893,248 bytes free

C:\POSIX>echo Upper case name > README.TXT

C:\POSIX>echo Lower case name > readme.txt

C:\POSIX>echo Mixed case name > ReadMe.txt

C:\POSIX>dir
 Volume in drive C is Local Disk
 Volume Serial Number is B022-6D5D

 Directory of C:\POSIX

10/10/2003  10:47 .
10/10/2003  10:47 ..
10/10/2003  10:47   18 README.TXT
10/10/2003  10:470 ReadMe.txt
10/10/2003  10:470 readme.txt
   3 File(s) 18 bytes
   2 Dir(s)   3,427,893,248 bytes free

C:\POSIX>type README.TXT
Mixed case name
Mixed case name
Mixed case name

C:\POSIX>type "README.TXT"
Mixed case name
Mixed case name
Mixed case name

C:\POSIX>type "ReadMe.txt"
Mixed case name
Mixed case name
Mixed case name

C:\POSIX>del "readme.txt"

C:\POSIX>dir
 Volume in drive C is Local Disk
 Volume Serial Number is B022-6D5D

 Directory of C:\POSIX

10/10/2003  10:48 .
10/10/2003  10:48 ..
   0 File(s)  0 bytes
   2 Dir(s)   3,427,893,248 bytes free

C:\POSIX>
==

With all of that

Re: Checkin libvol

[Mike Cantrell]

Hello
I used the following ksh script
for volser in $(libtapeck|grep FF00 |awk '{print $1}')
do
dsmck checkin libv sakslib02 $volser status=scratch devtype=3590
checklabel=no
done
Note libtapeck is a script  "mtlib -l /dev/lmcp0 -q I" and FF00 is inset
status.

This gets any volumes that are in insert status.

Mike

-Original Message-
From: Bill Boyer [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 10:14 AM
To: [EMAIL PROTECTED]
Subject: Re: Checkin libvol


The PERL script was more portable than an shell script. We do TSM
implementations on both Unix and Windows platforms. Yes, I work with Ted
Byrne. The Perl script can be used on any platform with Perl and the TSM
admin client loaded.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Wilcox, Andy
Sent: Friday, October 10, 2003 8:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Checkin libvol


Hiya Ted,

Just out of complete curiosity, why would you want to run such a script from
somewhere other than on the server itself??? We do something pretty much the
same except the scipt runs from AIX on our TSM server...

Cheers

Andy Wilcox
Midrange Services
Aquila Networks Services Ltd


> -Original Message-
> From: Ted Byrne [SMTP:[EMAIL PROTECTED]
> Sent: 10 October 2003 13:57
> To:   [EMAIL PROTECTED]
> Subject:  Re: Checkin libvol
>
> > >Hi everyone!
> > >Everytime I try to checkin my tapes to my library I need to run q
> > request and reply 
> > >Is it possible to checkin tape without to run a reply ?
>
> Checking in the tapes through an I/O station (search=bulk) does
> require that a reply be issued to a request.  However, for many of our
> customers, it is not practical to have the operator who  is actually
> handling tapes running a checkin manually after the Entry/Exit port is
> loaded with the day's tapes (almost always less than the capacity of
> the entry/exit port).
>
> For this situation, we have written a small perl script that gets
> scheduled once a day,  typically at the end of each weekday.  It's
> defined as a client event to run on a machine with the administrative
> client installed.  The script runs, issues the checkin libv command,
> issues the "q
> request", parses the output to get the request number, and then issues the
> reply.
>
> Works well for us and our customers...
>
> Ted
>
>
> **
> 
> **
> Confidentiality: This e-mail and any files transmitted with it are
> confidential and intended solely for the use of the individual or entity
> to whom they are addressed.  If you have received this e-mail in error,
> use of this information (including disclosure, copying or distribution)
> may be unlawful.  Please notify [EMAIL PROTECTED] and
> delete the message immediately.
>
> Security: Internet e-mail is not a 100% secure communications medium.
>
> Viruses: This e-mail (and any attachments) has been checked (using
> Sophos Sweep 3.68 + patches) and found to be clean from any virus
> infection before leaving. Therefore neither Aquila Networks Services
> Ltd nor Midlands Electricity plc  or any of their group undertakings
> (as defined by the Companies Act
> 1989) (together referred to as the "Companies") accept legal
> responsibility for this message or liability for the consequences of
> any computer viruses which may have been transmitted by this e-mail.
>
> Monitoring: All electronic communications with the Companies may be
> monitored in accordance with the UK Regulation of Investigatory Powers
> Act, Lawful Business Practice Regulations, 2000.  If you do not
> consent to such monitoring, you should contact the sender of this
> e-mail.
>
> Aquila Networks Services Limited,
> Registered office: Whittington Hall, Whittington, Worcester, WR5 2RB
> Registered in England and Wales number 3600545 This e-mail may be sent
> on behalf of any of the Companies.
> **
> 
> **




Confidentiality: This e-mail and any files transmitted with it are
confidential and intended solely for the use of the individual or entity to
whom they are addressed.  If you have received this e-mail in error, use of
this information (including disclosure, copying or distribution) may be
unlawful.  Please notify [EMAIL PROTECTED] and delete the
message immediately.
Security: Internet e-mail is not a 100% secure communications medium.
Viruses: This e-mail (and any attachments) has been checked (using Sophos
Sweep 3.74 + patches) and found to be clean from any virus infection before
leaving. Therefore neither Aquila Networks Services Ltd nor Midlands
Electricity plc or any of their group undertakings  (as defined by the
Companies Act 1989) (together referred to as the "Companies") accept legal
respon

Automatically setting a volume to "unavailable"

[Gerald Wichmann]

Is there a way to make TSM *not* mark a volume unavailable when there's a
problem reading it?

Gerald Wichmann
Manager, Systems Engineering
ZANTAZ, Inc.
925.598.3099 (w)



This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.

Re: Storagetek L180 with SDLT320 and DLT7000 drive

[Stapleton, Mark]

From: Scott, Brian [mailto:[EMAIL PROTECTED] 
>The way we've dealt with a mixed drive/media environment is to incorporate
ACSLS and Gresham's DistribuTAPE to create separate tape pools and then
within TSM create the separate libraries, device classes, storage pools,
etc. We do that with LTO, STK 9940A, and STK 9940B drives.<

A fine solution, but a very pricy one.
 
--
Mark Stapleton ([EMAIL PROTECTED])

Re: Scratch's low

[Stapleton, Mark]

From: William Rosette [mailto:[EMAIL PROTECTED] 
>We have a script that does our daily backups, and with DRM piece with
TSM.  We are currently at 34 Scratch tapes and sending 15-20 tapes offsite.
2 days left of scratches.  I have been running reclamation on COPYPOOL at
hi=50, and a move data on tapes that are 0-18% pct util and volume
status=full.  Can't figure what outgoing more than incoming, any helpers
out there.<

First approximation says that you're backing up significantly more data now than you 
did previously. Check your dsmaccnt.log. (You do have accounting turned on, don't you?)
 
How many reclaimed tapes come back from your vault on a daily basis? Are any of your 
reclaimed tapes in PENDING mode? What percentage of your copy pool tapes have less 
than 45% occupancy?
 
Don't get in the habit of regularly running MOVE DATAs. If you're required to do that 
on a regular basis to keep room in the library, and everything else is running well, 
you have a resource constraint in your library that is only solvable with a larger 
library.
 
--
Mark Stapleton ([EMAIL PROTECTED])

Re: Storagetek L180 with SDLT320 and DLT7000 drive

[Scott, Brian]

Kurt,

The way we've dealt with a mixed drive/media environment is to incorporate
ACSLS and Gresham's DistribuTAPE to create separate tape pools and then
within TSM create the separate libraries, device classes, storage pools,
etc. We do that with LTO, STK 9940A, and STK 9940B drives.

Regards,
Brian

Brian Scott
EDS - EOGDE
GM Distributed Management Systems Engineering
MS 3234
750 Tower Drive
Troy, MI  48098

* phone: +01-248-265-4596 (8-365)
* mailto:[EMAIL PROTECTED]




-Original Message-
From: Kurt Beyers [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 11:28 AM
To: [EMAIL PROTECTED]
Subject: Storagetek L180 with SDLT320 and DLT7000 drive


Hello again,

I'm still confused if a Storagetek library L180 with two SDLT drives and 1
DLT7000 drive is supported by TSM (server 5.2.x.y). I've been reading the
manuals again and the TSM manual says:

"While the Tivoli Storage Manager server now allows mixed device types in a
library, the mixing of different generations of the same type of drive is
still not supported. A new generation of media can be read and written to by
new drives, but cannot be read by older drives. The previous generation of
media usually can be read but cannot be written to by the new drives that
support the new generation of media."

But is a SDLT tape considered as a new generation derived from DLT7000 (SDLT
can read only a DLTIV tape and a SDLT tape cannot be read by a DLT7000
drive)? The manual says you cannot mix DLT7000 and DLT8000 drives (both
DLTIV media), neither can SDLT220 and SDLT320 be mixed. But is the same
reasoning valid for DLTIV and SDLT320? Has anybody tried this already or
does anybody knows an official answer from IBM itself? Or an answer from IBM
directly?

The library should be configured as follows:

define library mixlib libtype=scsi
define path server01 mixlib srctype=server desttype=library device=lb3.0.0.0

define drive mixlib dlt_mt4
define drive mixlib lto_mt5
define path server01 dlt_mt4 srctype=server desttype=drive library=mixlib
device=mt4.0.0.0 define path server01 sdlt_mt5 srctype=server desttype=drive
library=mixlib device=mt5.0.0.0

The type of the drives (DLT or SDLT is not yet specified anywhere), this is
done in the device class definition:

define devclass dlt_class devtype=dlt format=dlt35c library=mixlib define
devclass sdlt_class devtype=dlt format=sdlt320c library=mixlib

The format=drive cannot be used as the specified format is used by TSM to
select a drive.

And finally the storagepools are defined:

define stgpool dlt_pool dlt_class maxscratch=20
define stgpool sdlt_pool sdlt_class maxscratch=20

But if you checkin or label a new tape, how does TSM knows that it is a DLT
or SDLT tape? Or how does TSM knows when a new scratch volume is allocated
it is a DLT scratch tape or a SDLT scratch tape? The storagepool is linked
to DLT or SDLT through the device class. But in the drive definition or path
definition, the type of drive (DLT or SDLT) is not mentioned. So am I
missing a link here?

Any answers, remarks or other insights are more than appreciated.

Kurt

Storagetek L180 with SDLT320 and DLT7000 drive

[Kurt Beyers]

Hello again,

I'm still confused if a Storagetek library L180 with two SDLT drives and 1
DLT7000 drive is supported by TSM (server 5.2.x.y). I've been reading the
manuals again and the TSM manual says:

"While the Tivoli Storage Manager server now allows mixed device types in a
library, the mixing of different generations of the same type of drive is
still not supported. A new generation of media can be read and written to by
new drives,
but cannot be read by older drives. The previous generation of media usually
can be read but cannot be written to by the new drives that support the new
generation of media."

But is a SDLT tape considered as a new generation derived from DLT7000 (SDLT
can read only a DLTIV tape and a SDLT tape cannot be read by a DLT7000
drive)? The manual says you cannot mix DLT7000 and DLT8000 drives (both
DLTIV media), neither can SDLT220 and SDLT320 be mixed. But is the same
reasoning valid for DLTIV and SDLT320? Has anybody tried this already or
does anybody knows an official answer from IBM itself? Or an answer from IBM
directly?

The library should be configured as follows:

define library mixlib libtype=scsi
define path server01 mixlib srctype=server desttype=library device=lb3.0.0.0

define drive mixlib dlt_mt4
define drive mixlib lto_mt5
define path server01 dlt_mt4 srctype=server desttype=drive library=mixlib
device=mt4.0.0.0
define path server01 sdlt_mt5 srctype=server desttype=drive library=mixlib
device=mt5.0.0.0

The type of the drives (DLT or SDLT is not yet specified anywhere), this is
done in the device class definition:

define devclass dlt_class devtype=dlt format=dlt35c library=mixlib
define devclass sdlt_class devtype=dlt format=sdlt320c library=mixlib

The format=drive cannot be used as the specified format is used by TSM to
select a drive.

And finally the storagepools are defined:

define stgpool dlt_pool dlt_class maxscratch=20
define stgpool sdlt_pool sdlt_class maxscratch=20

But if you checkin or label a new tape, how does TSM knows that it is a DLT
or SDLT tape? Or how does TSM knows when a new scratch volume is allocated
it is a DLT scratch tape or a SDLT scratch tape? The storagepool is linked
to DLT or SDLT through the device class. But in the drive definition or path
definition, the type of drive (DLT or SDLT) is not mentioned. So am I
missing a link here?

Any answers, remarks or other insights are more than appreciated.

Kurt

Re: Checkin libvol

[Bill Boyer]

The PERL script was more portable than an shell script. We do TSM
implementations on both Unix and Windows platforms. Yes, I work with Ted
Byrne. The Perl script can be used on any platform with Perl and the TSM
admin client loaded.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Wilcox, Andy
Sent: Friday, October 10, 2003 8:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Checkin libvol


Hiya Ted,

Just out of complete curiosity, why would you want to run such a script from
somewhere other than on the server itself??? We do something pretty much the
same except the scipt runs from AIX on our TSM server...

Cheers

Andy Wilcox
Midrange Services
Aquila Networks Services Ltd


> -Original Message-
> From: Ted Byrne [SMTP:[EMAIL PROTECTED]
> Sent: 10 October 2003 13:57
> To:   [EMAIL PROTECTED]
> Subject:  Re: Checkin libvol
>
> > >Hi everyone!
> > >Everytime I try to checkin my tapes to my library I need to run q
> > request and reply 
> > >Is it possible to checkin tape without to run a reply ?
>
> Checking in the tapes through an I/O station (search=bulk) does require
> that a reply be issued to a request.  However, for many of our customers,
> it is not practical to have the operator who  is actually handling tapes
> running a checkin manually after the Entry/Exit port is loaded with the
> day's tapes (almost always less than the capacity of the entry/exit port).
>
> For this situation, we have written a small perl script that gets
> scheduled
> once a day,  typically at the end of each weekday.  It's defined as a
> client event to run on a machine with the administrative client
> installed.  The script runs, issues the checkin libv command, issues the
> "q
> request", parses the output to get the request number, and then issues the
> reply.
>
> Works well for us and our customers...
>
> Ted
>
>
> **
> **
> Confidentiality: This e-mail and any files transmitted with it are
> confidential and intended solely for the use of the individual or entity
> to whom they are addressed.  If you have received this e-mail in error,
> use of this information (including disclosure, copying or distribution)
> may be unlawful.  Please notify [EMAIL PROTECTED] and
> delete the message immediately.
>
> Security: Internet e-mail is not a 100% secure communications medium.
>
> Viruses: This e-mail (and any attachments) has been checked (using Sophos
> Sweep 3.68 + patches) and found to be clean from any virus infection
> before leaving.
> Therefore neither Aquila Networks Services Ltd nor Midlands Electricity
> plc  or any of their group undertakings  (as defined by the Companies Act
> 1989) (together referred to as the "Companies") accept legal
> responsibility for this message or liability for the consequences of any
> computer viruses which may have been transmitted by this e-mail.
>
> Monitoring: All electronic communications with the Companies may be
> monitored in accordance with the UK Regulation of Investigatory Powers
> Act, Lawful Business Practice Regulations, 2000.  If you do not consent to
> such monitoring, you should contact the sender of this e-mail.
>
> Aquila Networks Services Limited,
> Registered office: Whittington Hall, Whittington, Worcester, WR5 2RB
> Registered in England and Wales number 3600545
> This e-mail may be sent on behalf of any of the Companies.
> **
> **




Confidentiality: This e-mail and any files transmitted with it are
confidential and intended solely for the use of the individual or entity to
whom they are addressed.  If you have received this e-mail in error, use of
this information (including disclosure, copying or distribution) may be
unlawful.  Please notify [EMAIL PROTECTED] and delete the
message immediately.
Security: Internet e-mail is not a 100% secure communications medium.
Viruses: This e-mail (and any attachments) has been checked (using Sophos
Sweep 3.74 + patches) and found to be clean from any virus infection before
leaving.
Therefore neither Aquila Networks Services Ltd nor Midlands Electricity plc
or any of their group undertakings  (as defined by the Companies Act 1989)
(together referred to as the "Companies") accept legal responsibility for
this message or liability for the consequences of any computer viruses which
may have been transmitted by this e-mail.

Monitoring: All electronic communications with the Companies may be
monitored in accordance with the UK Regulation of Investigatory Powers Act,
Lawful Business Practice Regulations, 2000.  If you do not consent to such
monitoring, you should contact the sender of this e-mail.
Aquila Networks Services Limited,
Registered office: Whittington Hall, Whitti

Re: Scratch's low

[William Rosette]

Hi TSM guru's

  We have a script that does our daily backups, and with DRM piece with
TSM.  We are currently at 34 Scratch tapes and sending 15-20 tapes offsite.
2 days left of scratches.  I have been running reclamation on COPYPOOL at
hi=50, and a move data on tapes that are 0-18% pct util and volume
status=full.  Can't figure what outgoing more than incoming, any helpers
out there.

Thank You,
Bill Rosette
Data Center/IS/Papa Johns International
WWJD

SV: Checkin libvol

[Christian Svensson]

Hi Everyone!
Thanks for everyones feedback.
So if I understand everyone right. You can not checkin tapes via our I/O port without 
to run reply 
So the only way in my case is to write a batch file who does everything for me.

dsmadmc checkin libvol ltolib search=b checkl=yes
dsmadmc q request > c:\request.txt
FOR /f "tokens=1" %%i IN ('C:\request.txt') DO dsmadmc reply %%i

/Christian


-Ursprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Wilcox,
Andy
Skickat: den 10 oktober 2003 14:58
Till: [EMAIL PROTECTED]
Ämne: Re: Checkin libvol


Hiya Ted,

Just out of complete curiosity, why would you want to run such a script from
somewhere other than on the server itself??? We do something pretty much the
same except the scipt runs from AIX on our TSM server...

Cheers

Andy Wilcox
Midrange Services
Aquila Networks Services Ltd


> -Original Message-
> From: Ted Byrne [SMTP:[EMAIL PROTECTED]
> Sent: 10 October 2003 13:57
> To:   [EMAIL PROTECTED]
> Subject:  Re: Checkin libvol
>
> > >Hi everyone!
> > >Everytime I try to checkin my tapes to my library I need to run q
> > request and reply 
> > >Is it possible to checkin tape without to run a reply ?
>
> Checking in the tapes through an I/O station (search=bulk) does require
> that a reply be issued to a request.  However, for many of our customers,
> it is not practical to have the operator who  is actually handling tapes
> running a checkin manually after the Entry/Exit port is loaded with the
> day's tapes (almost always less than the capacity of the entry/exit port).
>
> For this situation, we have written a small perl script that gets
> scheduled
> once a day,  typically at the end of each weekday.  It's defined as a
> client event to run on a machine with the administrative client
> installed.  The script runs, issues the checkin libv command, issues the
> "q
> request", parses the output to get the request number, and then issues the
> reply.
>
> Works well for us and our customers...
>
> Ted
>
>
> **
> **
> Confidentiality: This e-mail and any files transmitted with it are
> confidential and intended solely for the use of the individual or entity
> to whom they are addressed.  If you have received this e-mail in error,
> use of this information (including disclosure, copying or distribution)
> may be unlawful.  Please notify [EMAIL PROTECTED] and
> delete the message immediately.
>
> Security: Internet e-mail is not a 100% secure communications medium.
>
> Viruses: This e-mail (and any attachments) has been checked (using Sophos
> Sweep 3.68 + patches) and found to be clean from any virus infection
> before leaving.
> Therefore neither Aquila Networks Services Ltd nor Midlands Electricity
> plc  or any of their group undertakings  (as defined by the Companies Act
> 1989) (together referred to as the "Companies") accept legal
> responsibility for this message or liability for the consequences of any
> computer viruses which may have been transmitted by this e-mail.
>
> Monitoring: All electronic communications with the Companies may be
> monitored in accordance with the UK Regulation of Investigatory Powers
> Act, Lawful Business Practice Regulations, 2000.  If you do not consent to
> such monitoring, you should contact the sender of this e-mail.
>
> Aquila Networks Services Limited,
> Registered office: Whittington Hall, Whittington, Worcester, WR5 2RB
> Registered in England and Wales number 3600545
> This e-mail may be sent on behalf of any of the Companies.
> **
> **



Confidentiality: This e-mail and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are addressed.  
If you have received this e-mail in error, use of this information (including 
disclosure, copying or distribution) may be unlawful.  Please notify [EMAIL PROTECTED] 
and delete the message immediately.
Security: Internet e-mail is not a 100% secure communications medium.
Viruses: This e-mail (and any attachments) has been checked (using Sophos Sweep 3.74 + 
patches) and found to be clean from any virus infection before leaving.
Therefore neither Aquila Networks Services Ltd nor Midlands Electricity plc  or any of 
their group undertakings  (as defined by the Companies Act 1989) (together referred to 
as the "Companies") accept legal responsibility for this message or liability for the 
consequences of any computer viruses which may have been transmitted by this e-mail.

Monitoring: All electronic communications with the Companies may be monitored in 
accordance with the UK Regulation of Investigatory Powers Act, Lawful Business 
Practice Regulations, 2000.  If you do not consent to such

Re: Administrative tools for Unix or Linux servers

[David E Ehresman]

>How are people handling the kinds of scheduling and
>monitoring functions described above on other platforms with similar
>tools available, such as Intel Linux or various Unix implementations?

By writing scripts.  The two biggest hurdles to overcome when moving
from a MVS TSM to a Unix TSM is tape monitoring/vaulting and admin
scheduling/monitoring.

David

Re: ADSM with Windows 2003 Server and SFU 3.5

[Remco Post]

On Fri, 10 Oct 2003 15:06:40 +0200
Gregor Küpper <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> we have a installation with a Windows 2003 Cluster and Microsoft
> Services for UNIX SFU 3.5
> In SFU we enable case sensitive filename processing. ( AAA.txt is not
> the same as aaa.txt )
> We are able to backup these files, but cannot restore them.
> The error message is: file already exist
> Who can help us?
> 
> Regards,
> 
> Gregor K|pper

IBM can. As soon as Tivoli is ready to admit that it is a feature of the
NTFS filesystem to be not only case preserving, but also case-sensitive, and
they are ready to admit that is is their job to be able to backup and
restore all files that can legally excist on a NTFS filesystem.

Basically IBM claims WAD, NTFS is not supposed to be used in a case
sensitive way, so we don't support that

-- 
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten  http://www.sara.nl
High Performance Computing  Tel. +31 20 592 8008Fax. +31 20 668 3167

"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer industry
didn't even foresee that the century was going to end." -- Douglas Adams

Re: ADSM with Windows 2003 Server and SFU 3.5

[Wheelock, Michael D]

Hi,

This sounds like a permissions issue.  Can you, for example, restore the
AAA.txt file to another location, then copy it to the nfs shares?  If you
can't then you are running into a permission issue (typically on the
unix/vms side) and need to look at the file perms there.  The only other
thing I can think of is that the user whose context the restore is running
as, may not have the permissions too.  Others on the list can check me if I
am wrong, but there are occasions where the restore can run as the local
system account with no network privs.  This may also be messing you up.  If
you are doing an interactive restore through the gui, it should run as your
user contect though.  Just some ideas to look at.

Just out of curiosity, why are you backing up things through sfu instead of
actually backing up the systems the files reside on?

Michael Wheelock
Integris Health

-Original Message-
From: Gregor Küpper [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 10, 2003 8:07 AM
To: [EMAIL PROTECTED]
Subject: ADSM with Windows 2003 Server and SFU 3.5


Hi,

we have a installation with a Windows 2003 Cluster and Microsoft Services
for UNIX SFU 3.5 In SFU we enable case sensitive filename processing. (
AAA.txt is not the same as aaa.txt ) We are able to backup these files, but
cannot restore them. The error message is: file already exist Who can help
us?

Regards,

Gregor K|pper

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: Checkin libvol

[Ted Byrne]

why would you want to run such a script from
somewhere other than on the server itself???
Hi Andy,

Usually the checkin script does run on the server.  In some instances, we
also have a set of administrative scripts and programs running from another
system, and we group all of those together to make the administration simpler.
Ted

ADSM with Windows 2003 Server and SFU 3.5

[Gregor Küpper]

Hi,

we have a installation with a Windows 2003 Cluster and Microsoft
Services for UNIX SFU 3.5
In SFU we enable case sensitive filename processing. ( AAA.txt is not
the same as aaa.txt )
We are able to backup these files, but cannot restore them.
The error message is: file already exist
Who can help us?
Regards,

Gregor K|pper

Re: Checkin libvol

[Wilcox, Andy]

Hiya Ted,

Just out of complete curiosity, why would you want to run such a script from
somewhere other than on the server itself??? We do something pretty much the
same except the scipt runs from AIX on our TSM server...

Cheers

Andy Wilcox
Midrange Services
Aquila Networks Services Ltd


> -Original Message-
> From: Ted Byrne [SMTP:[EMAIL PROTECTED]
> Sent: 10 October 2003 13:57
> To:   [EMAIL PROTECTED]
> Subject:  Re: Checkin libvol
>
> > >Hi everyone!
> > >Everytime I try to checkin my tapes to my library I need to run q
> > request and reply 
> > >Is it possible to checkin tape without to run a reply ?
>
> Checking in the tapes through an I/O station (search=bulk) does require
> that a reply be issued to a request.  However, for many of our customers,
> it is not practical to have the operator who  is actually handling tapes
> running a checkin manually after the Entry/Exit port is loaded with the
> day's tapes (almost always less than the capacity of the entry/exit port).
>
> For this situation, we have written a small perl script that gets
> scheduled
> once a day,  typically at the end of each weekday.  It's defined as a
> client event to run on a machine with the administrative client
> installed.  The script runs, issues the checkin libv command, issues the
> "q
> request", parses the output to get the request number, and then issues the
> reply.
>
> Works well for us and our customers...
>
> Ted
>
>
> **
> **
> Confidentiality: This e-mail and any files transmitted with it are
> confidential and intended solely for the use of the individual or entity
> to whom they are addressed.  If you have received this e-mail in error,
> use of this information (including disclosure, copying or distribution)
> may be unlawful.  Please notify [EMAIL PROTECTED] and
> delete the message immediately.
>
> Security: Internet e-mail is not a 100% secure communications medium.
>
> Viruses: This e-mail (and any attachments) has been checked (using Sophos
> Sweep 3.68 + patches) and found to be clean from any virus infection
> before leaving.
> Therefore neither Aquila Networks Services Ltd nor Midlands Electricity
> plc  or any of their group undertakings  (as defined by the Companies Act
> 1989) (together referred to as the "Companies") accept legal
> responsibility for this message or liability for the consequences of any
> computer viruses which may have been transmitted by this e-mail.
>
> Monitoring: All electronic communications with the Companies may be
> monitored in accordance with the UK Regulation of Investigatory Powers
> Act, Lawful Business Practice Regulations, 2000.  If you do not consent to
> such monitoring, you should contact the sender of this e-mail.
>
> Aquila Networks Services Limited,
> Registered office: Whittington Hall, Whittington, Worcester, WR5 2RB
> Registered in England and Wales number 3600545
> This e-mail may be sent on behalf of any of the Companies.
> **
> **



Confidentiality: This e-mail and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are addressed.  
If you have received this e-mail in error, use of this information (including 
disclosure, copying or distribution) may be unlawful.  Please notify [EMAIL PROTECTED] 
and delete the message immediately.
Security: Internet e-mail is not a 100% secure communications medium.
Viruses: This e-mail (and any attachments) has been checked (using Sophos Sweep 3.74 + 
patches) and found to be clean from any virus infection before leaving.
Therefore neither Aquila Networks Services Ltd nor Midlands Electricity plc  or any of 
their group undertakings  (as defined by the Companies Act 1989) (together referred to 
as the "Companies") accept legal responsibility for this message or liability for the 
consequences of any computer viruses which may have been transmitted by this e-mail.

Monitoring: All electronic communications with the Companies may be monitored in 
accordance with the UK Regulation of Investigatory Powers Act, Lawful Business 
Practice Regulations, 2000.  If you do not consent to such monitoring, you should 
contact the sender of this e-mail.
Aquila Networks Services Limited,
Registered office: Whittington Hall, Whittington, Worcester, WR5 2RB
Registered in England and Wales number 3600545
This e-mail may be sent on behalf of any of the Companies.

Re: Checkin libvol

[Ted Byrne]

>Hi everyone!
>Everytime I try to checkin my tapes to my library I need to run q
request and reply 
>Is it possible to checkin tape without to run a reply ?
Checking in the tapes through an I/O station (search=bulk) does require
that a reply be issued to a request.  However, for many of our customers,
it is not practical to have the operator who  is actually handling tapes
running a checkin manually after the Entry/Exit port is loaded with the
day's tapes (almost always less than the capacity of the entry/exit port).
For this situation, we have written a small perl script that gets scheduled
once a day,  typically at the end of each weekday.  It's defined as a
client event to run on a machine with the administrative client
installed.  The script runs, issues the checkin libv command, issues the "q
request", parses the output to get the request number, and then issues the
reply.
Works well for us and our customers...

Ted

Re: tape errors after 3590H upgrade - K tape - 3592s

[D. Malbrough]

Jason,

I have been experiencing problems with 3590 K-Type tapes as well and it has been well 
over 5 months since we have upgraded from B1A/E1A to H1A. You may be running into an 
APAR that support informed me on last month where you have to mark the volumes as 
READOnly to get them to mount. See info below:

DCF Document ID: 1137386 - IBM Tivoli Storage Manager: How to diagnose
ANR8447E and ANR1401W messages
Problem Desc:  On initial configuration or after migrating from one type of
drive type to another (say like 3590E to 3590H model), it is possible to
receive ANR8447E & ANR1401W messages if configuration is incorrect or drive
migration is not done correctly.

Solution:  For each tape volume that TSM writes own, it records the format
of the volume in the TSM database. When a tape needs to be mounted in a
drive, TSM checks the format of the tape from the db and checks to see if
any defined drive to TSM is capable of reading or writing in that format
(depending on the operation). If no drive matches the required tape format
in the required mode (read/write) then the mount fails with ANR8447E and
ANR1401W messages.
When this happens, you first have to find 2 things, (1) what formats does
the drives support for read and for write and (2) what format are the
volumes recorded with in the TSM db.
For (1), you use the "show library" command. This command will report the
drive list. For each drive in the list, its read and write capabilities are
reported. For example, for a 3590E drive, you would get :
Device Class = 3590,
RD Capabilities = 03F0,
(3590H-C,3590H-B,3590E-C,3590E-B,3590C,3590B),
WR Capabilities = 0300,
(3590H-C,3590H-B),
This shows the drive is capable of reading 3590B, 3590C, 3590E-B, 3590E-C
3590H-B and 3590H-C but can only write 3590H-B or 3590H-C.

For (2), you can do an MMS server trace. The trace would show the following
:

13:41:49.980 [55][mmslib.c][8032]: Obtaining reservation for volume A10774
in library 3494LIB; activity=4.
13:41:49.982 [55][mmsdrive.c][1227]: Acquiring a drive in library 3494LIB -
format 0080 and mode 1.
13:41:50.512 [55][mmsdrive.c][7146]: Drives in list cannot support format
0080 in mode 1.

In the above trace entries, it shows that TSM is trying to mount tape
A10774 which is a 3590E-C format tape (format=0080)in order to write to
the tape (mode 1).
In the above example, the mount failed with ANR8447E and ANR1401W because
the
drive cannot write in 3590E-C format (see (1)). This error originated from
a customer failing to update all filling volume to readonly access after
upgrading drives from 3590E to 3590H.
FYI, for a list of tape formats, please refer to the mms.c module.

Another way to get the tape volume format is retrieve the stored format for
the involved volume from the AS.Volume.Status table. The format is the 2nd
word stored in the pvrattr field in the table (column 13). You can

a) Issue the following TSM admin command to create a temporary sql table
that maps the AS.Volume.Status table :
---> create sqltable AS.Volume.Status volstat (case sensitive)

b) Issue the following TSM admin command to retrieve all filling volumes in
readwrite access with format = '0080' (3590E-C):
---> select volumes.volume_name from volumes,volstat where -
volumes.volume_name=volstat.c1 and volumes.status='FILLING' and -
volumes.access='READWRITE' and -
substring((cast(hex(volstat.c13) as char(112))) from 9 for 8) = '0080'

The above commands are particularly useful to "zero in" on a particular
volume.
Once the drive are defined properly and volumes properly set to readonly,
the ANR8447E and ANR1401W should cease.
Add Dt:  2003-09-04
Add Time:  09:10:24


Some Important Notes:
1.  When issuing the sql commands, follow the letter casing as shown in the
example
2.  In your case, the trace showed the following error:
  [mmsdrive.c][7115]: Drives in list cannot support format 0020 in
mode 1.
 Thus, for the select statement you need to replace the 0080 with
0020 to reflect the 3590H-C drive you are using.
3.  Once you get a list of the affected volumes you must update their
ACCESS to READONLY and either perform MOVE DATAs or allow the data to
expire off.The volumes will eventually get returned to scratch
at which time on their subsequent write, will get the proper volume
attribute info recorded.

Regards,

Demetrius Malbrough


   ---Original Message---
   > From: Jason Lee <[EMAIL PROTECTED]>
   > Subject: tape errors after 3590H upgrade - K tape - 3592s
   > Sent: 09 Oct 2003 18:22:34
   >
   >  Hi,
   >  
   >  A couple of months ago we upgraded our 3590E drives to H. Marked
   >  everything as readonly.. moved all the data to "new" (scratch) tape 
so
   >  as not to mix formats on the tape. etc etc etc
   >  
   >  Now I'm noticing a high number of media errors. I'm assuming that some
   >  of the old tape is not up to supporting 384 tracks. The question is,
   >  how does one go about finding out which tapes are

Re: Checkin libvol

[Jacque Mergens]

Someone correct me if I'm wrong but it has been my experience that when you use a bulk 
search, the library accesses the I/O port and expects manual intervention of an 
operator to put tape in the I/O port. In this case you will either have to have a 
console activated to watch for the reply number or perform a q req.  
When you use search=yes, it will scan the body of the library and the app expects that 
the tapes are already there and doesn't require a reply for this reason.


Jacque Mergens
Sr Systems Engineer
Emageon 
1200 Corporate Dr
Birmingham, AL 35242
205.980.7543 (o)
205.410.8326 (c)

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Christian Svensson
Sent: Friday, October 10, 2003 7:36 AM
To: [EMAIL PROTECTED]
Subject: SV: Checkin libvol

Hi Otto!
Search=yes is not picking up the media from the Service port.
I need to use Search=bulk.
And and it´s still does´nt work.

/Christian

-Ursprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Otto
Schakenbos
Skickat: den 10 oktober 2003 14:25
Till: [EMAIL PROTECTED]
Ämne: Re: Checkin libvol


we do for our 7337 (you should use your own libname ofcourse)
checkin libv  7337 search=yes checkl=yes stat=scr
and sit back

Christian Svensson wrote:

>Hi everyone!
>Everytime I try to checkin my tapes to my library I need to run q request and reply 
>
>Is it possible to checkin tape without to run a reply ?
>
>TSM Server : 5.1.7.1
>OS : Windows 2000 (SP 3)
>Library : Qualstar TLS-8222, Barcode Reader, Service port.
>Server HW : Dell PowerEdge 2650
>
>Best Regard / Med vdnlig hdlsning
>Christian Svensson
>Tivoli Storage Manager Certified
>.
>
>Cristie Nordic AB
>Box 2Phone : +46-(0)8-718 43 30
>SE-131 06 Nacka  Mobil : +46-(0)70-325 15 77
>Sweden   eMail : [EMAIL PROTECTED]
>Visit : Gamla Vdrmdvvdgen 4, Plan 2
>web : www.cristie.com 
>.
>
>
>
>


--
Otto Schakenbos
PC-Support

TEL: +49-7151/502 8468
FAX: +49-7151/502 8489
MOBILE: +49-172/7102715
E-MAIL: [EMAIL PROTECTED]

TFX IT-Service AG
Fronackerstrasse 33-35
71332 Waiblingen
GERMANY

Re: Checkin libvol

[Stapleton, Mark]

From: Christian Svensson [mailto:[EMAIL PROTECTED] 
>Search=yes is not picking up the media from the Service port.
I need to use Search=bulk.
And and it´s still does´nt work.<

If you're loading tapes into the I/O station, you'll have to run the request/reply 
process to check them. The search=yes parameter is only used when you put tapes into 
the library manually.
 
--
Mark Stapleton ([EMAIL PROTECTED])

SV: Checkin libvol

[Christian Svensson]

Hi Otto!
Search=yes is not picking up the media from the Service port.
I need to use Search=bulk.
And and it´s still does´nt work.

/Christian

-Ursprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Otto
Schakenbos
Skickat: den 10 oktober 2003 14:25
Till: [EMAIL PROTECTED]
Ämne: Re: Checkin libvol


we do for our 7337 (you should use your own libname ofcourse)
checkin libv  7337 search=yes checkl=yes stat=scr
and sit back

Christian Svensson wrote:

>Hi everyone!
>Everytime I try to checkin my tapes to my library I need to run q request and reply 
>
>Is it possible to checkin tape without to run a reply ?
>
>TSM Server : 5.1.7.1
>OS : Windows 2000 (SP 3)
>Library : Qualstar TLS-8222, Barcode Reader, Service port.
>Server HW : Dell PowerEdge 2650
>
>Best Regard / Med vdnlig hdlsning
>Christian Svensson
>Tivoli Storage Manager Certified
>.
>
>Cristie Nordic AB
>Box 2Phone : +46-(0)8-718 43 30
>SE-131 06 Nacka  Mobil : +46-(0)70-325 15 77
>Sweden   eMail : [EMAIL PROTECTED]
>Visit : Gamla Vdrmdvvdgen 4, Plan 2
>web : www.cristie.com 
>.
>
>
>
>


--
Otto Schakenbos
PC-Support

TEL: +49-7151/502 8468
FAX: +49-7151/502 8489
MOBILE: +49-172/7102715
E-MAIL: [EMAIL PROTECTED]

TFX IT-Service AG
Fronackerstrasse 33-35
71332 Waiblingen
GERMANY

Re: Checkin libvol

[Otto Schakenbos]

we do for our 7337 (you should use your own libname ofcourse)
checkin libv  7337 search=yes checkl=yes stat=scr
and sit back
Christian Svensson wrote:

Hi everyone!
Everytime I try to checkin my tapes to my library I need to run q request and reply 

Is it possible to checkin tape without to run a reply ?
TSM Server : 5.1.7.1
OS : Windows 2000 (SP 3)
Library : Qualstar TLS-8222, Barcode Reader, Service port.
Server HW : Dell PowerEdge 2650
Best Regard / Med vdnlig hdlsning
Christian Svensson
Tivoli Storage Manager Certified
.
Cristie Nordic AB
Box 2Phone : +46-(0)8-718 43 30
SE-131 06 Nacka  Mobil : +46-(0)70-325 15 77
Sweden   eMail : [EMAIL PROTECTED]
Visit : Gamla Vdrmdvvdgen 4, Plan 2
web : www.cristie.com 
.





--
Otto Schakenbos
PC-Support
TEL: +49-7151/502 8468
FAX: +49-7151/502 8489
MOBILE: +49-172/7102715
E-MAIL: [EMAIL PROTECTED]
TFX IT-Service AG
Fronackerstrasse 33-35
71332 Waiblingen
GERMANY

Checkin libvol

[Christian Svensson]

Hi everyone!
Everytime I try to checkin my tapes to my library I need to run q request and reply 

Is it possible to checkin tape without to run a reply ?
 
TSM Server : 5.1.7.1
OS : Windows 2000 (SP 3)
Library : Qualstar TLS-8222, Barcode Reader, Service port.
Server HW : Dell PowerEdge 2650
 
Best Regard / Med vänlig hälsning
Christian Svensson
Tivoli Storage Manager Certified


Cristie Nordic AB   
Box 2Phone : +46-(0)8-718 43 30 
SE-131 06 Nacka  Mobil : +46-(0)70-325 15 77
Sweden   eMail : [EMAIL PROTECTED]  
Visit : Gamla Värmdövägen 4, Plan 2 
web : www.cristie.com  

 
 

wrong volume type in NSM 3494

[Joern Gehm]

Hello,

I filled the Convenience I/O Station of a IBM 3494 Tape Library with 30
K-labeled (3590 extended length Cartridges). They are numbered from
05 to 050029 by Bar Code label. 29 Cartridges get the rigth Volume
Type,
one Cartrigde (050016) get a wrong type and cannot be checked in:

%mtlib -l /dev/lmcp0 -qV -V 050016
Volume Data:
   volume state.00
   logical volume...No
   volume class.3480 1/2 inch cartridge tape
   volume type..CST-2 320m nominal length
   volser...050016
   category.FF00
   subsystem affinity...01 02 03 04 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00

The other cartrigdes shows (for example 050017 after checkin):

%mtlib -l /dev/lmcp0 -qV -V 050017
Volume Data:
   volume state.00
   logical volume...No
   volume class.3590 1/2 inch cartridge tape
   volume type..EHPCT extended length
   volser...050017
   category.012C
   subsystem affinity...01 02 03 04 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00

After ejection of cartridge 050016 with the command:

  mtlib -l /dev/lmcp0 -C -V 050016 -t FF11

there is no Information about this cartridge in the Tape Library.

I take another K-labelled 3590 cartridge and placed the Bar Code Number
from the 050016 cartridge on it and inserted it in the 3494. The effect
was the same:

   volume class.3480 1/2 inch cartridge tape
   volume type..CST-2 320m nominal length
   volser...050016

?



Thanks in advance,

__
Joern Gehm E-Mail: [EMAIL PROTECTED]
   Tel: (0221) 478-5350 ,  FAX: -5568 ,   Sekr: -5586
ZAIK/RRZK, Universitaet zu Koeln, Robert-Koch-Str. 10, 50931 Koeln
__

/ /OREF:CPTC47F0 Re: Mkcd-AIX help

[Cecily Hewlett]

Dear Balanand,

Excluding files from a mkcd, works the same way as a mksysb.  mkcd
uses /etc/exclude.rootvg for files/directories to be excluded from
the backup.

  Use the -e flag.

/usr/sbin/mkcd -d /dev/cd0 -L -D -e


The mkcd command automatically excludes any temporary files created
during the backup, by  inserting  the  filenames  into the
/etc/exclude.rootvg file...

# cat /etc/exclude.rootvg
./mkcd/mksysb_image
./mkcd/cd_images
./mkcd/cd_fs

I have a nice script which runs my mksysbs, using mkcd command, if u
want it let me know.

Cecily

Re: 'Maximum Scratch Volumes Allowed' clarrification

[John Naylor]

Gordon,
Maxscratch is just a value you set high enough to prevent failures due to
running out of storage.
It will not use more tapes
Look at your reuse delay values
Try a move data against the 6 empty filling tapes
The number of filling tapes in a collocated pool should bear some
relationship to either the number of nodes or filespaces depending on the
type of collocation.
If you have multiple filling tapes for the same node/filespace then you
probably have scheduling issues
John







Gordon Woodward <[EMAIL PROTECTED]>@vm.marist.edu> on 10/10/2003
12:23:15 AM

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

Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:'Maximum Scratch Volumes Allowed' clarrification


Hi all,

I'm after some clarrification about the stgp maxscratch setting for one of
our storage pools. We recently decommissioned a server and removed all it's
data out of TSM, thus freeing up a lot of tapes for other uses, but I'm now
finding that our collocated storage pool has decided to hoard all our
scratch tapes for itself, even though it doesn't put any data in them.

Our collocated tape storage pool currently has 32 tapes allocated to it,11
of which are filling with only 5 tapes of those having data on them. The
Maximum Scratch Volumes Allowed setting for this storage pool is set to
100, which is a tad excessive so I want to pull it back to a smaller
number. Would setting this maxscratch paramater back down to say 5 be
reasonable without causing other problems? This particular storage pool is
lucky to fill one tape a night and it reclaims about 1 tape a day, I don't
want it to keep stealing all available scratch tapes for itself as our tape
library is already at capacity.

Thanks in advance!


Gordon Woodward


--

 This e-mail may contain confidential and/or privileged information. If you
 are not the intended recipient (or have received this e-mail in error)
 please notify the sender immediately and destroy this e-mail. Any
 unauthorized copying, disclosure or distribution of the material in this
 e-mail is strictly forbidden.



**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

dsmcad running scheduler

[Lars Bebensee]

Hi folks,

I am sure this question has been asked before. One of our customers is
running dsmcad (Client ver 5.1.1.0) in "webclient schedule" mode. Last
night the schedules got missed. After I checked the log files this morning,
I realized dsmcad set with a HTTPClientport 1582 claims to have shifted to
port 1583:

10/09/03   16:58:27 Trying port number 1583
10/09/03   16:58:27 Obtained new port number on which to listen.

However, a "netstat -a" reveales that it is still listening on 1582. Is
there a reason why dsmcad would lie to the TSM server?

CYA Lars

/ /OREF:CPT9101F Re: TSM Backup client Mac osX

[Cecily Hewlett]

Dear Bruno,

Im running TSM 5.1 on AIX 5.1

I have also experienced these 'authentication' problems
intermittently.  At first I thought my nodes were 'locked' but this
wasn't the case.

Have set: PASSWORDACCESS GENERATE in dsm.sys, my schedule and storage
agent startup from cron, but sometimes the schedule would not kick
off the backups with these authentication problems.

The next morning, I would then run dsmc on client, &  would be
prompted for the nodename & password.
The following night backups would run as normal.

Cecily