Re: BACKUPSET DELETE PROBLEM

[Ruddy STOUDER]

I wrote the script yesterday afternoon (Belgian time), one of my
backupset expiring this afternoon, I will see how if it works.

What I am sure is that, the expiration process was working perfectly
before I decided to eject the backupsets and store them off-line. That's
why I was almost sure it would work to reload the tape in the library
before the expiration process happened.

I will see this afternoon and let you know.

If it does not work, I have a real problem ...


By the way, thanks to all of you taking time to answer and communicate
your experiences to others.

Do you know where it is possible to access all those mails centralized
on Internet ?

Ruddy

--
From: Maria Paz Gimeno
To: [EMAIL PROTECTED]
Sent: 11/08/2000 5:17:29 PM
Subject: Re: BACKUPSET DELETE PROBLEM

Ruddy,
Your workaround did not work for me.
When I deleted the backup set the tapes were already in the library, but
they remained in private state,
and the command to change to scratch didn't succeed.
The tape wan't change status because the volhistory entry was not
removed.
Could you change the status of the tapes from private to scratch?
Thanks
Maria

- Original Message -
From: Ruddy STOUDER <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 08, 2000 3:34 PM
Subject: Re: BACKUPSET DELETE PROBLEM


> The work-around I found in the meantime is write a script which is
> looking what backupset will expire, to call the tape back from
off-site,
> check it in with PRIVATE status and then make the backupset expire.
That
> way, it is ok but the MAIN condition is to have the tape in the
library
> before running the expire process.
>
> --
> From: Maria Paz Gimeno
> To: [EMAIL PROTECTED]
> Sent: 11/07/2000 8:47:14 PM
> Subject: Re: BACKUPSET DELETE PROBLEM
>
> M have not yet installed 3.7.4, but sure I will write to the list with
> the
> results.
> Thanks very much Richard for your help it is invaluable.
> Best regards
> Maria
>
> - Original Message -
> From: Richard Sims <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 07, 2000 5:04 PM
> Subject: Re: BACKUPSET DELETE PROBLEM
>
>
> > >We have the same problem overhere.  I think it has to be a bug
> because
> > >several other persons are having
> > >this problem too.  I hope there is someone outthere with a
solution.
> >
> > As mentioned last week, the 3.7.4 server README notes the APAR
> >  IC27123  BACKUPSETS DON'T EXPIRE PROPERLY
> > which may address the problem.  We need a 3.7.4 adopter to post to
> > the List as to whether that level fixes the noted problems.
> >  Richard Sims, BU

No Subject

[Ruddy STOUDER]

FULLY agree with you Maria. After many different trials, I decided to to
use Move Media for both directions, based on the Copy Storage Pool,
followed by an update status ReadOnly->Offsite.

I am not using nor running the cmd option.

To send tapes offsite, the move media is ejecting the tape, changing
status to readonly and ejecting the tape. The update volume is changing
status to offsite.

To call empty tapes back, the move media is modifying status. The
checkin is reallocating the tape to the library.

Ruddy

--
From: Maria Paz Gimeno
To: [EMAIL PROTECTED]
Sent: 11/08/2000 12:15:21 PM
Subject: Re: "Move media" vs. checkout

I use MOVE MEDIA for this operation both ways, out and in the library.
With CHECKOUT  you have to provide the volume labels of the tapes you
want
to remove from the library, while with "move media" you can select by
stgpool. I am not sure if the "checkout" changes the access to offsite
but
"Move media" creates a file with the volume label of the tapes that
processes, and you can afterwards run a command to perform an update of
the
volumes with access=offsite.
The only problem is that, what the command creates is a macro and can
only
be scheduled by a cron job,( my system is UNIX.)
The macro can not be scheduled by TSM, not included in a script. It has
to
run from the command line.
Regards
Maria

- Original Message -
From: Reiner Sauer <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 08, 2000 8:26 AM
Subject: Antw: "Move media" vs. checkout


I've learned that to get the tape out and set in the db to offsite, is
to
use the command checkout and the tape get offsite. Now the tape is not
availiable fpr the library. To get the tape in you should use the
commands
checkin and update volume.

>>> [EMAIL PROTECTED] 7.11.2000 22:14:11 >>>
I'm looking at moving our copypool tapes offsite.  We are not running
DRM.  I've been reading the archive of this list and it seems some
people
use the adsm checkout command and others the Move media command to
remove
the tapes from the library for offsite storage.  I've read up on both
and
it seems the move media command is the right one for removing the tape
from
the library and a checkin command to bring it back in.  Does anyone have
any comments on the checkout versus "move media" command that might help
explain their use?  Am I on the right track thinking the "move media"
command should be used?

Re: tsm 4.1 event notification

[Mark A. Adams]

Try snmp notification. With that you can eliminate all of your scripts.
You would just have to set up a snmp server. We use it and have the snmp
server send email to necessary individuals. This will pull errors straight
out of the activity log.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Steve Bennett
Sent: Wednesday, November 08, 2000 5:15 PM
To: [EMAIL PROTECTED]
Subject: tsm 4.1 event notification


We have been running adsm 3.2.1.50 running on aix for several years. We
have written numerous korn shell scripts that do monitoring functions
like checking for offline drives, missed or failed schedules,
outstanding tape mounts, etc.

One important function is notifying our operators of a pending tape
mount for the 8mm drive which is used for our offsite media. In aix we
accomplish this by a script that tails the adsm console log so that
mount and other necessary messages can be trapped. Once trapped we
generate emails for some messages and for other messages we ftp jcl to
our os390 system. The job runs and puts up a mount message on the
operator console.

Now we are in the process of replacing adsm with tsm 4.1 which will run
on windows 2000. To ease the migration I installed cygwin (bash shell)
and blat (mail) so that most of our aix scripts would work with minor
modifications. However, the really important script that tails the
console log has some problems. It works fine for a while and then just
stops working. I have not had any luck diagnosing the problem so I have
been looking for alternatives. So far I have looked at event logging for
file, filetext, nteventlog and userexit and for various reasons have not
been successfull implementing them.

How do the rest of you handle notifying your operations staff of tsm
manual tape mount requests or other events that need attention?


--

Steve Bennett, (907) 465-5783
State of Alaska, Information Technology Group, Technical Services
Section

tsm 4.1 event notification

[Steve Bennett]

We have been running adsm 3.2.1.50 running on aix for several years. We
have written numerous korn shell scripts that do monitoring functions
like checking for offline drives, missed or failed schedules,
outstanding tape mounts, etc.

One important function is notifying our operators of a pending tape
mount for the 8mm drive which is used for our offsite media. In aix we
accomplish this by a script that tails the adsm console log so that
mount and other necessary messages can be trapped. Once trapped we
generate emails for some messages and for other messages we ftp jcl to
our os390 system. The job runs and puts up a mount message on the
operator console.

Now we are in the process of replacing adsm with tsm 4.1 which will run
on windows 2000. To ease the migration I installed cygwin (bash shell)
and blat (mail) so that most of our aix scripts would work with minor
modifications. However, the really important script that tails the
console log has some problems. It works fine for a while and then just
stops working. I have not had any luck diagnosing the problem so I have
been looking for alternatives. So far I have looked at event logging for
file, filetext, nteventlog and userexit and for various reasons have not
been successfull implementing them.

How do the rest of you handle notifying your operations staff of tsm
manual tape mount requests or other events that need attention?


--

Steve Bennett, (907) 465-5783
State of Alaska, Information Technology Group, Technical Services
Section

Seeking Senior *SM administrator in Calgary, Alberta, Candada.

[Daniel Swan-TM]

My manager say's he's gonna buy me an ADSM mentor for Xmas, if I can track
one down.

I'm unable to provide any info as to reloc allow, salary, but these details
can be worked out.  Reply to sending address if interested.

Re: SELFTUNEXNSIZE

[Claudio Cofre Caro]

Ricardo,  Mr Sims te dice que "no todas las opciones" de TSM se pueden
setear mediante el comando SETOPT, y ésta es una de ellas. La forma de
setear esta opcion es modificar directamente esta opcion en el archivo de
opciones (dsmserv.opt) y luego reiniciar el servicio TSM Server.

Atte.

Claudio Cofré




   
 
Ricardo
 
Negrete  To: [EMAIL PROTECTED]  
 
 Subject: Re: SELFTUNEXNSIZE   
 
Sent by:   
 
"ADSM: Dist
 
Stor Manager"  
 
<[EMAIL PROTECTED]  
 
RIST.EDU>  
 
   
 
   
 
08-11-00   
 
17:39  
 
Please 
 
respond to 
 
"ADSM: Dist
 
Stor Manager"  
 
   
 
   
 




 I try:
SETOPT SELFTUNEXNSIZE yes

but is not successful.

ANR2020E SETOPT: Invalid parameter - SELFTUNEXNSIZE.


that it happens ?

Ricardo Negrete Santelices
Cientec Integración S.A.
Fono : (56 2) 335 7107
e-mail: [EMAIL PROTECTED]


-Mensaje original-
De: Richard Sims <[EMAIL PROTECTED]>
Para: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Fecha: Miércoles, 08 de Noviembre de 2000 03:54 p.m.
Asunto: Re: SELFTUNEXNSIZE


>>As I can change setting server Storage Options "SELFTUNEXNSIZE" to yes, =
>>from the TSM command line?
>
>Ricardo - Only the SETOPT command can dynamically set server options, and
>  only some of them.  The 4.1 Admin Ref manual indicates that the
>SETOPT command cannot set the one you want.  You can verify this in your
>server via HELP SETOPT.  Looks like you'll have to manually update the
>server options file and restart the server.
>   Richard Sims, BU

ANS1017E (RC-50)

[Maria Ragan]

server:  ADSM Server 3.7.2.0AIX 4.3.2.0
client:   NT 4.0; MS SQL Server 7.0; ADSMConnect Agent for MS SQL Server
1.1.1A

I'm receiving the following error when backing up the logs on one database
on this client.  The full database backups complete successfully on this and
other databases on this client.  Incrementals complete successfully on other
databases on this client.

:\WIN32APP\IBM\ADSM\agentsql\dsm, SQL status: DB-LIB message: Write on
'\\.\pipe\sqladsm\204541\4240' failed, status = 109. See the SQL Server
error log for more details., ADSM status: ANS1017E (RC-50)  Session
rejected: TCP/IP connection failure

Thanks,

Maria

Maria Ragan
Mid Range Systems
Bear Creek Corporation

Re: SELFTUNEXNSIZE

[Ricardo Negrete]

 I try:
SETOPT SELFTUNEXNSIZE yes

but is not successful.

ANR2020E SETOPT: Invalid parameter - SELFTUNEXNSIZE.


that it happens ?

Ricardo Negrete Santelices
Cientec Integración S.A.
Fono : (56 2) 335 7107
e-mail: [EMAIL PROTECTED]


-Mensaje original-
De: Richard Sims <[EMAIL PROTECTED]>
Para: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Fecha: Miércoles, 08 de Noviembre de 2000 03:54 p.m.
Asunto: Re: SELFTUNEXNSIZE


>>As I can change setting server Storage Options "SELFTUNEXNSIZE" to yes, =
>>from the TSM command line?
>
>Ricardo - Only the SETOPT command can dynamically set server options, and
>  only some of them.  The 4.1 Admin Ref manual indicates that the
>SETOPT command cannot set the one you want.  You can verify this in your
>server via HELP SETOPT.  Looks like you'll have to manually update the
>server options file and restart the server.
>   Richard Sims, BU

Re: Upgrade Serverlevel 3.1.2.16

[Richard Sims]

>On the FTP Servers of ftp.tivoli.com or service.boulder.ibm.com are only
>Levelupgrades of 3.7 and 4.1. Are there any Upgrades available for 3.1? I
>need it for long file names for Novell Fileservers...

I surmise that you are looking in the /storage/tivoli-storage-management/
area, whereas ADSM software is in the /storage/adsm/ area.

3.7.3.8 tivoli.tsm.msg.en_US.server

[Joel Fuhrman]

I'm trying to install the TSM Server 3.7.3.8 patches to a 3.7.3.0
installation running on AIX 4.3.3.0.  My problem is that smit does not list
the tivoli.tsm.msg.en_US.server in the installable filesets.  Any
suggestions as to what would cause this?

-
selected section from .toc  -- wrapped lines are indented for readability
-
PA3738M.bff 4 R S tivoli.tsm.msg.en_US.server {
tivoli.tsm.msg.en_US.server 03.07.0003.0008 1 N U en_US Tivoli Storage
Manager Server Common Messages - US English
[
*prereq tivoli.tsm.msg.en_US.server  3.7.0.0
%
/usr/lib/nls/msg/en_US 8864
/usr/lpp/SAVESPACE 8864
/usr/lib/objrepos 8
INSTWORK 56 16
%
%
%
IC26881  1 LABEL LIBVOLUME W/ OVERWRITE=YES CAN OVERWRITE THE LABELS OF
Ultrium  1 - Add support for IBM LTO Ultrium Devices
Drv_Rtry  1 - Improvement to mount retry processing for drive in use in a
  shared library
]
}


installp -l -d /aix43/tsm/aixsrv  output

  Fileset NameLevel I/U Q Content
  
  tivoli.tsm.devices.rte  3.7.3.8S  b usr,root
#   Tivoli Storage Manager Device Support runtime

  tivoli.tsm.msg.en_US.server 3.7.3.8S  N usr
#   Tivoli Storage Manager Server Common Messages - US E

  tivoli.tsm.server.rte42 3.7.3.8S  N usr,root
#   Tivoli Storage Manager Server Runtime

-
lslpp -l tivoli.tsm.msg.en_US.devices  output
-
  Fileset  Level  State  Description


Path: /usr/lib/objrepos
  tivoli.tsm.msg.en_US.devices
 3.7.3.0  COMMITTED  Tivoli Storage Manager
Devices
 SMIT Menus - US English

--
lslpp -l tivoli*  shows all filesets as 3.7.3.0  COMMITTED
--

Re: unavailable" or "destroyed".

[Richard Sims]

>AH HA...I have experienced the same thing. I chased this with support and so far
>I've gotten a working as designed answer...

So much for the design.  ;-)
Actually, the following players are involved in this scenario, and it may
be worth taking a look at relative levels:
  - TSM server
  - Operating system PTF level
  - SCSI device driver level (connection to tape drives)
  - Atape device driver
  - Atldd device driver
  - 3590 microcode level
  - 3494 microcode level
What appears in the operating system error log can be indicative.
In general, if the device-related code is at a higher level than the
host-related software that receives indications, the host-closer
software may fail to understand or misinterpret what the device-related
code is saying.
The 3494 itself has error logs, which your customer engineer can
inspect for anomalies - worth having him/her do the next time they
are in your shop, so save the date and time of the events.
With all the elements involved in the mix, trying to keep them all
compatible and happily interacting becomes a challenge, considering
all the other things we have to do.
Richard Sims, BU

Re: SELFTUNEXNSIZE

[Richard Sims]

>As I can change setting server Storage Options "SELFTUNEXNSIZE" to yes, =
>from the TSM command line?

Ricardo - Only the SETOPT command can dynamically set server options, and
  only some of them.  The 4.1 Admin Ref manual indicates that the
SETOPT command cannot set the one you want.  You can verify this in your
server via HELP SETOPT.  Looks like you'll have to manually update the
server options file and restart the server.
   Richard Sims, BU

Re: "Move media" vs. checkout

[Alex Paschal]

Checkout is when the volume will no longer be managed by the automated
library, ie, volumes going offsite.  If ADSM wants that volume, its mount
request fails.

move media is used to move media to an overflow location, ie, the "tape
room" because you don't have enough room in your library to contain all of
your primary pool volumes.  moved media is different than checked out media
in that ADSM can still ask for moved media to be mounted.  If ADSM wants one
of these volumes, it creates a mount request that shows up on the console
your operators are running to satisfy overflow mount requests.  See the
"query request" command.

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail

-Original Message-
From: Diana J. Noble [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 07, 2000 1:14 PM
To: [EMAIL PROTECTED]
Subject: "Move media" vs. checkout


I'm looking at moving our copypool tapes offsite.  We are not running
DRM.  I've been reading the archive of this list and it seems some people
use the adsm checkout command and others the Move media command to remove
the tapes from the library for offsite storage.  I've read up on both and
it seems the move media command is the right one for removing the tape from
the library and a checkin command to bring it back in.  Does anyone have
any comments on the checkout versus "move media" command that might help
explain their use?  Am I on the right track thinking the "move media"
command should be used?

SELFTUNEXNSIZE

[Ricardo Negrete]

Hi all !

As I can change setting server Storage Options "SELFTUNEXNSIZE" to yes, from the TSM 
command line?

tanks in advance

Ricardo Negrete Santelices
Cientec Integración S.A.-Chile
Fono : (56 2) 335 7107
e-mail: [EMAIL PROTECTED] 

Re: unavailable" or "destroyed".

[Shekhar Dhotre]

 Williams  ys it happened when  tape was not dissmounted that is  dismount
failure .
then i recycled TSm and got all above messages. unavailable" or
"destroyed". now i have updated all tapes/volumes
as readwrite , i am usning STK9710  ,but drives shows available state
tsm: TSM>q drive

Library Name  Drive NameDevice Type  DeviceON LINE
    ---    ---
STK9710   DRIVE1DLT  /dev/mt0  Yes
STK9710   DRIVE2DLT  /dev/mt1  Yes






"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/08/2000 12:44:04 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: unavailable" or "destroyed".

AH HA...I have experienced the same thing. I chased this with support and so far
I've gotten a working as designed answer...
My gut... you have a tape drive that may appear to be online, but it it isn't!
Are you 3494 with 3590s? mtlib -l/dev/lmcp0 -qM  (query mount...and compare this
with q mount in TSM)
If you have a tape mounted, then try a mtlib eject/demount   mtlib -l/dev/lmcp0
-f/dev/rmtx -d  (rmt for the 'invalid' mount).
Also a visual check may help...
check through your logs to see if you had a dismount failure (I think this was
the start to my 3 day demise).
Recycling my server cleared the problem.
I recreated the problem (messages below are only one flavor) by doing a rmdev -l
/dev/rmt0 AND TSM keeps this drive online.
even when it tries to access it and can't.
are you 3494shared yes???
If so, this is probably why development is saying it, so far, is working as
designed...
Call me if you like for further discussion
Thanks Tim Williams
(972) 376-7774





Shekhar Dhotre <[EMAIL PROTECTED]>
11/08/2000 10:09 AM

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

To:   [EMAIL PROTECTED]@SMTP@Exchange
cc:

Subject:  unavailable" or "destroyed".

Hi all ,
Today morning i restarted TSM ,cause  the DRM procedure backup stgpool
tapepool  copypool was not
completed . when the TSM server was coming up ,i saw
following messages,
   ,what could be the problem   all  volume access are
  offline or access mode is "unavailable" or
"destroyed"(.all these tapes MED403,MED404,MED545 whose accesss mode
   is unavailable or destroyed  belongs to  tapeool)



11/08/00   09:56:19  ANR2017I Administrator ADMIN issued command: BACKUP
  STGPOOL tapepool copypool
11/08/00   09:56:19  ANR1229W Volume MED403 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED404 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED545 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED575 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED576 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR0984I Process 3 for BACKUP STORAGE POOL started in the
  BACKGROUND at 09:56:19.

Thnaks in advance

Re: unavailable" or "destroyed".

[Shekhar Dhotre]

Thanks i did the following

tsm: TSM>update volume med403 access=readwrite
ANR2207I Volume MED403 updated.

tsm: TSM>update volume med404 access=readwrite
ANR2207I Volume MED404 updated.

tsm: TSM>update volume med545 access=readwrite
ANR2207I Volume MED545 updated.

tsm: TSM>update volume med575 access=readwrite
ANR2207I Volume MED575 updated.

tsm: TSM>update volume med576 access=readwrite
ANR2207I Volume MED576 updated.

tsm: TSM>audit library stk9710
ANS8003I Process number 10 started.




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/08/2000 12:10:08 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: unavailable" or "destroyed".

When TSM tries to mount a tape and the tape mount fails, it marks the tape
as "unavailable".
If you search back through your activity log, you can probably find when it
happened for each tape.

Usually this occurs because of a problem with the tape robot.
Once the mechanical problem is resolved, it's up to you to mark the tapes
available again.
You can do it through the GUI, or the cmd line:

update volume xx access=readwrite


> -Original Message-
> From: Shekhar Dhotre [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 08, 2000 11:09 AM
> To:   [EMAIL PROTECTED]
> Subject:  unavailable" or "destroyed".
>
> Hi all ,
> Today morning i restarted TSM ,cause  the DRM procedure backup stgpool
> tapepool  copypool was not
> completed . when the TSM server was coming up ,i
> saw
> following messages,
>,what could be the problem   all  volume access are
>   offline or access mode is "unavailable" or
> "destroyed"(.all these tapes MED403,MED404,MED545 whose accesss mode
>is unavailable or destroyed  belongs to  tapeool)
>
>
>
> 11/08/00   09:56:19  ANR2017I Administrator ADMIN issued command: BACKUP
>   STGPOOL tapepool copypool
> 11/08/00   09:56:19  ANR1229W Volume MED403 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED404 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED545 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED575 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED576 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR0984I Process 3 for BACKUP STORAGE POOL started in
> the
>   BACKGROUND at 09:56:19.
>
> Thnaks in advance

Re: unavailable" or "destroyed".

[Shekhar Dhotre]

Thanks a lot





"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/08/2000 12:10:08 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: unavailable" or "destroyed".

When TSM tries to mount a tape and the tape mount fails, it marks the tape
as "unavailable".
If you search back through your activity log, you can probably find when it
happened for each tape.

Usually this occurs because of a problem with the tape robot.
Once the mechanical problem is resolved, it's up to you to mark the tapes
available again.
You can do it through the GUI, or the cmd line:

update volume xx access=readwrite


> -Original Message-
> From: Shekhar Dhotre [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 08, 2000 11:09 AM
> To:   [EMAIL PROTECTED]
> Subject:  unavailable" or "destroyed".
>
> Hi all ,
> Today morning i restarted TSM ,cause  the DRM procedure backup stgpool
> tapepool  copypool was not
> completed . when the TSM server was coming up ,i
> saw
> following messages,
>,what could be the problem   all  volume access are
>   offline or access mode is "unavailable" or
> "destroyed"(.all these tapes MED403,MED404,MED545 whose accesss mode
>is unavailable or destroyed  belongs to  tapeool)
>
>
>
> 11/08/00   09:56:19  ANR2017I Administrator ADMIN issued command: BACKUP
>   STGPOOL tapepool copypool
> 11/08/00   09:56:19  ANR1229W Volume MED403 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED404 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED545 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED575 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED576 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR0984I Process 3 for BACKUP STORAGE POOL started in
> the
>   BACKGROUND at 09:56:19.
>
> Thnaks in advance

Re: unavailable" or "destroyed".

[Tim Williams]

AH HA...I have experienced the same thing. I chased this with support and so far
I've gotten a working as designed answer...
My gut... you have a tape drive that may appear to be online, but it it isn't!
Are you 3494 with 3590s? mtlib -l/dev/lmcp0 -qM  (query mount...and compare this
with q mount in TSM)
If you have a tape mounted, then try a mtlib eject/demount   mtlib -l/dev/lmcp0
-f/dev/rmtx -d  (rmt for the 'invalid' mount).
Also a visual check may help...
check through your logs to see if you had a dismount failure (I think this was
the start to my 3 day demise).
Recycling my server cleared the problem.
I recreated the problem (messages below are only one flavor) by doing a rmdev -l
/dev/rmt0 AND TSM keeps this drive online.
even when it tries to access it and can't.
are you 3494shared yes???
If so, this is probably why development is saying it, so far, is working as
designed...
Call me if you like for further discussion
Thanks Tim Williams
(972) 376-7774





Shekhar Dhotre <[EMAIL PROTECTED]>
11/08/2000 10:09 AM

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

To:   [EMAIL PROTECTED]@SMTP@Exchange
cc:

Subject:  unavailable" or "destroyed".

Hi all ,
Today morning i restarted TSM ,cause  the DRM procedure backup stgpool
tapepool  copypool was not
completed . when the TSM server was coming up ,i saw
following messages,
   ,what could be the problem   all  volume access are
  offline or access mode is "unavailable" or
"destroyed"(.all these tapes MED403,MED404,MED545 whose accesss mode
   is unavailable or destroyed  belongs to  tapeool)



11/08/00   09:56:19  ANR2017I Administrator ADMIN issued command: BACKUP
  STGPOOL tapepool copypool
11/08/00   09:56:19  ANR1229W Volume MED403 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED404 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED545 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED575 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED576 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR0984I Process 3 for BACKUP STORAGE POOL started in the
  BACKGROUND at 09:56:19.

Thnaks in advance

Re: unavailable" or "destroyed".

[Prather, Wanda]

When TSM tries to mount a tape and the tape mount fails, it marks the tape
as "unavailable".
If you search back through your activity log, you can probably find when it
happened for each tape.

Usually this occurs because of a problem with the tape robot.
Once the mechanical problem is resolved, it's up to you to mark the tapes
available again.
You can do it through the GUI, or the cmd line:

update volume xx access=readwrite


> -Original Message-
> From: Shekhar Dhotre [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 08, 2000 11:09 AM
> To:   [EMAIL PROTECTED]
> Subject:  unavailable" or "destroyed".
>
> Hi all ,
> Today morning i restarted TSM ,cause  the DRM procedure backup stgpool
> tapepool  copypool was not
> completed . when the TSM server was coming up ,i
> saw
> following messages,
>,what could be the problem   all  volume access are
>   offline or access mode is "unavailable" or
> "destroyed"(.all these tapes MED403,MED404,MED545 whose accesss mode
>is unavailable or destroyed  belongs to  tapeool)
>
>
>
> 11/08/00   09:56:19  ANR2017I Administrator ADMIN issued command: BACKUP
>   STGPOOL tapepool copypool
> 11/08/00   09:56:19  ANR1229W Volume MED403 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED404 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED545 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED575 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR1229W Volume MED576 cannot be backed up - volume
> is
>   offline or access mode is "unavailable" or
> "destroyed".
> 11/08/00   09:56:19  ANR0984I Process 3 for BACKUP STORAGE POOL started in
> the
>   BACKGROUND at 09:56:19.
>
> Thnaks in advance

unavailable" or "destroyed".

[Shekhar Dhotre]

Hi all ,
Today morning i restarted TSM ,cause  the DRM procedure backup stgpool
tapepool  copypool was not
completed . when the TSM server was coming up ,i saw
following messages,
   ,what could be the problem   all  volume access are
  offline or access mode is "unavailable" or
"destroyed"(.all these tapes MED403,MED404,MED545 whose accesss mode
   is unavailable or destroyed  belongs to  tapeool)



11/08/00   09:56:19  ANR2017I Administrator ADMIN issued command: BACKUP
  STGPOOL tapepool copypool
11/08/00   09:56:19  ANR1229W Volume MED403 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED404 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED545 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED575 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR1229W Volume MED576 cannot be backed up - volume is
  offline or access mode is "unavailable" or "destroyed".
11/08/00   09:56:19  ANR0984I Process 3 for BACKUP STORAGE POOL started in the
  BACKGROUND at 09:56:19.

Thnaks in advance

Re: SQL restore question

[Brian Nick]

John,

 Thanks for the info. and I'll look into the client sched log and the
server activity log. As far as your question regarding unload and reload
our DB is 21gb but we also question the performance of this function. We
were waiting for someone else to be brave enough to attempt this.

 Sorry I couldn't be more help and thanks again for your insight on my SQL
question.

 Thanks,
Brian

Brian L. Nick
System Programmer - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281




John Naylor
 cc:
Sent by: "ADSM: Dist Stor  Subject: Re: SQL restore 
question
Manager"
<[EMAIL PROTECTED]>


11/08/2000 10:44 AM
Please respond to "ADSM:
Dist Stor Manager"






Brian,
Have you got a perform trace set on the client.
If you have,  the Final Detailed Instrumentation statistics will give you a
breakdown
of where the time is being spent.
If not then the session stats either from the client schedule log or from a
query active on the
os390 server will give some info.
The data transfer time is basically the time not spent on the client, ie.
in the
network and on the
host tsm accessing the database and reading the data from the tape or disk.
The rest of the elapsed time is going to be time spent on the client mainly
in
writing out the data
This should at least give you a better idea where you need to look to
improve
the performance
 By the way I see you are an OS390  TSM 3.7.2 shop.
Any thoughts on my unload/reload question
John





Brian Nick <[EMAIL PROTECTED]> on 11/08/2000 02:46:01 PM

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

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Re: SQL restore question



Larry,

 We are talking about the restore of the flat file from the TSM server to
the SQL server.

 - Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281




Lawrence Clark
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
ATE.NY.US> cc:
Sent by: "ADSM: Dist   Subject: Re: SQL
restore
question
Stor Manager"
<[EMAIL PROTECTED]>


11/08/2000 09:23 AM
Please respond to
"ADSM: Dist Stor
Manager"






The restore of the 'flat' file to the server is TSM, the restore of the
flat file to MS-SQL is MS-SQL. Which is it that is slow?

>>> [EMAIL PROTECTED] 11/08/00 08:56AM >>>
Hello everyone,

 I was just contacted by one of our DBA's and I have a questions about SQL
restore. We are running TSM 3.7.3 on OS/390 2.9 and TSM client version
3.7.2. Please note that we are not using TDP for SQL. As explained to me by
our DBA there is a dump of the SQL data base taken every night and TSM
backs up the dump. By the way this is SQL 6.5 SP5a. The questions is
performance, we are currently attempting to restore the dump which is a
small file only 230mb. At the current rate it looks like the restore will
take about 2.5 hours to run. The dump file is being restored to its
original location.

 I realize that this question might be vague but it is all the information
that I have to offer at this time. Any help on improving the performance of
this SQL restore would be appreciated.

 Thanks,
Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281






**
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 and Southern Electric are trading names of
Scottish and Southern Energy Group.
**

Re: Unload /Reload timings and efficacy

[Sheelagh Treweek]

John,

I would be very reticent to use UNLOADDB/LOADDB (note : not DUMPDB,
UNLOADDB was new at 3.7) in order to resolve a performance problem.
This is a non-trivial undertaking.

I did it on two databases last year after having split the service
into two.  I was left with many GBs of database I could not utilise
in one DB and I wanted to regain space : that was very successful.
The other reason was to tidy up the larger DB after many years of
service and although the initial gain was impressive (about 30-40%)
the algorithm for space utilisation afterwards meant that it rapidly
expanded (and I don't believe that has been changed?).  I did some
DB performance measurements (my own crude metrics : EXPIRE INVENTORY
performance was one) and could discern no measurable improvement.

The platform base I did this on was AIX and the original DBs were
about 60GB.  The one that was really only 4GB after the split took
about 8 hours (on an RS6000/R40) and reduced to the 4GB.  The other
(really 60GB) took about 2 days (reducing to 40GB).

I think the likelyhood of it impacting on Netware restore performance
would be almost nil (my own honest opinion).  I'd be interested in
who advised you to do this?

I hope this helps ...

Sheelagh
--

Sheelagh Treweek
Oxford University Computing Services
Email: [EMAIL PROTECTED]
Phone: +44 (0)1865 273205 Fax:-273275

Re: SQL restore question

[John Naylor]

Brian,
Have you got a perform trace set on the client.
If you have,  the Final Detailed Instrumentation statistics will give you a
breakdown
of where the time is being spent.
If not then the session stats either from the client schedule log or from a
query active on the
os390 server will give some info.
The data transfer time is basically the time not spent on the client, ie. in the
network and on the
host tsm accessing the database and reading the data from the tape or disk.
The rest of the elapsed time is going to be time spent on the client mainly in
writing out the data
This should at least give you a better idea where you need to look to improve
the performance
 By the way I see you are an OS390  TSM 3.7.2 shop.
Any thoughts on my unload/reload question
John





Brian Nick <[EMAIL PROTECTED]> on 11/08/2000 02:46:01 PM

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

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Re: SQL restore question



Larry,

 We are talking about the restore of the flat file from the TSM server to
the SQL server.

 - Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281




Lawrence Clark
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
ATE.NY.US> cc:
Sent by: "ADSM: Dist   Subject: Re: SQL restore
question
Stor Manager"
<[EMAIL PROTECTED]>


11/08/2000 09:23 AM
Please respond to
"ADSM: Dist Stor
Manager"






The restore of the 'flat' file to the server is TSM, the restore of the
flat file to MS-SQL is MS-SQL. Which is it that is slow?

>>> [EMAIL PROTECTED] 11/08/00 08:56AM >>>
Hello everyone,

 I was just contacted by one of our DBA's and I have a questions about SQL
restore. We are running TSM 3.7.3 on OS/390 2.9 and TSM client version
3.7.2. Please note that we are not using TDP for SQL. As explained to me by
our DBA there is a dump of the SQL data base taken every night and TSM
backs up the dump. By the way this is SQL 6.5 SP5a. The questions is
performance, we are currently attempting to restore the dump which is a
small file only 230mb. At the current rate it looks like the restore will
take about 2.5 hours to run. The dump file is being restored to its
original location.

 I realize that this question might be vague but it is all the information
that I have to offer at this time. Any help on improving the performance of
this SQL restore would be appreciated.

 Thanks,
Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281






**
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 and Southern Electric are trading names of
Scottish and Southern Energy Group.
**

Re: Library error.

[Prather, Wanda]

Look in the AIX errpt.
(type in errpt | pg, or
 errpt -a | pg   to get details).

You will probably find some hardware errors on that drive.
The errpt -a will have sense information, you can send it to your STK
CE/specialist for review.

Also look at the tail of the acsls error log:

su - acsss (or log on as acssa)
cd log
tail -100 acsss_event.log

They may want to see those errors as well.


> -Original Message-
> From: Shekhar Dhotre [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 08, 2000 9:32 AM
> To:   [EMAIL PROTECTED]
> Subject:  Library error.
>
>  Hi all , STk9710 , ACSLS 5.3.0 , TSM 3.7.2 on AIX 4.3.3.0
>   i am getting following errors ?anybody  had this problem
> ?
>
>
> DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
> 11/08/00   08:47:21  ANRD mmslib.c(6242): Entry not found in activity
> list;
>   lib=STK9710, vol=MED597.
> 11/08/00   08:47:21  ANR8469E Dismount of DLT volume MED597 from drive
> DRIVE1
>   (/dev/mt0) in library STK9710 failed.
> 11/08/00   08:48:21  ANR8311E An I/O error occurred while accessing drive
>   DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
> 11/08/00   08:48:21  ANRD mmslib.c(6242): Entry not found in activity
> list;
>   lib=STK9710, vol=MED597.
> 11/08/00   08:48:21  ANR8469E Dismount of DLT volume MED597 from drive
> DRIVE1
>   (/dev/mt0) in library STK9710 failed.
> 11/08/00   08:49:21  ANR8311E An I/O error occurred while accessing drive
>   DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
> 11/08/00   08:49:21  ANRD mmslib.c(6242): Entry not found in activity
> list;
>   lib=STK9710, vol=MED597.
> 11/08/00   08:49:21  ANR8469E Dismount of DLT volume MED597 from drive
> DRIVE1
>   (/dev/mt0) in library STK9710 failed.
> 11/08/00   08:50:21  ANR8311E An I/O error occurred while accessing drive
>   DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
> 11/08/00   08:50:21  ANRD mmslib.c(6242): Entry not found in activity
> list;
>   lib=STK9710, vol=MED597.
> 11/08/00   08:50:21  ANR8469E Dismount of DLT volume MED597 from drive
> DRIVE1
> more...   ( to continue, 'C' to cancel)
>from ACSLS all drives are available .
>
>  run  1440/00/00/0   0/0
> 0/0
> ACSSA> q dri all
> 2000-11-08 09:28:11   Drive Status
>  Identifier   State   Status  Volume Type
>0, 0, 2, 0 online  available  DLT7000
>0, 0, 2, 1 online  available  DLT7000
>0, 0, 2, 2 online  available  DLT7000
>0, 0, 2, 3 online  available  DLT7000
>0, 0, 2, 4 online  in use  MED581 DLT7000
>0, 0, 2, 5 online  available  DLT7000
> ACSSA>

Re: BACKUPSET DELETE PROBLEM

[Maria Paz Gimeno]

Ruddy,
Your workaround did not work for me.
When I deleted the backup set the tapes were already in the library, but
they remained in private state,
and the command to change to scratch didn't succeed.
The tape wan't change status because the volhistory entry was not removed.
Could you change the status of the tapes from private to scratch?
Thanks
Maria

- Original Message -
From: Ruddy STOUDER <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 08, 2000 3:34 PM
Subject: Re: BACKUPSET DELETE PROBLEM


> The work-around I found in the meantime is write a script which is
> looking what backupset will expire, to call the tape back from off-site,
> check it in with PRIVATE status and then make the backupset expire. That
> way, it is ok but the MAIN condition is to have the tape in the library
> before running the expire process.
>
> --
> From: Maria Paz Gimeno
> To: [EMAIL PROTECTED]
> Sent: 11/07/2000 8:47:14 PM
> Subject: Re: BACKUPSET DELETE PROBLEM
>
> M have not yet installed 3.7.4, but sure I will write to the list with
> the
> results.
> Thanks very much Richard for your help it is invaluable.
> Best regards
> Maria
>
> - Original Message -
> From: Richard Sims <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 07, 2000 5:04 PM
> Subject: Re: BACKUPSET DELETE PROBLEM
>
>
> > >We have the same problem overhere.  I think it has to be a bug
> because
> > >several other persons are having
> > >this problem too.  I hope there is someone outthere with a solution.
> >
> > As mentioned last week, the 3.7.4 server README notes the APAR
> >  IC27123  BACKUPSETS DON'T EXPIRE PROPERLY
> > which may address the problem.  We need a 3.7.4 adopter to post to
> > the List as to whether that level fixes the noted problems.
> >  Richard Sims, BU

Re: Client ver 3.7.2 - no SA software

[Andy Raibeck]

Did you do a "Typical" or "Custom" install?

Beginning with the 3.7 client, the Administrative command line interface is
no longer part of the typical install in order to bring it in line with the
meaning of "typical". The rationale is that the typical TSM user is an end
user who does not require this capability.

If you run a custom install, you can select the Admin component for
install.

Regards,

Andy

Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."


Mike Glassman - Admin <[EMAIL PROTECTED]> on 11/08/2000 02:45:42

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

To:   [EMAIL PROTECTED]
cc:(bcc: Andrew Raibeck/Tivoli Systems)
Subject:  Client ver 3.7.2 - no SA software



All,

I just downloaded the TSM client for Windows (Intell) version as above, and
I noticed after the install, that even tho I told it I wanted to have the
administrative software installed as well, that it does not install and
administrative client.

Since I need this Administrative capability, anyone have any ideas how I
can
get at it ? Or what to install ?

I need the same type of Administrative capabilities as were available in
the
3.1.08 client version.

Thanks,

Mike Glassman
System & Security Admin
Israeli Airports Authority
Ben-Gurion Airport
http://www.ben-gurion-airport.co.il

Tel : 972-3-9710785
Fax : 972-3-9710939
Email : [EMAIL PROTECTED]

Usage of this email address or any email address at iaa.gov.il for the
purpose of sales pitches, SPAM or any other such unwanted garbage, is
illegal, and any person, whether corporate or alone doing so, will be
prosecuted to the fullest possible extent.

Re: Client ver 3.7.2 - no SA software

[Gill, Geoffrey L.]

Mike,

The Admin client is no longer installed by default as it was in the 3.1.08
version. If you do a custom install you can select to install it separately.


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


>-Original Message-
>From: Mike Glassman - Admin [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, November 08, 2000 1:46 AM
>To: [EMAIL PROTECTED]
>Subject: Client ver 3.7.2 - no SA software
>Importance: High
>
>
>All,
>
>I just downloaded the TSM client for Windows (Intell) version
>as above, and
>I noticed after the install, that even tho I told it I wanted
>to have the
>administrative software installed as well, that it does not install and
>administrative client.
>
>Since I need this Administrative capability, anyone have any
>ideas how I can
>get at it ? Or what to install ?
>
>I need the same type of Administrative capabilities as were
>available in the
>3.1.08 client version.
>
>Thanks,
>
>Mike Glassman
>System & Security Admin
>Israeli Airports Authority
>Ben-Gurion Airport
>http://www.ben-gurion-airport.co.il
>
>Tel : 972-3-9710785
>Fax : 972-3-9710939
>Email : [EMAIL PROTECTED]
>
>Usage of this email address or any email address at iaa.gov.il for the
>purpose of sales pitches, SPAM or any other such unwanted garbage, is
>illegal, and any person, whether corporate or alone doing so, will be
>prosecuted to the fullest possible extent.
>

Re: SQL restore question

[Jerry Kube]

Brian,

My experience with SQL database has been to use the TSM SQL Agent.   The
performance is far greater than a flat file restore.  To restore a database
that is 1 GB takes about 15 min in our environment using TSM 3.7 on NT
direct from tape.

If a speedy restore is of importance the agent is the way to go.  The Flat
File backup is a good secondary backup measure.

Hope this helps..

Jerry Kube
Senior Technical Analyst
Ceridian Canada Ltd.
[EMAIL PROTECTED]






Brian Nick <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2000/11/08 07:56:10 AM

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

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


To:   [EMAIL PROTECTED]
cc:

Subject:  SQL restore question


Hello everyone,

 I was just contacted by one of our DBA's and I have a questions about SQL
restore. We are running TSM 3.7.3 on OS/390 2.9 and TSM client version
3.7.2. Please note that we are not using TDP for SQL. As explained to me by
our DBA there is a dump of the SQL data base taken every night and TSM
backs up the dump. By the way this is SQL 6.5 SP5a. The questions is
performance, we are currently attempting to restore the dump which is a
small file only 230mb. At the current rate it looks like the restore will
take about 2.5 hours to run. The dump file is being restored to its
original location.

 I realize that this question might be vague but it is all the information
that I have to offer at this time. Any help on improving the performance of
this SQL restore would be appreciated.

 Thanks,
Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281

Re: SQL restore question

[Brian Nick]

Larry,

 We are talking about the restore of the flat file from the TSM server to
the SQL server.

 - Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281




Lawrence Clark
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
ATE.NY.US> cc:
Sent by: "ADSM: Dist   Subject: Re: SQL restore 
question
Stor Manager"
<[EMAIL PROTECTED]>


11/08/2000 09:23 AM
Please respond to
"ADSM: Dist Stor
Manager"






The restore of the 'flat' file to the server is TSM, the restore of the
flat file to MS-SQL is MS-SQL. Which is it that is slow?

>>> [EMAIL PROTECTED] 11/08/00 08:56AM >>>
Hello everyone,

 I was just contacted by one of our DBA's and I have a questions about SQL
restore. We are running TSM 3.7.3 on OS/390 2.9 and TSM client version
3.7.2. Please note that we are not using TDP for SQL. As explained to me by
our DBA there is a dump of the SQL data base taken every night and TSM
backs up the dump. By the way this is SQL 6.5 SP5a. The questions is
performance, we are currently attempting to restore the dump which is a
small file only 230mb. At the current rate it looks like the restore will
take about 2.5 hours to run. The dump file is being restored to its
original location.

 I realize that this question might be vague but it is all the information
that I have to offer at this time. Any help on improving the performance of
this SQL restore would be appreciated.

 Thanks,
Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281

Re: Number of bytes backed up

[John Naylor]

First the bytes transferred should be reasonably close to the amount backed up.
If not, sounds like you are getting too many retries and you should look at that
as
otherwise you are putting unnecesary load on your network.
Are you interested for specific clients or in the overall total.
If specific clients you might compare query occupancy run after previous days
expiration
with query occupancy run after the backup but before todays expiration.
For the overall total then the easiest way is to have a disk storage pool/s
large enough to
hold a nights backups. Then if you clear that pool out to tape daily, the figure
you want will be
the disk pool utilisation before the migration






"Ulbrink, Birger" <[EMAIL PROTECTED]> on 11/07/2000 10:37:37 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Number of bytes backed up



**
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 and Southern Electric are trading names of
Scottish and Southern Energy Group.
**



Where do I see the number of bytes backed up?

At the end of the schedule log (and in the accounting log) the number of
bytes transferred are shown, but this does not match the filesize in NT. Not
even taking the "objects compressed by" into the calculation!



Med venlig hilsen / Kind regards
Birger Ulbrink
Netværksadministrator / Network administration

METRO Cash & Carry ApS.
IT afdelingen /  IT department
Ejby Industrivej 111
DK 2600 Glostrup

Tel  +45 43467700
Tel  +45 43467819 (direct)
Fax +45 43452321
Email   [EMAIL PROTECTED] 

Library error.

[Shekhar Dhotre]

 Hi all , STk9710 , ACSLS 5.3.0 , TSM 3.7.2 on AIX 4.3.3.0
  i am getting following errors ?anybody  had this problem ?


DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
11/08/00   08:47:21  ANRD mmslib.c(6242): Entry not found in activity list;
  lib=STK9710, vol=MED597.
11/08/00   08:47:21  ANR8469E Dismount of DLT volume MED597 from drive DRIVE1
  (/dev/mt0) in library STK9710 failed.
11/08/00   08:48:21  ANR8311E An I/O error occurred while accessing drive
  DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
11/08/00   08:48:21  ANRD mmslib.c(6242): Entry not found in activity list;
  lib=STK9710, vol=MED597.
11/08/00   08:48:21  ANR8469E Dismount of DLT volume MED597 from drive DRIVE1
  (/dev/mt0) in library STK9710 failed.
11/08/00   08:49:21  ANR8311E An I/O error occurred while accessing drive
  DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
11/08/00   08:49:21  ANRD mmslib.c(6242): Entry not found in activity list;
  lib=STK9710, vol=MED597.
11/08/00   08:49:21  ANR8469E Dismount of DLT volume MED597 from drive DRIVE1
  (/dev/mt0) in library STK9710 failed.
11/08/00   08:50:21  ANR8311E An I/O error occurred while accessing drive
  DRIVE1 (/dev/mt0) for OFFL operation, errno = 9.
11/08/00   08:50:21  ANRD mmslib.c(6242): Entry not found in activity list;
  lib=STK9710, vol=MED597.
11/08/00   08:50:21  ANR8469E Dismount of DLT volume MED597 from drive DRIVE1
more...   ( to continue, 'C' to cancel)
   from ACSLS all drives are available .

 run  1440/00/00/0   0/00/0
ACSSA> q dri all
2000-11-08 09:28:11   Drive Status
 Identifier   State   Status  Volume Type
   0, 0, 2, 0 online  available  DLT7000
   0, 0, 2, 1 online  available  DLT7000
   0, 0, 2, 2 online  available  DLT7000
   0, 0, 2, 3 online  available  DLT7000
   0, 0, 2, 4 online  in use  MED581 DLT7000
   0, 0, 2, 5 online  available  DLT7000
ACSSA>

Re: Client ver 3.7.2 - no SA software

[Lawrence Clark]

You can  still use the 3.1 Admin interface with 3.7.

>>> [EMAIL PROTECTED] 11/08/00 04:45AM >>>
All,

I just downloaded the TSM client for Windows (Intell) version as above, and
I noticed after the install, that even tho I told it I wanted to have the
administrative software installed as well, that it does not install and
administrative client.

Since I need this Administrative capability, anyone have any ideas how I can
get at it ? Or what to install ?

I need the same type of Administrative capabilities as were available in the
3.1.08 client version.

Thanks,

Mike Glassman
System & Security Admin
Israeli Airports Authority
Ben-Gurion Airport
http://www.ben-gurion-airport.co.il 

Tel : 972-3-9710785
Fax : 972-3-9710939
Email : [EMAIL PROTECTED] 

Usage of this email address or any email address at iaa.gov.il for the
purpose of sales pitches, SPAM or any other such unwanted garbage, is
illegal, and any person, whether corporate or alone doing so, will be
prosecuted to the fullest possible extent.

Re: BACKUPSET DELETE PROBLEM

[Ruddy STOUDER]

 The work-around I found in the meantime is write a script which is
looking what backupset will expire, to call the tape back from off-site,
check it in with PRIVATE status and then make the backupset expire. That
way, it is ok but the MAIN condition is to have the tape in the library
before running the expire process.

--
From: Maria Paz Gimeno
To: [EMAIL PROTECTED]
Sent: 11/07/2000 8:47:14 PM
Subject: Re: BACKUPSET DELETE PROBLEM

M have not yet installed 3.7.4, but sure I will write to the list with
the
results.
Thanks very much Richard for your help it is invaluable.
Best regards
Maria

- Original Message -
From: Richard Sims <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 07, 2000 5:04 PM
Subject: Re: BACKUPSET DELETE PROBLEM


> >We have the same problem overhere.  I think it has to be a bug
because
> >several other persons are having
> >this problem too.  I hope there is someone outthere with a solution.
>
> As mentioned last week, the 3.7.4 server README notes the APAR
>  IC27123  BACKUPSETS DON'T EXPIRE PROPERLY
> which may address the problem.  We need a 3.7.4 adopter to post to
> the List as to whether that level fixes the noted problems.
>  Richard Sims, BU

Re: SQL restore question

[Lawrence Clark]

The restore of the 'flat' file to the server is TSM, the restore of the flat file to 
MS-SQL is MS-SQL. Which is it that is slow?

>>> [EMAIL PROTECTED] 11/08/00 08:56AM >>>
Hello everyone,

 I was just contacted by one of our DBA's and I have a questions about SQL
restore. We are running TSM 3.7.3 on OS/390 2.9 and TSM client version
3.7.2. Please note that we are not using TDP for SQL. As explained to me by
our DBA there is a dump of the SQL data base taken every night and TSM
backs up the dump. By the way this is SQL 6.5 SP5a. The questions is
performance, we are currently attempting to restore the dump which is a
small file only 230mb. At the current rate it looks like the restore will
take about 2.5 hours to run. The dump file is being restored to its
original location.

 I realize that this question might be vague but it is all the information
that I have to offer at this time. Any help on improving the performance of
this SQL restore would be appreciated.

 Thanks,
Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED] 
PHONE:   (860)403-2281

Re: Unload /Reload timings and efficacy

[John Naylor]

Reinhard,
I think the process may be different or improved under 3.7
I have tried it on our much smaller development TSM database
where I saw :-

Before, the load/reload Total Usable Pages: 607,232   Used Pages: 304,812
After,   the load/reload   Total Usable Pages: 608,256Used Pages: 177,578

So the compress was significant and in this case the unload took 9 minutes and
the
load 15 minutes,  and that is what I based my 6 hour estimate on, but it is a
lot smaller than my production TSM and I was not sure how safe it was to
extrapolate from such a small database.
As far as the performance gain, I must admit I tend to agree with you, certainly
for backups and
the normal small restores. I am not a database expert, but I suppose it may be
different for large restores.
Any database or os390 gurus out there ?
John





Reinhard Mersch <[EMAIL PROTECTED]> on 11/08/2000 01:32:46 PM

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

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Re: Unload /Reload timings and efficacy



John,

from my experience with ADSM 3.1.2 on AIX, I do not think that it can
be done within 12 hours. The DUMPDB is quite fast, but the LOADDB takes
a lot of time (more in the order of days than hours). And it may require
much more space than the original 18 GB.

But again, this is my ADSM 3.1.2 experience. Perhaps things are totally
different with TSM 3.7. I would love to hear that they are, but nobody could
assure me so far.

Even more, I tend to doubt the wisdom of that recommendation. I never
heard, that performance problems could be resolved by a DB reorganization.

Reinhard

John Naylor writes:
 > Hi,
 > I have been recommended a compress of the database ie. unload/reload as a
cure
 > for
 > slow restores with large Novell data servers.
 > Has anybody been through this,  and can confirm my estimate of 6 hours approx
 > for the unload reload part of thr process.
 > We are OS390, TSM 3.7.20.0
 > The database is 84.5% occupied of 18.1gb   8 logical volumes ie :
 > Total Usable Pages: 4,764,672  Used Pages: 4,027,026
 >  Also any feelings on whether this is likely to make a real impact on the
 > database access
 > element of the restores.
 > Thanks, John
 >
 > Has anybody been there, done it, got the figures.
 > I am looking for a nice warm feeling. I cannot have TSM unavailable for more
 > than 12 hours
 > max.
 > Thanks
 >
 >
 > **
 > 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 and Southern Electric are trading names of
 > Scottish and Southern Energy Group.
 > **

--
Reinhard MerschWestfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany  Tel: +49(251)83-31583
E-Mail: [EMAIL PROTECTED]   Fax: +49(251)83-31653






**
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 and Southern Electric are trading names of
Scottish and Southern Energy Group.
**

SQL restore question

[Brian Nick]

Hello everyone,

 I was just contacted by one of our DBA's and I have a questions about SQL
restore. We are running TSM 3.7.3 on OS/390 2.9 and TSM client version
3.7.2. Please note that we are not using TDP for SQL. As explained to me by
our DBA there is a dump of the SQL data base taken every night and TSM
backs up the dump. By the way this is SQL 6.5 SP5a. The questions is
performance, we are currently attempting to restore the dump which is a
small file only 230mb. At the current rate it looks like the restore will
take about 2.5 hours to run. The dump file is being restored to its
original location.

 I realize that this question might be vague but it is all the information
that I have to offer at this time. Any help on improving the performance of
this SQL restore would be appreciated.

 Thanks,
Brian


Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281

VS: Number of bytes backed up

[Ulbrink, Birger]

Sample from the activity log:

ANE4952I (Session: 3299, Node: KOPSAPP1) Total number of objects inspected:
55,892
ANE4954I (Session: 3299, Node: KOPSAPP1) Total number of objects backed up:
365
ANE4958I (Session: 3299, Node: KOPSAPP1) Total number of objects updated: 0
ANE4960I (Session: 3299, Node: KOPSAPP1) Total number of objects rebound: 0
ANE4957I (Session: 3299, Node: KOPSAPP1) Total number of objects deleted:
150
ANE4959I (Session: 3299, Node: KOPSAPP1) Total number of objects failed: 12
ANE4961I (Session: 3299, Node: KOPSAPP1) Total number of bytes transferred:
12.15 GB
ANE4963I (Session: 3299, Node: KOPSAPP1) Data transfer time: 2,241.35 sec
ANE4966I (Session: 3299, Node: KOPSAPP1) Network data transfer rate:
5,684.97 KB/sec
ANE4967I (Session: 3299, Node: KOPSAPP1) Aggregate data transfer rate:
1,311.44 KB/sec
ANE4968I (Session: 3299, Node: KOPSAPP1) Objects compressed by: 63%
ANE4964I (Session: 3299, Node: KOPSAPP1) Elapsed processing time: 02:41:56


NT filesize = 30GB


/Regards,
Birger Ulbrink


-Oprindelig meddelelse-
Fra:Richard Sims [mailto:[EMAIL PROTECTED]]
Sendt:  7. november 2000 13:23
Emne:   Re: Number of bytes backed up

>Where do I see the number of bytes backed up?
>
>At the end of the schedule log (and in the accounting log) the number
>of bytes transferred are shown, but this does not match the filesize
>in NT. Not even taking the "objects compressed by" into the calculation!

Do you see more? Less?  Please cite an example.
Here are my notes on the number, from
http://people.bu.edu/rbs/ADSM.QuickFacts:
Total number of bytes transferred:  In the summary statistics from an
Archive or Backup operation, or the Activity Log message ANE4961I which
records the client operation stats.  Note that the number will probably be
less than the sum reflected by including the numbers shown on "Directory-->"
lines of the report, in that *SM stores only the name and attributes of
directories.  Note also that Retry operations may inflate this value, if
they result in the file being re-sent to the server, as in the case of the
beginning of a direct-to-tape backup, when the tape is not yet mounted.
Richard Sims, BU

Re: Unload /Reload timings and efficacy

[Reinhard Mersch]

John,

from my experience with ADSM 3.1.2 on AIX, I do not think that it can
be done within 12 hours. The DUMPDB is quite fast, but the LOADDB takes
a lot of time (more in the order of days than hours). And it may require
much more space than the original 18 GB.

But again, this is my ADSM 3.1.2 experience. Perhaps things are totally
different with TSM 3.7. I would love to hear that they are, but nobody could
assure me so far.

Even more, I tend to doubt the wisdom of that recommendation. I never
heard, that performance problems could be resolved by a DB reorganization.

Reinhard

John Naylor writes:
 > Hi,
 > I have been recommended a compress of the database ie. unload/reload as a cure
 > for
 > slow restores with large Novell data servers.
 > Has anybody been through this,  and can confirm my estimate of 6 hours approx
 > for the unload reload part of thr process.
 > We are OS390, TSM 3.7.20.0
 > The database is 84.5% occupied of 18.1gb   8 logical volumes ie :
 > Total Usable Pages: 4,764,672  Used Pages: 4,027,026
 >  Also any feelings on whether this is likely to make a real impact on the
 > database access
 > element of the restores.
 > Thanks, John
 >
 > Has anybody been there, done it, got the figures.
 > I am looking for a nice warm feeling. I cannot have TSM unavailable for more
 > than 12 hours
 > max.
 > Thanks
 >
 >
 > **
 > 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 and Southern Electric are trading names of
 > Scottish and Southern Energy Group.
 > **

--
Reinhard MerschWestfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany  Tel: +49(251)83-31583
E-Mail: [EMAIL PROTECTED]   Fax: +49(251)83-31653

Unload /Reload timings and efficacy

[John Naylor]

Hi,
I have been recommended a compress of the database ie. unload/reload as a cure
for
slow restores with large Novell data servers.
Has anybody been through this,  and can confirm my estimate of 6 hours approx
for the unload reload part of thr process.
We are OS390, TSM 3.7.20.0
The database is 84.5% occupied of 18.1gb   8 logical volumes ie :
Total Usable Pages: 4,764,672  Used Pages: 4,027,026
 Also any feelings on whether this is likely to make a real impact on the
database access
element of the restores.
Thanks, John

Has anybody been there, done it, got the figures.
I am looking for a nice warm feeling. I cannot have TSM unavailable for more
than 12 hours
max.
Thanks


**
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 and Southern Electric are trading names of
Scottish and Southern Energy Group.
**

Re: How to reclaim with only 1 drive

[Hans H. Röhr]

Hello,

in short writing: we defined a "sequential" storage pool as
a disk pool and use it as a reclamation storage pool for our
one-drive-library, works so far...

*---*
*
* Hans H. Roehr
* Akademie fuer DV
* Danziger Strasse 6
* D-71034 Boeblingen
*
* [EMAIL PROTECTED]
*
* Telefon 07031-627-0(Sekretariat)
*  -143  (direkt)
* Fax 07031-627-101
*---*

ameerul madzali schrieb:
>
> Hi friends,
> Has anyone with the experience with doing reclaimation with only 1 drive on
> the 3570? How should it be done?
>
> regards
> Ameerul
> _
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.

--

Client ver 3.7.2 - no SA software

[Mike Glassman - Admin]

All,

I just downloaded the TSM client for Windows (Intell) version as above, and
I noticed after the install, that even tho I told it I wanted to have the
administrative software installed as well, that it does not install and
administrative client.

Since I need this Administrative capability, anyone have any ideas how I can
get at it ? Or what to install ?

I need the same type of Administrative capabilities as were available in the
3.1.08 client version.

Thanks,

Mike Glassman
System & Security Admin
Israeli Airports Authority
Ben-Gurion Airport
http://www.ben-gurion-airport.co.il

Tel : 972-3-9710785
Fax : 972-3-9710939
Email : [EMAIL PROTECTED]

Usage of this email address or any email address at iaa.gov.il for the
purpose of sales pitches, SPAM or any other such unwanted garbage, is
illegal, and any person, whether corporate or alone doing so, will be
prosecuted to the fullest possible extent.

Re: "Move media" vs. checkout

[Maria Paz Gimeno]

I use MOVE MEDIA for this operation both ways, out and in the library.
With CHECKOUT  you have to provide the volume labels of the tapes you want
to remove from the library, while with "move media" you can select by
stgpool. I am not sure if the "checkout" changes the access to offsite but
"Move media" creates a file with the volume label of the tapes that
processes, and you can afterwards run a command to perform an update of the
volumes with access=offsite.
The only problem is that, what the command creates is a macro and can only
be scheduled by a cron job,( my system is UNIX.)
The macro can not be scheduled by TSM, not included in a script. It has to
run from the command line.
Regards
Maria

- Original Message -
From: Reiner Sauer <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 08, 2000 8:26 AM
Subject: Antw: "Move media" vs. checkout


I've learned that to get the tape out and set in the db to offsite, is to
use the command checkout and the tape get offsite. Now the tape is not
availiable fpr the library. To get the tape in you should use the commands
checkin and update volume.

>>> [EMAIL PROTECTED] 7.11.2000 22:14:11 >>>
I'm looking at moving our copypool tapes offsite.  We are not running
DRM.  I've been reading the archive of this list and it seems some people
use the adsm checkout command and others the Move media command to remove
the tapes from the library for offsite storage.  I've read up on both and
it seems the move media command is the right one for removing the tape from
the library and a checkin command to bring it back in.  Does anyone have
any comments on the checkout versus "move media" command that might help
explain their use?  Am I on the right track thinking the "move media"
command should be used?

Migrating from ADSM 3.1.0.6 to TSM 3.7 or 4.1

[Stephanie canon]

Hi,

We are going to migrate our OS/390 ADSM Server ver 3.1.0.6 to OS/390 TSM
server ver 3.7 or 4.1.
Does anybody know where I can find documentation about this upgrade, on how
to process, warnings, ... ?


Thanks for your help



---
Stéphanie Canon
[EMAIL PROTECTED]
Tel : (02 38 74) 59 41

Upgrade Serverlevel 3.1.2.16

[Michael Donabauer]

On the FTP Servers of ftp.tivoli.com or service.boulder.ibm.com are only Levelupgrades 
of 3.7 and 4.1. Are there any Upgrades available for 3.1? I need it for long file 
names for Novell Fileservers...

thanx Mike