DB2 restore takes long

[Crawford, Lindy]

Hi TSMers,
Could some please assist me. I did a restore yesterday, started it 8:13am
and it only completed at 21:04 pm. This for the environment that we work
with it is unacceptable in terms of response. My client  - node is as
follows:_
TSM 4.2
DB2 7.2
SAP R3 4.6c
Database size is : 48gigs
What can I do to make this process faster. The reason why I am concerned is
that my backup only takes 1h30mins, so the most time it took I would have
expected it to be 2 or 3hours.

Please help!!!



> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> *  +27-31-3642185
 <<...OLE_Obj...>>  +27-31-3642946
 [EMAIL PROTECTED] 





WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm

Re: Licensing

[Ofer vaknin]

Managed Libraries - when TSM backup to a large library (exm. LTO library up
to 40 slots and/or 3 drives u do not need this license above u need !, u can
see the supported library in the web and indication if u need this license
for a particular library or not !)

Library Sharing - when u connect TSM to backup in SAN u need this license
for 1. sharing the library with several TSM server in SAN 2. LAN-FREE &
SERVER-FREE backup !

Regards
Ofer Vaknin

Tivoli Products Manager
CDD - I S R A E L

-Original Message-
From: Mark D. Rodriguez [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 5:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Licensing


Nick Rutherford wrote:

>Hello
> can somebody please clarrify the difference between the license for
>'Managed Libraries' and the license for 'Library Sharing'.
>Many thanks,
>Nick Rutherford
>
>
>*
>This e-mail is confidential and intended solely for the use of the
>individual to whom it is addressed.  Any views or opinions presented
>are solely those of the author and do not necessarily represent
>those of Honda of the UK Manufacturing Ltd.
>
>If you are not the intended recipient please notify the sender
>immediately by return e-mail and then delete this message from your
>system.  Also be advised that any use, disclosure, forwarding,
>printing or copying of this e-mail if sent in error is strictly
>prohibited.  Thank you for your co-operation.
>*
>
>
Hi Nick,

'Library Sharing" license is just what it sounds like if youare sharing
a single library, say between TSM servers.

 'Managed Library" is need for the those libraries that are listed as
requiring the *A/E* feature on the Tivoli supported device page (
http://www.tivoli.com/support/storage_mgr/requirements.html ).
 Generally this is for libraries with more than 3 drives and/or more
than 40 slots.  There are some exception so just go by whether it has
the *A/E* in the notes section, if so then you must purchase the
'Managed Library" license as well.

I hope that clears it up for you.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.


===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE

===


**
This email 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 email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Re: DB2 restore takes long

[MUSTAFA BAYTAR]

Hi Lindy ,
We have SAP R3 4.B with DB2 database running on aix 4.3.3 and
we had similar problem about 1.5 years ago.
our db2 size was 120 GB and when we started database restore its took  nearly  12 
hours to create
db2 conteiners and 4 hours to restore them.
after that we have moved filesystem conteiners to rowdevices conteiners and distrubute 
them over
diferent disks .
now our db2 size is 420 GB and restore take approximately 4 hours.



  "Crawford,
  Lindy"   To:  [EMAIL PROTECTED]
  Subject: DB2 restore takes long
  Sent by: "ADSM:
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  T.EDU>


  15.08.2002 10:26
  Please respond
  to "ADSM: Dist
  Stor Manager"





Hi TSMers,
Could some please assist me. I did a restore yesterday, started it 8:13am
and it only completed at 21:04 pm. This for the environment that we work
with it is unacceptable in terms of response. My client  - node is as
follows:_
TSM 4.2
DB2 7.2
SAP R3 4.6c
Database size is : 48gigs
What can I do to make this process faster. The reason why I am concerned is
that my backup only takes 1h30mins, so the most time it took I would have
expected it to be 2 or 3hours.

Please help!!!



> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> *  +27-31-3642185
 <<...OLE_Obj...>>  +27-31-3642946
 [EMAIL PROTECTED] 





WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm

Re: Win2k system state restore

[Frost, Dave]

Jim,

Thanks for that.  But...

A lookup in the tivoli/support/knowledgebase/ for apar ic34015 returns 0
records.  Nor is it documented in the readmes for the 4.2 or 5.1 client in
"maintenance" or "patches" at boulder.

It would seem that this apar is not publically available.


  regards,

-=Dave=-
--
+44 (0)20 7608 7140

Know thyself.  If you need help, call the C.I.A.



-Original Message-
From: Jim Smith [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 11:55 PM
To: [EMAIL PROTECTED]
Subject: Re: Win2k system state restore


Dave,

The TSM B-A client does have a facility to not replace the hardware
dependent driver information during a system object restore.  Let me
explain:

The traditional method backup/restore of the registry was for the backup
product to export the registry files and backup the exported files.  For
restore, the backup product would simply then restore the files to a
staging area and import the information back into the registry (the
activation of the registry, if you will).  This was a pretty simple
exercises for a backup product.

When Windows 2000 arrived Microsoft changed the procedure a bit and
introduced the registry key:
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore.
The basic procedure now is the backup product restores the registry
information to the staging area (as before) but now is required to move
information from the current registry (these KeysNotToRestore) over the
information that was just restored and then activate the registry. This is
basically allowing information in the current registry to be preserved
across a restore and reboot.  Systems like Active Directory rely on this
as they write information about the log reply into the current registry
which would otherwise be overwritten by the restored copy of the registry
and not available after the reboot.  Another system which exploits this is
the Plug & Play subsystem which describes the hardware dependent driver
information about which you are inquiring.  This subsystem preserves the
information in the HKLM\SYSTEM\CurrentControlSet\Enum portion of the
registry among other things.

While TSM uses the procedures that Microsoft outlines regarding registry
restoration, we found that by default the administrator doesn't have the
proper permissions to write into Enum branch.  This information is well
documented in APAR IC34015.  The APAR will be fixed in TSM 5.1.5; a simple
work around involving using regedit to grant the proper permissions is
documented in the APAR if you are using the TSM 4.2.2 client or TSM 5.1.0
client.

Having said all this, I caution that Microsoft does not guarantee that you
can always restore from hardware a to hardware b.  If you are using
Ntbackup.exe, then it would be safe for me to say that if your particular
environment can be brought back by Ntbackup.exe then TSM should be able to
do it as well.

Hope this helps,
Jim Smith
TSM Development

>>>

Dear All,

Does anybody know if there is any plan in future releases of the TSM
client
for W2K, to implement a facility to not replace the hardware dependent
driver information during a system object restore.

My reason for asking ;

We have a requirement to fully restore a W2K server back to different
hardware (ie. different RAID controller and/or different processor
architecture)
At present, our solution is to use NTBACKUP to backup the system state and
TSM to backup the remainder.

NTBACKUP is intelligent enough to not restore hardware dependent drivers
back onto a platform that is different. I cannot get TSM to emulate this.

The above solution is OK, but I am backing up the WINNT directory with TSM
as flat files, then I am backing up the System Object with TSM and finally
backing up the flat file generated by the NTBACKUP system state operation.

It all seems a bit needless really. ( I know I could exlude WINNT but as
yet
I don't know of any way to exclude the systemobject).

Any thoughts or knowledge of future client releases would be welcome.

Thanks

regards,

-=Dave=-
--
+44 (0)20 7608 7140

"I'll be Bach." - Johann Sebastian Schwarzenegger



www.guardianit.com

The information contained in this email is confidential and intended
only for the use of the individual or entity named above.  If the reader
of this message is not the intended recipient, you are hereby notified
that any dissemination, distribution, or copying of this communication
is strictly prohibited.  Guardian iT Group will accept no responsibility
or liability in respect to this email other than to the addressee.  If you
have received this communication in error, please notify us
immediately via email: [EMAIL PROTECTED]



This e-mail has been scanned for all viruses by MessageLabs.


This e-mail has been scanned for all viruses by MessageLabs.

Re: Simple Archiving question

[Farren Minns]

Hi ??SMers (Thanks for the reply David)

It seems odd to me that the data is not taken from the server. Wouldn't
this be a much quicker option? Anyone know why it works this way?

Also, I'm running TSM 3.7.3.8 (I know it's old, but Tectrade are coming in
a few weeks to bring us bang up to date) on a Solaris 2.7 server. The
client that I wish to archive from is running TSM Client 3.7.2.0.

When I run an archive, will the origional data automatically be removed? I
would rather run the archive, check that it worked ok  and then remove the
data.

So, in this case, I want to archive the dir /wispers/home/fred

Do I simply use the command

archive -subdir=yes "/wispers/home/fred*"

Thanks in advance

Farren Minns - John Wiley & Sons







David Longo <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 14/08/2002
20:01:03

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

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


To:[EMAIL PROTECTED]
cc:
Subject:Re: Simple Archiving question


It is requested from the client.  It doesn't just take some already backed
data and archive it.  Archive works differently, can have different mgmnt
classes, etc.

David Longo

>>> [EMAIL PROTECTED] 08/14/02 10:55AM >>>
Hi all

Just a quick question here. When an archive is performed, am I right in
thinking that the data is taken directly from the TSM server, or is it
requested from the client again?

Thanks in advance

Farren Minns - John Wiley & Sons Ltd

**


Our Chichester based offices are amalgamating and relocating to a new
address
from 1st September 2002

John Wiley & Sons Ltd
The Atrium
Southern Gate
Chichester
West Sussex
PO19 8SQ

Main phone and fax numbers remain the same:
Phone +44 (0)1243 779777
Fax   +44 (0)1243 775878
Direct dial numbers are unchanged

Address, phone and fax nos. for all other Wiley UK locations are unchanged
**




"MMS " made the following
 annotations on 08/14/2002 03:02:16 PM
--

This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify
the sender.  You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of a particular
entity;  and (2) the sender is authorized by the entity to give such views
or opinions.

==



**

Our Chichester based offices are amalgamating and relocating to a new
address
from 1st September 2002

John Wiley & Sons Ltd
The Atrium
Southern Gate
Chichester
West Sussex
PO19 8SQ

Main phone and fax numbers remain the same:
Phone +44 (0)1243 779777
Fax   +44 (0)1243 775878
Direct dial numbers are unchanged

Address, phone and fax nos. for all other Wiley UK locations are unchanged
**

Antwort: Re: Storageworks / AIX / TSM

[Markus Veit]

Hi,
is that a Compaq ( Cambex) HBA or an IBM HBA? There are problems with the driver
for AIX with a Compaq HBA we found.
Although stated, the driver didn't support fabric connections, only AL and PtP.
Our environment was AIX 4.3.3 Compaq HBA and Compaq SAN, trying to do LAN free
backup, which failed.


Mit freundlichen Grüßen / Best Regards

Markus

E-Mail:  [EMAIL PROTECTED]
Internet :  http://www.bayer-ag.de




   

   

   

   An:  [EMAIL PROTECTED]   

   Kopie:  

   Thema:   Re: Storageworks / AIX / TSM   

   

 [EMAIL PROTECTED] 

 U 

 Received :  14.08.2002

 21:34 

 Bitte antworten an "ADSM: 

 Dist Stor Manager"

   

   





Has anyone setup TSM 4.2 on AIX 4.3.3 using Cambex HBAs and compaq
storageworks disk for the disk pool ? Any luck out there?

_
Send and receive Hotmail on your mobile device: http://mobile.msn.com

Bad performance from tape to tape

[Halvorsen Geirr Gulbrand]

Hi All,
I have a performance problem when doing Space-Reclaamtion, or backup storage
pool, when TSM is copying data from one tape drive to the other.
Environment:
Windows 2K server, TSM 4.2.1.15.
Library, Compaq MSL5026, with 2 SDLT drives (Single Module Library).
SCSI Controller, Compaq 64-bit/66Mhz Dual Channel Wide Ultra3 SCSI Adapter
(Compaq version of Adaptec 39160)

Moving data from Disk to Tape runs with expected speed (8-10 MB/s).

>From Tape to tape speed is around 2MB/s. (50GB takes about 7-8hours.)

Does anyone know why? It is killing my daily operations.

Mvh
Geirr G. Halvorsen
TSM Enterprise Backup Specialist
WMdata Danmark A/S

Re: Simple Archiving question

[Large, Matthew]

Farren,

BACKUPSETS take an image from the files the server currently has active for
that client. You could use the -del option on the archive command

**
Deletefiles

Use the deletefiles option with the archive command to delete archived
files from your workstation.

You can also use this option with the restore image command and the
incremental option to delete files from the restored image if they were
deleted from the file space after the image was created.

Syntax

>>-DELetefiles-><



Parameters

There are no parameters for this option.

Examples

Command line:

 dsmc archive "/home/foo/*.c" -deletefiles

 dsmc restore image /local/data -incremental -deletefile

**


By not using the above command, when you issue the archive command, the
files will remain exactly as they were.

Hope this helps.


Matthew Large
TSM Infrastructure Engineer
Lavington Street
Int: 7430 4995
Ext: 07736 448 808


-Original Message-
From: Farren Minns [mailto:[EMAIL PROTECTED]]
Sent: 15 August 2002 10:15
To: [EMAIL PROTECTED]
Subject: Re: Simple Archiving question


Hi ??SMers (Thanks for the reply David)

It seems odd to me that the data is not taken from the server. Wouldn't
this be a much quicker option? Anyone know why it works this way?

Also, I'm running TSM 3.7.3.8 (I know it's old, but Tectrade are coming in
a few weeks to bring us bang up to date) on a Solaris 2.7 server. The
client that I wish to archive from is running TSM Client 3.7.2.0.

When I run an archive, will the origional data automatically be removed? I
would rather run the archive, check that it worked ok  and then remove the
data.

So, in this case, I want to archive the dir /wispers/home/fred

Do I simply use the command

archive -subdir=yes "/wispers/home/fred*"

Thanks in advance

Farren Minns - John Wiley & Sons







David Longo <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 14/08/2002
20:01:03

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

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


To:[EMAIL PROTECTED]
cc:
Subject:Re: Simple Archiving question


It is requested from the client.  It doesn't just take some already backed
data and archive it.  Archive works differently, can have different mgmnt
classes, etc.

David Longo

>>> [EMAIL PROTECTED] 08/14/02 10:55AM >>>
Hi all

Just a quick question here. When an archive is performed, am I right in
thinking that the data is taken directly from the TSM server, or is it
requested from the client again?

Thanks in advance

Farren Minns - John Wiley & Sons Ltd


**


Our Chichester based offices are amalgamating and relocating to a new
address
from 1st September 2002

John Wiley & Sons Ltd
The Atrium
Southern Gate
Chichester
West Sussex
PO19 8SQ

Main phone and fax numbers remain the same:
Phone +44 (0)1243 779777
Fax   +44 (0)1243 775878
Direct dial numbers are unchanged

Address, phone and fax nos. for all other Wiley UK locations are unchanged

**




"MMS " made the following
 annotations on 08/14/2002 03:02:16 PM

--

This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify
the sender.  You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of a particular
entity;  and (2) the sender is authorized by the entity to give such views
or opinions.


==




**

Our Chichester based offices are amalgamating and relocating to a new
address
from 1st September 2002

John Wiley & Sons Ltd
The Atrium
Southern Gate
Chichester
West Sussex
PO19 8SQ

Main phone and fax numbers remain the same:
Phone +44 (0)1243 779777
Fax   +44 (0)1243 775878
Direct dial numbers are unchanged

Address, phone and fax nos. for all other Wiley UK locations are unchanged

**


-

Antwort: Re: Simple Archiving question

[Sascha Braeuning]

Hi Farren,

archived data won't be automatically deleted from your client. Use the
option -deletefiles to delete files after an archive operation.

Example: archive -deletefiles -subdir=yes "/wispers/home/fred*"


MfG
Sascha Bräuning


Sparkassen Informatik, Fellbach

OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach

Telefon:   (0711) 5722-2144
Telefax:   (0711) 5722-1630

Mailadr.:  [EMAIL PROTECTED]

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Gerhard Rentschler]

Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED]
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED]
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the following error message after issuing an update
> storage pool command:
>
>
> ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
> SS
> universe lock.
> ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
>
>  This condition seems to occur when we are in a heavy backup period, which
> since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> upgrading to that release, we applied the 4.2.1.15 fix level at the
> recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
> running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?
>
>  Thanks for  any input.
>
>  - Brian
>
>
>
> Brian L. Nick
> Systems Technician - Storage Solutions
> The Phoenix Companies Inc.
> 100 Bright Meadow Blvd
> Enfield CT. 06082-1900
>
> E-MAIL:  [EMAIL PROTECTED]
> PHONE:   (860)403-2281

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[MC Matt Cooper (2838)]

Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.   This morning I
am looking at my EXPIRATION process was hung and a backup of local tape to
the copytape is hung and it all started with very similar message..
Matt
ANR0538I A resource waiter has been aborted.

ANR0538I A resource waiter has been aborted.

ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.

ANR0538I A resource waiter has been aborted.

ANR0538I A resource waiter has been aborted.

ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
for   
ANRD node 499, filespace 35

ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
processed 
ANR0986I 3603 items for a total of 970,174,464 bytes with a completion state
of 
ANR0986I FAILURE at 06:06:44.

ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
for   
ANRD node 499, filespace 35


-Original Message-
From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:25 AM
To: [EMAIL PROTECTED]
Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server

Good morning...

Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
Going to take it up with support.

Regards Niklas

-Ursprungligt meddelande-
Från: Brian L. Nick [mailto:[EMAIL PROTECTED]]
Skickat: den 14 augusti 2002 16:16
Till: [EMAIL PROTECTED]
Ämne: ANR message Lock acquisition - TSM 4.2.1.15 server

Good morning,

 We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
Also we are receiving the following error message after issuing an update
storage pool command:


ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
SS
universe lock.
ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.

 This condition seems to occur when we are in a heavy backup period, which
since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
upgrading to that release, we applied the 4.2.1.15 fix level at the
recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?

 Thanks for  any input.

 - Brian



Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

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

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Jolliff, Dale]

4.2.2.x servers on AIX are exhibiting the same problems, along with numerous
others.
Oddly enough, our 4.2.1.15 Solaris servers seem to be operating relatively
smoothly.
Note that I said "relatively" and they all have very small DB.

We have an open crit-sit with IBM/Tivoli on an AIX 4.2.2.x server -
We eventually suffered enough DB corruption that we were forced to rebuild
the server and we are in the process of recovering what archives we can from
the old server and importing it into the new server.

This isn't to say that the lock issues caused the corruption, I believe the
corruption was there when we upgraded to 4.2 - the issues that came along
with 4.2 exacerbated the long list of problems we already had.

All in all, if I had it to do over again, I would definitely wait on moving
to 4.2.2.x in production.




-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 6:38 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED]
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED]
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the following error message after issuing an update
> storage pool command:
>
>
> ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
> SS
> universe lock.
> ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
>
>  This condition seems to occur when we are in a heavy backup period, which
> since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> upgrading to that release, we applied the 4.2.1.15 fix level at the
> recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
> running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?
>
>  Thanks for  any input.
>
>  - Brian
>
>
>
> Brian L. Nick
> Systems Technician - Storage Solutions
> The Phoenix Companies Inc.
> 100 Bright Meadow Blvd
> Enfield CT. 06082-1900
>
> E-MAIL:  [EMAIL PROTECTED]
> PHONE:   (860)403-2281

Re: DB2 restore takes long

[Crawford, Lindy]

Hi

Just as a matter of interest, how does rawdevices containers work???

With your db backups, do you do weekly and monthly backups , daily etc and
what type of retention periods do use for these ..

Do you also have offsite copies of these backups and how do you do them at
present.??


Thanks you your assistance.

> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> * +27-31-3642185
> +27-31-3642946
 [EMAIL PROTECTED] 




-Original Message-
From: MUSTAFA BAYTAR [mailto:[EMAIL PROTECTED]]
Sent: 15 August 2002 10:18
To: [EMAIL PROTECTED]
Subject: Re: DB2 restore takes long


Hi Lindy ,
We have SAP R3 4.B with DB2 database running on aix 4.3.3 and
we had similar problem about 1.5 years ago.
our db2 size was 120 GB and when we started database restore its took
nearly  12 hours to create
db2 conteiners and 4 hours to restore them.
after that we have moved filesystem conteiners to rowdevices conteiners and
distrubute them over
diferent disks .
now our db2 size is 420 GB and restore take approximately 4 hours.



  "Crawford,
  Lindy"   To:  [EMAIL PROTECTED]
  Subject: DB2 restore takes
long
  Sent by: "ADSM:
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  T.EDU>


  15.08.2002 10:26
  Please respond
  to "ADSM: Dist
  Stor Manager"





Hi TSMers,
Could some please assist me. I did a restore yesterday, started it 8:13am
and it only completed at 21:04 pm. This for the environment that we work
with it is unacceptable in terms of response. My client  - node is as
follows:_
TSM 4.2
DB2 7.2
SAP R3 4.6c
Database size is : 48gigs
What can I do to make this process faster. The reason why I am concerned is
that my backup only takes 1h30mins, so the most time it took I would have
expected it to be 2 or 3hours.

Please help!!!



> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> *  +27-31-3642185
 <<...OLE_Obj...>>  +27-31-3642946
 [EMAIL PROTECTED] 





WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm


WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm

Re: DB2 restore takes long

[Mr. Lindsay Morris]

If you have accounting turned on, look at the accounting log to see whether
the time was spent mostly in:
--idle wait (client creating files is slower than client reading them!)
--media wait (was client data scattered over 30 tapes?)
--comm wait (was network slow then?)
It's in dsmaccnt.log, in your server bin directory.

We have some detailed info on how to do this at
http://www.servergraph.com/techtip3.htm

Hope this helps.
-
Mr. Lindsay Morris
CEO, Servergraph
www.servergraph.com
859-253-8000 ofc
425-988-8478 fax


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Crawford, Lindy
> Sent: Thursday, August 15, 2002 3:26 AM
> To: [EMAIL PROTECTED]
> Subject: DB2 restore takes long
>
>
> Hi TSMers,
> Could some please assist me. I did a restore yesterday, started it 8:13am
> and it only completed at 21:04 pm. This for the environment that we work
> with it is unacceptable in terms of response. My client  - node is as
> follows:_
> TSM 4.2
> DB2 7.2
> SAP R3 4.6c
> Database size is : 48gigs
> What can I do to make this process faster. The reason why I am
> concerned is
> that my backup only takes 1h30mins, so the most time it took I would have
> expected it to be 2 or 3hours.
>
> Please help!!!
>
>
>
> > Lindy Crawford
> > Business Solutions: IT
> > BoE Corporate
> >
> > *  +27-31-3642185
>  <<...OLE_Obj...>>  +27-31-3642946
>  [EMAIL PROTECTED] 
>
>
>
>
>
> WARNING:
> Any unauthorised use or interception of this email is illegal. If
> this email
> is not intended for you, you may not copy, distribute nor disclose the
> contents to anyone. Save for bona fide company matters, BoE Ltd does not
> accept any responsibility for the opinions expressed in this email.
> For further details please see: http://www.boe.co.za/emaildisclaimer.htm
>

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Menides, Richard]

I had the same problem after upgrading from 3.74 tp 5.11 on AIX 4.3. The fix
is to change the resource time out in the TSM server's dsmserv.opt file to
60 the default is 10. Hope this helps you out.

Senior TSM consultant

Richard Menides

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 7:38 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED]
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED]
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the following error message after issuing an update
> storage pool command:
>
>
> ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
> SS
> universe lock.
> ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
>
>  This condition seems to occur when we are in a heavy backup period, which
> since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> upgrading to that release, we applied the 4.2.1.15 fix level at the
> recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
> running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?
>
>  Thanks for  any input.
>
>  - Brian
>
>
>
> Brian L. Nick
> Systems Technician - Storage Solutions
> The Phoenix Companies Inc.
> 100 Bright Meadow Blvd
> Enfield CT. 06082-1900
>
> E-MAIL:  [EMAIL PROTECTED]
> PHONE:   (860)403-2281

***
 This message and any attachments is solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use, or
distribution of the information included in this message is prohibited --
please immediately and permanently delete this message.

More on mount points

[McMullen David E]

Can anyone give me any help on the mountpoint problem I posted earlier?

>>I turned on collocation last week and now I am getting this message:
>>
>>ANR1082W Space reclamation terminated for volume 4A0023 - insufficient
number of mount points >>available for removable media.
>>
>>I looked up the error message and it tells me:User Response: If necessary,
make more mount points available
>>
>>Is this the same as mount limit for the server?  I see that you can
specify number of mount points for a
>>node.  But how can you specify this for a tape?

David Mac

Re: 5.1.1 Windows 2000 scheduler won't start

[Adams, Matt (US - Hermitage)]

Thanks Eliza.  I am in the same boat as Tab, I have experienced it
intermittently, but haven't reported it because we rarely boot our W2K
servers.

If you have the time, and think about it, let us know the APAR number
assigned.

Thanks,

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP



-Original Message-
From: Eliza Lau [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 9:57 AM
To: [EMAIL PROTECTED]
Subject: Re: 5.1.1 Windows 2000 scheduler won't start


Just heard from Level 2 support.  It is a bug since 4.2.  An APAR will be
assigned to the problem.  4.2 has been out for a while.  Why Tivoli didn't
know about this?  It is so obvious.  The  scheduler didn't start the first
time we installed it.

Eliza

>
> Eliza,
>
> Just for the record, I'm seeing the same behavior in the TSM 4.2.2 client
> on Windows 2000 Server.
>
> I haven't done anything about it yet because the service does start
> eventually, and we almost never reboot servers.
>
> Tab Trepagnier
> TSM Administrator
> Laitram Corporation
>
>
>
>
>
>
> Eliza Lau
> <[EMAIL PROTECTED]   To: [EMAIL PROTECTED]
> VT.EDU>  cc:
> Sent by: Subject: Re: 5.1.1 Windows
2000 scheduler won't
> "ADSM: Dist   start
> Stor Manager"
> <[EMAIL PROTECTED]
> IST.EDU>
>
>
> 08/09/2002
> 01:58 PM
> Please respond
> to "ADSM: Dist
> Stor Manager"
>
>
>
>
>
>
> Ours is also a brand new W2K server with no previous version of TSM client
> installed.
>
> Eliza
>
> >
> > In our case, the servers that are failing are brand new servers, never
> had
> > an older client installed.
> >
> > As a bypass, we've set the recovery option on the service to restart on
> the
> > first failure - seems to work so far.
> >
> > Tim
> > -Original Message-
> > From: Halvorsen Geirr Gulbrand [mailto:[EMAIL PROTECTED]]
> > Sent: August 9, 2002 1:32 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: 5.1.1 Windows 2000 scheduler won't start
> >
> > Hello,
> > I've seen this when upgrading from one level to another, (in my case
from
> > 4.1.x to 4.2.x).
> > I used DSMCUTIL to remove the service, then started the client, and from
> > utilities, installed scheduler service again, importing same opt-file,
> and
> > it worked fine.
> > I don't know if this is the case for v. 5.1.x, but it's worth a
> try...maybe?
> >
> > Rgds.
> > Geirr G. Halvorsen
> >
> > -Original Message-
> > From: Boireau, Eric (MED) [mailto:[EMAIL PROTECTED]]
> > Sent: 9. august 2002 07:35
> > To: [EMAIL PROTECTED]
> > Subject: Re: 5.1.1 Windows 2000 scheduler won't start
> >
> >
> > I have the same kind of issue on my Laptop with Win2K Pro and TSM
5.1.0.1
> > Client. It sayd that the service hangs at startup. But the service is
> > started and run well
> >
> > Regards,
> > Eric
> > -Original Message-
> > From: Rushforth, Tim [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 09, 2002 3:27 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: 5.1.1 Windows 2000 scheduler won't start
> >
> >
> > Hi Eliza:
> >
> > We are experiencing this on SOME of our Windows 2000 Servers.  On these
> > servers the Schedule service fails SOMETIMES on reboot. On other 2000
> > servers we have never had a problem.  I've opened a problem with Tivoli
> on
> > this (PMR 40368).  The only similarity for machines that are failing
that
> I
> > can see (so far!) is that they are all multi-processor.
> >
> > We are running 5.11 clients, server is windows 2000 4.2.0.  (We've just
> > started to roll out the 5.11 client - all looked good in testing!)
> >
> > Tim Rushforth
> > City of Winnipeg
> >
> > -Original Message-
> > From: Eliza Lau [mailto:[EMAIL PROTECTED]]
> > Sent: August 8, 2002 11:39 AM
> > To: [EMAIL PROTECTED]
> > Subject: 5.1.1 Windows 2000 scheduler won't start
> >
> > We are experiencing problems with the TSM scheduler not starting on
> Windows
> > 2000 servers.
> >
> > A user installed TSM client 5.1.1 on a Windows 2000 server with SP2 and
> all
> > hotfoxes.  After the scheduler is installed, the user got the following
> > message:
> >   An error occurred while starting the service
> >
> > He then pressed OK and a message box said
> >   Scheduler successfully installed
> >
> > When he looked at the Scheduler service, it was installed but not
> started.
> > He started it manually and things worked fine from then on. The error in
> the
> > event log:  event 7031
> > The TSM scheduler service terminated unexpectedly
> >
> > After the machine reboots, the schedule doesn't start even though it is
> set
> > to automatic.  In the event log:  event 7022
> > The TSM scheduler service hung on starting
> >
> > After a manual start, the scheduler works again.  He c

Re: Win2k system state restore

[Bill Boyer]

I found it on IBMlink. Here's the apar text:

ERROR DESCRIPTION:
TSM Client on Windows 2000 incorrectly restores the registry
  key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum

This key is specified in the registry under KeysNotToRestore,
  and according to Microsoft article Q249694, the existing copy of
  this registry key and its subkeys should be retained during a
  registry restore.  During a TSM registry restore, this key is
  replaced with the backed up version because Administrators do
  not have access to write to this key, by default.

No error is reported, but the registry is restored incorrectly
  which could cause unknown results.  This problem occurs because
  permissions are preserved in the registry copy being restored,
  so TSM cannot overwrite the Enum key with the existing copy.

This affects 4.2 and 5.1 TSM Clients on Windows 2000 and XP.

  Initial Impact: MEDIUM


  LOCAL FIX:
  Use regedt32 to grant Administrators 'Full Control' to the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum
  Then run registry/system object restore.


  PROBLEM SUMMARY:
  
  * USERS AFFECTED: Windows BA clients.  *
  
  * PROBLEM DESCRIPTION: TSM Client on Windows 2000 incorrectly  *
  *  restores the registry key:  *
  *  HKLM\SYSTEM\CurrentControlSet\Enum. *
  *  This key is specified in the registry   *
  *  under KeysNotToRestore, and according   *
  *  to Microsoft article Q249694, the   *
  *  existing copy of this registry key and  *
  *  its subkeys should be retained during   *
  *  a registry restore. During a TSM*
  *  registry restore, this key is replaced  *
  *  with the backed up version because  *
  *  Administrators do not have access   *
  *  to write to this key, by default.   *
  
  * RECOMMENDATION:  *
  
  Some of the Registry keys (like 'Enum') give ReadOnly access
  for Everyone and Full access for System only. As a result
  everyone gets the ERROR_ACCESS_DENIED error trying to write
  into these keys.

  Also, to access Registry keys TSM uses Win32 API function
  RegQueryInfoKey(). There is a MS article Q307308
  (W2k, W2k SP1, W2k SP2) which describes that RegQueryInfoKey()
  function may return Zero for ControlSetnnn subkey parameters.



  PROBLEM CONCLUSION:
  TSM uses temporary Registry hive to perform operations which
  are described in Microsoft article Q249694. Added code to reset
  Registry key access permissions for this temporary hive before
  any operations and restore them after.

  Also due to Microsoft article Q307308 TSM could incorrectly
  skip some of the Registry keys. Added code to avoid this
  problem using RegQueryInfoKey() and RegEnumKeyEx() together
  to obtain the correct subkey parameters.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Frost, Dave
Sent: Thursday, August 15, 2002 5:15 AM
To: [EMAIL PROTECTED]
Subject: Re: Win2k system state restore


Jim,

Thanks for that.  But...

A lookup in the tivoli/support/knowledgebase/ for apar ic34015 returns 0
records.  Nor is it documented in the readmes for the 4.2 or 5.1 client in
"maintenance" or "patches" at boulder.

It would seem that this apar is not publically available.


  regards,

-=Dave=-
--
+44 (0)20 7608 7140

Know thyself.  If you need help, call the C.I.A.



-Original Message-
From: Jim Smith [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 11:55 PM
To: [EMAIL PROTECTED]
Subject: Re: Win2k system state restore


Dave,

The TSM B-A client does have a facility to not replace the hardware
dependent driver information during a system object restore.  Let me
explain:

The traditional method backup/restore of the registry was for the backup
product to export the registry files and backup the exported files.  For
restore, the backup product would simply then restore the files to a
staging area and import the information back into the registry (the
activation of the registry, if you will).  This was a pretty simple
exercises for a backup product.

When Windows 2000 arrived Microsoft changed the procedure a bit and
introduced the registry key:
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore.
The basic procedure now is the backup product restores the registry
information to the staging area (as before) but now is required to move
information from the current registry (these KeysNotToRestore) o

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[David Longo]

Richard,
I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is 
set to 10.  Looked at manuals and see this is a new option with 4.2.
There is only a small paragraph about this.  What RESOURCES is this 
talking about and what are the implications of changing?

It's probably not tape mounts as I can have a process waiting on a tape
that's being used by another process for well over 10 minutes. (No problem 
with that, just know it doesn't apply to tape mounts.)

David Longo

>>> [EMAIL PROTECTED] 08/15/02 08:47AM >>>
I had the same problem after upgrading from 3.74 tp 5.11 on AIX 4.3. The fix
is to change the resource time out in the TSM server's dsmserv.opt file to
60 the default is 10. Hope this helps you out.

Senior TSM consultant

Richard Menides

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, August 15, 2002 7:38 AM
To: [EMAIL PROTECTED] 
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED] 
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED] 
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED] 
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]] 
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED] 
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the following error message after issuing an update
> storage pool command:
>
>
> ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
> SS
> universe lock.
> ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
>
>  This condition seems to occur when we are in a heavy backup period, which
> since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> upgrading to that release, we applied the 4.2.1.15 fix level at the
> recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
> running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?
>
>  Thanks for  any input.
>
>  - Brian
>
>
>
> Brian L. Nick
> Systems Technician - Storage Solutions
> The Phoenix Companies Inc.
> 100 Bright Meadow Blvd
> Enfield CT. 06082-1900
>
> E-MAIL:  [EMAIL PROTECTED] 
> PHONE:   (860)403-2281

***
 This message and any attachments is solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use, or
distribution of the information included in this message is prohibited --
please immediately and permanently delete this message.


"MMS " made the following
 annotations on 08/15/20

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Gerhard Rentschler]

The default changed from 10 minutes to 60 minutes with TSM 5.1.
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> David Longo
> Sent: Thursday, August 15, 2002 3:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Richard,
> I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is
> set to 10.  Looked at manuals and see this is a new option with 4.2.
> There is only a small paragraph about this.  What RESOURCES is this
> talking about and what are the implications of changing?
>
> It's probably not tape mounts as I can have a process waiting on a tape
> that's being used by another process for well over 10 minutes.
> (No problem
> with that, just know it doesn't apply to tape mounts.)
>
> David Longo
>
> >>> [EMAIL PROTECTED] 08/15/02 08:47AM >>>
> I had the same problem after upgrading from 3.74 tp 5.11 on AIX
> 4.3. The fix
> is to change the resource time out in the TSM server's dsmserv.opt file to
> 60 the default is 10. Hope this helps you out.
>
> Senior TSM consultant
>
> Richard Menides
>
> -Original Message-
> From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Hello,
> this is obviously a known problem. See the discussion a few days earlier
> with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
> I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
> 5.1.1.2. This didn't change anything. Then I had to supply diagnostic
> information. According to the web interface to Tivoli problem
> management the
> problem was closed on August 6th without any further information.
> I haven't
> got any new information since  this day.
> Best regards
> Gerhard
>
> ---
> Gerhard Rentschleremail:[EMAIL PROTECTED]
> Regional Computing Center tel.   ++49/711/685 5806
> University of Stuttgart   fax:   ++49/711/682357
> Allmandring 30a
> D 70550
> Stuttgart
> Germany
>
>
>
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> > MC Matt Cooper (2838)
> > Sent: Thursday, August 15, 2002 1:22 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
> >
> >
> > Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> > This morning I
> > am looking at my EXPIRATION process was hung and a backup of
> local tape to
> > the copytape is hung and it all started with very similar message..
> > Matt
> > ANR0538I A resource waiter has been aborted.
> >
> > ANR0538I A resource waiter has been aborted.
> >
> > ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
> >
> > ANR0538I A resource waiter has been aborted.
> >
> > ANR0538I A resource waiter has been aborted.
> >
> > ANRD IMFS(3566): ThreadId<656> Lock conflict error in
> obtaining sLock
> > for
> > ANRD node 499, filespace 35
> >
> > ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> > processed
> > ANR0986I 3603 items for a total of 970,174,464 bytes with a
> > completion state
> > of
> > ANR0986I FAILURE at 06:06:44.
> >
> > ANRD IMFS(3566): ThreadId<662> Lock conflict error in
> obtaining sLock
> > for
> > ANRD node 499, filespace 35
> >
> >
> > -Original Message-
> > From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 15, 2002 2:25 AM
> > To: [EMAIL PROTECTED]
> > Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
> >
> > Good morning...
> >
> > Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> > Going to take it up with support.
> >
> > Regards Niklas
> >
> > -Ursprungligt meddelande-
> > Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> > Skickat: den 14 augusti 2002 16:16
> > Till: [EMAIL PROTECTED]
> > Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
> >
> > Good morning,
> >
> >  We are running TSM 4.2.1.15 on OS/390 2.10 and are having
> several issues.
> > One of these is poor performance since upgrading from 4.2.2.0
> to 4.2.1.15.
> > Also we are receiving the following error message after issuing
> an update
> > storage pool command:
> >
> >
> > ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock)
> failed for
> > SS
> > universe lock.
> > ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> > ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
> >
> >  This condition seems to occur when we are in a heavy backup
> period, which
> > since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> > upgrading to that release, we applied the 4.2.1.15 fix 

Upgrading TSM from 3.7.x to 5.1.xx

[Halvorsen Geirr Gulbrand]

Hello all of You!

I'm about to do an upgrade of TSM from version 3.7.x to version 5.1.x
I know that upgrading from 3.7 to 4.1 required running a special tool called
tsmfixup.cmd.
Are there any consideration like these or other things I have to be aware
of?

Any help highly appreciated!

Best Regards
Geirr G. Halvorsen

Re: More on mount points

[Bill Dourado]

David,

Enter command:

QUERY STGPOOL  NAME_OF_YOUR_COLOCATIONDISKPOOL  F=D

In the response look for "Migration Processes:  ?"

If ? greater than 1,  reduce to suit,  depending on how many tape drives
you have available.
Example:

UPDATE STGPOOL NAME_OF_YOUR_COLOCATIONDISKPOOL MIGPROCESS=1


Regards

Bill Dourado







McMullen David E
  cc:
Sent by: "ADSM: Subject: More on mount points
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>


15/08/02 14:05
Please respond
to "ADSM: Dist
Stor Manager"






Can anyone give me any help on the mountpoint problem I posted earlier?

>>I turned on collocation last week and now I am getting this message:
>>
>>ANR1082W Space reclamation terminated for volume 4A0023 - insufficient
number of mount points >>available for removable media.
>>
>>I looked up the error message and it tells me:User Response: If
necessary,
make more mount points available
>>
>>Is this the same as mount limit for the server?  I see that you can
specify number of mount points for a
>>node.  But how can you specify this for a tape?

David Mac

Re: Bad performance from tape to tape

[Joe Pendergast]

Is the disk pool cached?
I ran into a situation where the disk pool cache instead of tape was being used.
This slowed my LTO drives to a crawl during certain operations.
I now varyoff the disk pools before I run the process with expected results
Don't forget to vary them back on at the end..
Note: the disk pool cache is a great help in restore time, but it can adversely
the affect of what should be a tape to tape process.





Halvorsen Geirr Gulbrand <[EMAIL PROTECTED]> on 08/15/2002 03:00:23 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: Joseph Pendergast/Corona/Watson)

Subject:  Bad performance from tape to tape



Hi All,
I have a performance problem when doing Space-Reclaamtion, or backup storage
pool, when TSM is copying data from one tape drive to the other.
Environment:
Windows 2K server, TSM 4.2.1.15.
Library, Compaq MSL5026, with 2 SDLT drives (Single Module Library).
SCSI Controller, Compaq 64-bit/66Mhz Dual Channel Wide Ultra3 SCSI Adapter
(Compaq version of Adaptec 39160)

Moving data from Disk to Tape runs with expected speed (8-10 MB/s).

>From Tape to tape speed is around 2MB/s. (50GB takes about 7-8hours.)

Does anyone know why? It is killing my daily operations.

Mvh
Geirr G. Halvorsen
TSM Enterprise Backup Specialist
WMdata Danmark A/S

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Jolliff, Dale]

Just be aware of what lengthening the RESOURCETIMEOUT will do, especially if
you are susceptible to "logpinned" conditions due to slow, long-running
sessions.




-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 8:17 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Richard,
I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is
set to 10.  Looked at manuals and see this is a new option with 4.2.
There is only a small paragraph about this.  What RESOURCES is this
talking about and what are the implications of changing?

It's probably not tape mounts as I can have a process waiting on a tape
that's being used by another process for well over 10 minutes. (No problem
with that, just know it doesn't apply to tape mounts.)

David Longo

>>> [EMAIL PROTECTED] 08/15/02 08:47AM >>>
I had the same problem after upgrading from 3.74 tp 5.11 on AIX 4.3. The fix
is to change the resource time out in the TSM server's dsmserv.opt file to
60 the default is 10. Hope this helps you out.

Senior TSM consultant

Richard Menides

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 7:38 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED]
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED]
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the following error message after issuing an update
> storage pool command:
>
>
> ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
> SS
> universe lock.
> ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
>
>  This condition seems to occur when we are in a heavy backup period, which
> since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> upgrading to that release, we applied the 4.2.1.15 fix level at the
> recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
> running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?
>
>  Thanks for  any input.
>
>  - Brian
>
>
>
> Brian L. Nick
> Systems Technician - Storage Solutions
> The Phoenix Companies Inc.
> 100 Bright Meadow Blvd
> Enfield CT. 06082-1900
>
> E-MAIL:  [EMAIL PROTECTED]
> PHONE:   (860)403-2281

***

Re: W2K - BMR - using GHOST *RESOLVED*

[Marc Levitan]

It looks like you have to backup the system object more than once???
Here is some data from only 1 backup of the system objects.
Following is the data from a second backup.  Notice the size of the COMPDB,
EVENTLOG, and RSM all increase!
It is after the second backup that I was able to successfully restore the
system objects.

Total number of objects inspected:7,527
Total number of objects backed up:7,328
Total number of objects updated:  0
Total number of objects rebound:  0
Total number of objects deleted:  0
Total number of objects expired:  0
Total number of objects failed:   0
Total number of bytes transferred:   504.75 MB
Data transfer time:   69.29 sec
Network data transfer rate:7,459.44 KB/sec
Aggregate data transfer rate:652.23 KB/sec
Objects compressed by:   30%
Elapsed processing time:   00:00:12
tsm> q systemobject
Session established with server
  Server Version 4, Release 2, Level 1.15
  Server date/time: 08/15/2002 08:06:14  Last access: 08/14/2002 15:54:01

 Size  Backup DateMgmt Class A/I File
   ----- --- 
  376  08/14/2002 16:03:01DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\COMPDB
  376  08/14/2002 16:03:02DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\EVENTLOG
  138,902,044  08/14/2002 16:04:57DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\SYSFILES
3,972,159  08/14/2002 16:07:09DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\REGISTRY
  392  08/14/2002 16:07:11DEFAULT A  SYSTEM
OBJECT\TSMOSDRT\RSM



Total number of objects inspected:7,539
Total number of objects backed up:1,838
Total number of objects updated:  0
Total number of objects rebound:  0
Total number of objects deleted:  0
Total number of objects expired:  0
Total number of objects failed:   0
Total number of bytes transferred:   141.17 MB
Data transfer time:   30.65 sec
Network data transfer rate:4,715.24 KB/sec
Aggregate data transfer rate:309.93 KB/sec
Objects compressed by:   41%
Elapsed processing time:   00:03:46
tsm> q systemobject
 Size  Backup DateMgmt Class A/I File
   ----- --- 
7,930  08/15/2002 08:09:24DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\COMPDB
5,593  08/15/2002 08:09:25DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\EVENTLOG
  138,902,044  08/15/2002 08:11:19DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\SYSFILES
4,022,582  08/15/2002 08:14:15DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\REGISTRY
   19,936  08/15/2002 08:14:17DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\RSM




"Cowperthwaite,
Eric" To: [EMAIL PROTECTED]
Subject: Re: W2K - BMR - using GHOST
Sent by: "ADSM:
Dist Stor Manager"
<[EMAIL PROTECTED]
EDU>


08/14/2002 07:39
PM
Please respond to
"ADSM: Dist Stor
Manager"





That method should work fine, based on my, admittedly, limited
understanding
of Win2K domains. I do know that our desktop support unit uses this sort of
method with Win2K desktops, ghost and system restores.

Eric

> -Original Message-
> From: Rob Schroeder [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 14, 2002 10:53 AM
> To: [EMAIL PROTECTED]
> Subject: Re: W2K - BMR - using GHOST
>
>
> After the install you can just change the server to be a member of a
> workgroup, then without rebooting, change it back to be a
> member of the
> domain.  The SID will then be reconciled within AD.  If this
> ghost image is
> a copy of a server already in production, then you may have
> to do this to
> both the clone and the cloned server.
>
> Rob
>
>
>
>   Marc Levitan
>[EMAIL PROTECTED]
>   C.COM>   cc:
>   Sent by: "ADSM:  Subject:  Re:
> W2K - BMR - using GHOST
>   Dist Stor
>   Manager"
>   <[EMAIL PROTECTED]
>   .EDU>
>
>
>   08/14/2002 12:18
>  

Re: DB2 restore takes long

[MUSTAFA BAYTAR]

Hi Lindy,
We do online backups every Weekday  and offline backup every Sunday.Every day we are 
running backup
storage pools .All backups have 10 days retention
periods.We dont keep monthly or  weekly backups  but every Monday in our disaster 
recovery center we
are  restoring db2 ofline backups from offsite copies.





  "Crawford,
  Lindy"   To:  [EMAIL PROTECTED]
  Subject: Re: DB2 restore takes long
  Sent by: "ADSM:
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  T.EDU>


  15.08.2002 15:17
  Please respond
  to "ADSM: Dist
  Stor Manager"





Hi

Just as a matter of interest, how does rawdevices containers work???

With your db backups, do you do weekly and monthly backups , daily etc and
what type of retention periods do use for these ..

Do you also have offsite copies of these backups and how do you do them at
present.??


Thanks you your assistance.

> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> * +27-31-3642185
> +27-31-3642946
 [EMAIL PROTECTED] 




-Original Message-
From: MUSTAFA BAYTAR [mailto:[EMAIL PROTECTED]]
Sent: 15 August 2002 10:18
To: [EMAIL PROTECTED]
Subject: Re: DB2 restore takes long


Hi Lindy ,
We have SAP R3 4.B with DB2 database running on aix 4.3.3 and
we had similar problem about 1.5 years ago.
our db2 size was 120 GB and when we started database restore its took
nearly  12 hours to create
db2 conteiners and 4 hours to restore them.
after that we have moved filesystem conteiners to rowdevices conteiners and
distrubute them over
diferent disks .
now our db2 size is 420 GB and restore take approximately 4 hours.



  "Crawford,
  Lindy"   To:  [EMAIL PROTECTED]
  Subject: DB2 restore takes
long
  Sent by: "ADSM:
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  T.EDU>


  15.08.2002 10:26
  Please respond
  to "ADSM: Dist
  Stor Manager"





Hi TSMers,
Could some please assist me. I did a restore yesterday, started it 8:13am
and it only completed at 21:04 pm. This for the environment that we work
with it is unacceptable in terms of response. My client  - node is as
follows:_
TSM 4.2
DB2 7.2
SAP R3 4.6c
Database size is : 48gigs
What can I do to make this process faster. The reason why I am concerned is
that my backup only takes 1h30mins, so the most time it took I would have
expected it to be 2 or 3hours.

Please help!!!



> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> *  +27-31-3642185
 <<...OLE_Obj...>>  +27-31-3642946
 [EMAIL PROTECTED] 





WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm


WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm

TSM Client on SGI

[Short, Anne]

I've installed TSM version 5.1 on an IRIX box but get the following when I
tried to start it:

32052:dsm: rld: Fatal Error: Cannot Successfully map soname
'libdm.so' under any of the filenames
/usr/lib32/libdm.so:/usr/lib32/internal/libdm.so:/lib32/libdm.so:/opt/lib32/
libdm.so:/usr/lib32/libdm.so.1:/usr/lib32/internal/libdm.so.1:/lib32/libdm.s
o.1:/opt/lib32/libdm.so.1:

I searched the archives and found the following exchange:

Fred, we went through that...answer:

 eoe.sw.dmi is the package.found this by running this
command:
 versions long|grep libdm.so

 Kent Monthei
 GlaxoSmithKline

 "Fred Johanson" <[EMAIL PROTECTED]>

 Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
 20-Mar-2002 14:14
 Please respond to "ADSM: Dist Stor Manager"
<[EMAIL PROTECTED]>

 To: ADSM-L
 Subject:ADSM on sgi system

 I received this from one of my users.  This is a platform
that we do not
 support internall, but if anyone wants to use it, we try to
answer any
 questions they have.
 Can any one help me on this??


 >I am trying to install ADSM on a sgi system but get the
error on start
 >up can not Successfully map soname 'libdm.so' under
any of the
 >filenames //... and so on.
 >Could you run a query on this I need to find out were to
get this file.
 >Ian

But I'm not sure what to do with that information.  An IRIX guru I'm not!
How do I fix the libdm.so problem and what does eoe.sw.dmi have to do with
it??

Also, when I downloaded the version 5.1 software, there was a note that said
that it was "at v4.2 functionality"; what does that mean?  They just slapped
a new version number on the old version?  Would that be 4.2 with or without
all the latest fixes?

Any help would be appreciated...Thanks!


Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland  20879
301-240-6184
CODA/I Storage Management

Re: Bad performance from tape to tape

[Bill Boyer]

The tape-to-tape operation that is adversely affected is reclamation. If the
primay location of a file is in a random access disk pool, then TSM does not
'batch' the files together. Each transaction is a single file. The primary
location can be a disk sequential access pool, but not random access. We
originally came across this with DIRMC. We had the primary a DISK pool and
then only created the copypool. The reclamation on the copypool tapes used
to take days. Opened a PMR with Tivoli and got the 'working as designed'
answer.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Joe Pendergast
Sent: Thursday, August 15, 2002 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Bad performance from tape to tape


Is the disk pool cached?
I ran into a situation where the disk pool cache instead of tape was being
used.
This slowed my LTO drives to a crawl during certain operations.
I now varyoff the disk pools before I run the process with expected results
Don't forget to vary them back on at the end..
Note: the disk pool cache is a great help in restore time, but it can
adversely
the affect of what should be a tape to tape process.





Halvorsen Geirr Gulbrand <[EMAIL PROTECTED]> on 08/15/2002 03:00:23 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: Joseph Pendergast/Corona/Watson)

Subject:  Bad performance from tape to tape



Hi All,
I have a performance problem when doing Space-Reclaamtion, or backup storage
pool, when TSM is copying data from one tape drive to the other.
Environment:
Windows 2K server, TSM 4.2.1.15.
Library, Compaq MSL5026, with 2 SDLT drives (Single Module Library).
SCSI Controller, Compaq 64-bit/66Mhz Dual Channel Wide Ultra3 SCSI Adapter
(Compaq version of Adaptec 39160)

Moving data from Disk to Tape runs with expected speed (8-10 MB/s).

>From Tape to tape speed is around 2MB/s. (50GB takes about 7-8hours.)

Does anyone know why? It is killing my daily operations.

Mvh
Geirr G. Halvorsen
TSM Enterprise Backup Specialist
WMdata Danmark A/S

Re: TSM Client on SGI

[Remco Post]

TSM on IRIX uses the DMI (data migration interface) to performa backups
and restores (and even HSM, if you're really daring), so you need the
libs to DMI to be able to use is, install the eoe.sw.dmi package. The
Irix client is btw very unstable, and though I personally have seen very
few problems with it, still think it's the least stable client

On donderdag, augustus 15, 2002, at 03:57 , Short, Anne wrote:

> I've installed TSM version 5.1 on an IRIX box but get the following
> when I
> tried to start it:
>
> 32052:dsm: rld: Fatal Error: Cannot Successfully map
> soname
> 'libdm.so' under any of the filenames
> /usr/lib32/libdm.so:/usr/lib32/internal/libdm.so:/lib32/libdm.so:/opt/lib32/
> libdm.so:/usr/lib32/libdm.so.1:/usr/lib32/internal/libdm.so.1:/lib32/libdm.
> s
> o.1:/opt/lib32/libdm.so.1:
>
> I searched the archives and found the following exchange:
>
> Fred, we went through that...answer:
>
>  eoe.sw.dmi is the package.found this by running
> this
> command:
>  versions long|grep libdm.so
>
>  Kent Monthei
>  GlaxoSmithKline
>
>  "Fred Johanson" <[EMAIL PROTECTED]>
>
>  Sent by: "ADSM: Dist Stor Manager"  [EMAIL PROTECTED]>
>  20-Mar-2002 14:14
>  Please respond to "ADSM: Dist Stor Manager"
> <[EMAIL PROTECTED]>
>
>  To: ADSM-L
>  Subject:ADSM on sgi system
>
>  I received this from one of my users.  This is a
> platform
> that we do not
>  support internall, but if anyone wants to use it, we
> try to
> answer any
>  questions they have.
>  Can any one help me on this??
>
>
>> I am trying to install ADSM on a sgi system but get the
> error on start
>> up can not Successfully map soname 'libdm.so' under
> any of the
>> filenames //... and so on.
>> Could you run a query on this I need to find out were to
> get this file.
>> Ian
>
> But I'm not sure what to do with that information.  An IRIX guru I'm
> not!
> How do I fix the libdm.so problem and what does eoe.sw.dmi have to do
> with
> it??
>
> Also, when I downloaded the version 5.1 software, there was a note that
> said
> that it was "at v4.2 functionality"; what does that mean?  They just
> slapped
> a new version number on the old version?  Would that be 4.2 with or
> without
> all the latest fixes?
>
> Any help would be appreciated...Thanks!
>
>
> Anne Short
> Lockheed Martin Enterprise Information Systems
> Gaithersburg, Maryland  20879
> 301-240-6184
> CODA/I Storage Management
>
---
Met vriendelijke groeten,

Remco Post

SARA - Stichting Academisch Rekencentrum Amsterdamhttp://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: SQL timestamp not working when upgraded to 4.2.2 for summary tabl e

[PAC Brion Arnaud]

Hi Denis,

Just for information : I tested your query on my system (4.2.2.15) and
it worked like a charm (except I had to modify "Node Name" to
"Node_Name")

Did you apply the latest PTF's to get 4.2.2.15 ? Maybe it could help ...
Good luck anyway !

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   | 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-Original Message-
From: L'Huillier, Denis [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, 15 August, 2002 15:39
To: [EMAIL PROTECTED]
Subject: SQL timestamp not working when upgraded to 4.2.2 for summary
tabl e


Hello -
Since I upgraded our 4.1 server to 4.2.2 my sql query against the
summary table no longer works. Has anyone run into this problem before?
Here's the query...

/* --- Query Summary Table  */
/* ---   Run as a macro   - */
select cast(entity as varchar(12)) as "Node Name", \ cast(activity as
varchar(10)) as Type, \ cast(number as varchar(8)) "Filespace", \
cast(failed as varchar(3)) "Stg", \ cast(affected as decimal(7,0)) as
files, \ cast(bytes/1024/1024 as decimal(12,4)) as "Phy_MB", \
cast(bytes/1024/1024 as decimal(12,4)) as "Log_MB" \ from summary where
end_time>=timestamp(current_date -1 days, '09:00:00') \ and
end_time<=timestamp(current_date, '08:59:59') \ and (activity='BACKUP'
or activity='ARCHIVE') \ order by "Node Name"

Here's the output from a 4.1 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB
Log_MB
  --  -  ---  -  --
--
CENKRSBACKUP  6490   26  0.0222
0.0222
CENNTNFS  BACKUP  6480   15  0.0072
0.0072
RSCH-AS1-PBACKUP  6150   90  7.3412
7.3412
RSCH-DB2-PBACKUP  6140   43  5.6337
5.6337
RSCH-DB3-PBACKUP  60810  0.
0.
RSCH-DB3-PBACKUP  6160  114   1477.5513
1477.5513
RSCH-FS1-PBACKUP  61110  0.
0.
RSCH-FS1-PBACKUP  6180   97 10.3834
10.3834
RSCH-WS5-PBACKUP  6670   29  2.5706
2.5706
RSCH-WS6-PBACKUP  6660   35  5.4812
5.4812
TPRSCHHOME01  BACKUP  62420  0.
0.
TPRSCHHOME01  BACKUP  6270 2467  16412.1675
16412.1675
TPRSCHHOME02  BACKUP  63410  0.
0.
TPRSCHHOME02  BACKUP  6370 3552  19135.1409
19135.1409

Here's the output from a 4.2 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB
Log_MB
  --  -  ---  -  --
--
REMEDY2W  BACKUP  3896   0   64  0.
0.

I only get one line back.. There should be one for each node (about 100
nodes on this server)

Now, for any of you who are wondering..  'Filespace' and 'Stg' are
columns put in just as place holders. We were using the 'q occu' to
generate charge back info.  I needed to generate an sql query would look
Just like the q occu (same columns) so the data could be fed into an
existing program which handled charge Back to the clients.

Regards,

Denis L. L'Huillier
212-647-2168

drive online=no versus path offline=no

[Gerhard Rentschler]

Hello,
with TSM 5.1 one has to define a path for each drive. Both, update drive and
update path have an online option. Is it sufficient to set a drive offline
in a single server environment?
Regards
Gerhard
---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany

Re: Multiple logical libraries for 3584

[Don France]

Gentille,

Sure;  shared library support in 4.2/5.1 is what you would want to
exploit... full details are in the Admin. Guide.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Barkhordar,Gentille,GLENDALE,IS
Sent: Wednesday, August 14, 2002 10:21 AM
To: [EMAIL PROTECTED]
Subject: Re: Multiple logical libraries for 3584


Don,
I have 2 TSM servers accessing a single 3584 library and I would like to set
up multiple control paths to the library so that both servers can access it
equally.  Have you or anyone else done this successfully and do you have any
information on setting it up?
Thanks,
Gentille

-Original Message-
From: Mark D. Rodriguez [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 13, 2002 4:19 PM
To: [EMAIL PROTECTED]
Subject: Re: Multiple logical libraries for 3584


Don France wrote:

>Yep (to the last question);  you cannot span multiple physical libraries to
>make a single logical.  You can define multiple logicals within a single
>physical;  that is a common thing I've done, for various reasons.
>
>
>Don France
>Technical Architect -- Tivoli Certified Consultant
>Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
>San Jose, Ca
>(408) 257-3037
>mailto:[EMAIL PROTECTED]
>
>Professional Association of Contract Employees
>(P.A.C.E. -- www.pacepros.com)
>
>
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
>Dan Foster
>Sent: Tuesday, August 13, 2002 2:14 PM
>To: [EMAIL PROTECTED]
>Subject: Multiple logical libraries for 3584
>
>
>I've got a question.
>
>One 3584-L32 with 6 drives and one 3584-D32 with 6 drives.
>
>Is it possible to have a logical library that covers 4 drives in
>the L32, and a second logical library that covers last 2 drives
>in the L32 and all 6 drives in the D32?
>
>Or is that not a valid configuration -- ie, do I need to keep
>logical libraries from spanning multiple drives in multiple 3584
>units?
>
>-Dan
>
>
Hi Dan,

Judging by your configuration I beleive that you have just one physical
library.  I beleive the L32 is the base unit and the D32 is an expansion
cabinet, i.e. the 2 of them are physicaly attached to one another and
share the same robotics.  Is this correct?  If so then yes you can
partition the library as you described.

But the real question is whatare you trying to accomplish?  If this is
to be connected to 2 different servers there are a few more things that
have to be in place.  If both of these logical libraries are to be used
by the same TSM server I am not sure I understand the rational for doing
so.  You could just as easily manage the drive utilization through other
TSM server options.  Please explain a little bit more what you are
trying to accomplish.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.


===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE

===

LTO Tape Status Full

[Camilo A. Marrugo]

Do anyone ever seen when a tape goes to status full with 0.0% used. And
every time that you try to move the data out of it, it gives you an:

ANR2209W Volume A00060 contains no data.

And if you try to delete the volume it gives you:

ANR2406E DELETE VOLUME: Volume A00060 still contains data.

Any help will be appreciated.

Thanks,
Camilo Marrugo

--
Camilo Marrugo
Backup Solutions Administrator/Sr. Systems Administrator
Dialtone Inc. an Interland Company
[EMAIL PROTECTED] - http://www.dialtone.com
Voice: (954) 581-0097 ext. 130 - Fax: (954) 581-7629
"We are Interland... One Team, One Vision."

Re: Deleting 'specific' EXPORT volumes

[Prather, Wanda]

No, you can't pick and choose.

YOu can:  DELETE VOLHIST TYPE=EXPORT TODATE= etc

So that you delete ONLY the EXPORT tapes and not other stuff, but you can't
delete specific EXPORT tapes.

On the other hand, if you delete the EXPORT tape from the VOLHIST, that
won't prevent you from using the data on an IMPORT, which is how you would
make use of the tape in a DR situation.  (After all, many people use IMPORT
to move data from one TSM server to another server that has never seen the
tape before.)

If the EXPORTed tape is deleted from VOLHIST, it just means you will have to
keep track of that tape manually somehow.  ANd if somebody accidentally
mounts that tape as scratch again (which shouldn't happen if the tape is
offsite), TSM will not prevent you from writing over it.

Also, just FYI, you DO NOT need the DRM license to make COPY POOL tapes.
That is part of the base product.
Many people use copy pool tapes and send them offsite, without having the
DRM product.

The DRM product does the vault management for you - marks the copy pool
tapes as OFFSITE, does the eject (if you want it to) of volumes from the
library, and shows you which tapes are ready to return ONSITE, etc.   It's a
pain in the posterior, but you can do it manually, without DRM.


Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert










-Original Message-
From: Theresa Sarver [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 4:25 PM
To: [EMAIL PROTECTED]
Subject: Deleting 'specific' EXPORT volumes


Hi all;

I was told this week that I had to setup some sort of disaster recovery
ASAP.  As the company never purchased DRM 2 years ago when they implemented
the server, I just decided to export the node as a quick and dirty way to
take care of this request (until DRM get's purchased and installed).

My question is this, I'll be running an export node every Sunday (in the
interim), and these (4) tapes are taken offsite to be returned after 30
days.  However, the last day of the month I am to run an export node, and
these tapes will not be returned for 6 months.

I need to find someway to discriminate between "EXPORT" volumes when
deleting the volhist - as not all of these will be deleted after 30 days.
Is this even possible?  I can't find anyone on adsm.org who's successfully
made this happen...read about lots of people who want to do this though.  :>

Any help would be appreciated.
Thanks - Theresa

Re: Deleting 'specific' EXPORT volumes

[Theresa Sarver]

Thank you s much for all the valuable information Wanda!  No, I didn't know one 
could "manually" do any sort of DRM, and since they've already ordered DRM, I guess I 
don't have to mess with that headache - thank God!!.  :)  

Have a good day;
Theresa
>>> [EMAIL PROTECTED] 08/15/02 11:03AM >>>
No, you can't pick and choose.

YOu can:  DELETE VOLHIST TYPE=EXPORT TODATE= etc

So that you delete ONLY the EXPORT tapes and not other stuff, but you can't
delete specific EXPORT tapes.

On the other hand, if you delete the EXPORT tape from the VOLHIST, that
won't prevent you from using the data on an IMPORT, which is how you would
make use of the tape in a DR situation.  (After all, many people use IMPORT
to move data from one TSM server to another server that has never seen the
tape before.)

If the EXPORTed tape is deleted from VOLHIST, it just means you will have to
keep track of that tape manually somehow.  ANd if somebody accidentally
mounts that tape as scratch again (which shouldn't happen if the tape is
offsite), TSM will not prevent you from writing over it.

Also, just FYI, you DO NOT need the DRM license to make COPY POOL tapes.
That is part of the base product.
Many people use copy pool tapes and send them offsite, without having the
DRM product.

The DRM product does the vault management for you - marks the copy pool
tapes as OFFSITE, does the eject (if you want it to) of volumes from the
library, and shows you which tapes are ready to return ONSITE, etc.   It's a
pain in the posterior, but you can do it manually, without DRM.


Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED] 

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert










-Original Message-
From: Theresa Sarver [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, August 14, 2002 4:25 PM
To: [EMAIL PROTECTED] 
Subject: Deleting 'specific' EXPORT volumes


Hi all;

I was told this week that I had to setup some sort of disaster recovery
ASAP.  As the company never purchased DRM 2 years ago when they implemented
the server, I just decided to export the node as a quick and dirty way to
take care of this request (until DRM get's purchased and installed).

My question is this, I'll be running an export node every Sunday (in the
interim), and these (4) tapes are taken offsite to be returned after 30
days.  However, the last day of the month I am to run an export node, and
these tapes will not be returned for 6 months.

I need to find someway to discriminate between "EXPORT" volumes when
deleting the volhist - as not all of these will be deleted after 30 days.
Is this even possible?  I can't find anyone on adsm.org who's successfully
made this happen...read about lots of people who want to do this though.  :>

Any help would be appreciated.
Thanks - Theresa

Deactivate ALL admin schedules? (how-to)

[Taylor, David]

Hi all,

Is there anyway that I can globally set all of my admin schedules to
"ACTIVE=NO"?

I was looking for something like a standard SQL UPDATE-SET type statement,
but couldn't find anything.

I want to include this in a disaster recovery script (Korn).  The problem
that I've run into is that some of my schedule-names are longer than 16
characters (and therefor wrap).   I could probably write something (ugly and
bulky) that would work around this issue, but would prefer something
cleaner.

Additional info:

TSM server 4.2.1.15
AIX 4.3.3 ML6

TIA

David


**
This email 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 email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Re: Deactivate ALL admin schedules? (how-to)

[Doug Thorneycroft]

>From the Admin command line:
update sch * type=admin active=no

-Original Message-
From:   Taylor, David [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, August 15, 2002 9:09 AM
To: [EMAIL PROTECTED]
Subject:Deactivate ALL admin schedules? (how-to)

Hi all,

Is there anyway that I can globally set all of my admin schedules to
"ACTIVE=NO"?

I was looking for something like a standard SQL UPDATE-SET type statement,
but couldn't find anything.

I want to include this in a disaster recovery script (Korn).  The problem
that I've run into is that some of my schedule-names are longer than 16
characters (and therefor wrap).   I could probably write something (ugly and
bulky) that would work around this issue, but would prefer something
cleaner.

Additional info:

TSM server 4.2.1.15
AIX 4.3.3 ML6

TIA

David


**
This email 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 email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Re: Deactivate ALL admin schedules? (how-to)

[McClean, Frank]

One way is to set the parameter "Disablescheds" to 'yes' in the dsmserv.opt
file
before restarting the TSM server.

Frank
Frank McClean
[EMAIL PROTECTED]


-Original Message-
From: Taylor, David [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 9:09 AM
To: [EMAIL PROTECTED]
Subject: Deactivate ALL admin schedules? (how-to)


Hi all,

Is there anyway that I can globally set all of my admin schedules to
"ACTIVE=NO"?

I was looking for something like a standard SQL UPDATE-SET type statement,
but couldn't find anything.

I want to include this in a disaster recovery script (Korn).  The problem
that I've run into is that some of my schedule-names are longer than 16
characters (and therefor wrap).   I could probably write something (ugly and
bulky) that would work around this issue, but would prefer something
cleaner.

Additional info:

TSM server 4.2.1.15
AIX 4.3.3 ML6

TIA

David


**
This email 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 email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Re: Deactivate ALL admin schedules? (how-to)

[Don France]

The DRM script includes a change to dsmserv.opt ---
disablescheds yes

This ensures that ALL schedules are disabled when preparing the DR site
configuration.  You just add to the bottom of the file, before starting the
TSM server.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Taylor, David
Sent: Thursday, August 15, 2002 9:09 AM
To: [EMAIL PROTECTED]
Subject: Deactivate ALL admin schedules? (how-to)


Hi all,

Is there anyway that I can globally set all of my admin schedules to
"ACTIVE=NO"?

I was looking for something like a standard SQL UPDATE-SET type statement,
but couldn't find anything.

I want to include this in a disaster recovery script (Korn).  The problem
that I've run into is that some of my schedule-names are longer than 16
characters (and therefor wrap).   I could probably write something (ugly and
bulky) that would work around this issue, but would prefer something
cleaner.

Additional info:

TSM server 4.2.1.15
AIX 4.3.3 ML6

TIA

David


**
This email 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 email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Re: SQL timestamp not working when upgraded to 4.2.2 for summary tabl e

[L'Huillier, Denis]

Hey look what I found...

*
$$4225 Interim fixes delivered by patch 4.2.2.5
$$Patches are cumulative, just like PTFs.  So Interim fixes
$$delivered as "4.2.2.5" include those delivered in previous patches
*
<@>
IC33455 SUMMARY TABLE NOT BEING FULLY UPDATED


And I'm querying the summary table..

Thanks..

-Original Message-
From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 11:34 AM
To: [EMAIL PROTECTED]
Subject: Re: SQL timestamp not working when upgraded to 4.2.2 for summary tabl e


Hi Denis,

Just for information : I tested your query on my system (4.2.2.15) and
it worked like a charm (except I had to modify "Node Name" to
"Node_Name")

Did you apply the latest PTF's to get 4.2.2.15 ? Maybe it could help ...
Good luck anyway !

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-Original Message-
From: L'Huillier, Denis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 15 August, 2002 15:39
To: [EMAIL PROTECTED]
Subject: SQL timestamp not working when upgraded to 4.2.2 for summary
tabl e


Hello -
Since I upgraded our 4.1 server to 4.2.2 my sql query against the
summary table no longer works. Has anyone run into this problem before?
Here's the query...

/* --- Query Summary Table  */
/* ---   Run as a macro   - */
select cast(entity as varchar(12)) as "Node Name", \ cast(activity as
varchar(10)) as Type, \ cast(number as varchar(8)) "Filespace", \
cast(failed as varchar(3)) "Stg", \ cast(affected as decimal(7,0)) as
files, \ cast(bytes/1024/1024 as decimal(12,4)) as "Phy_MB", \
cast(bytes/1024/1024 as decimal(12,4)) as "Log_MB" \ from summary where
end_time>=timestamp(current_date -1 days, '09:00:00') \ and
end_time<=timestamp(current_date, '08:59:59') \ and (activity='BACKUP'
or activity='ARCHIVE') \ order by "Node Name"

Here's the output from a 4.1 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB
Log_MB
  --  -  ---  -  --
--
CENKRSBACKUP  6490   26  0.0222
0.0222
CENNTNFS  BACKUP  6480   15  0.0072
0.0072
RSCH-AS1-PBACKUP  6150   90  7.3412
7.3412
RSCH-DB2-PBACKUP  6140   43  5.6337
5.6337
RSCH-DB3-PBACKUP  60810  0.
0.
RSCH-DB3-PBACKUP  6160  114   1477.5513
1477.5513
RSCH-FS1-PBACKUP  61110  0.
0.
RSCH-FS1-PBACKUP  6180   97 10.3834
10.3834
RSCH-WS5-PBACKUP  6670   29  2.5706
2.5706
RSCH-WS6-PBACKUP  6660   35  5.4812
5.4812
TPRSCHHOME01  BACKUP  62420  0.
0.
TPRSCHHOME01  BACKUP  6270 2467  16412.1675
16412.1675
TPRSCHHOME02  BACKUP  63410  0.
0.
TPRSCHHOME02  BACKUP  6370 3552  19135.1409
19135.1409

Here's the output from a 4.2 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB
Log_MB
  --  -  ---  -  --
--
REMEDY2W  BACKUP  3896   0   64  0.
0.

I only get one line back.. There should be one for each node (about 100
nodes on this server)

Now, for any of you who are wondering..  'Filespace' and 'Stg' are
columns put in just as place holders. We were using the 'q occu' to
generate charge back info.  I needed to generate an sql query would look
Just like the q occu (same columns) so the data could be fed into an
existing program which handled charge Back to the clients.

Regards,

Denis L. L'Huillier
212-647-2168

IBM vs. Storage Tek

[Joni Moyer]

Hello,

I know I've asked about this before, but now I have more information so I
hope someone out there has done this.  Here is my environment for TSM.
Right now it is on the mainframe and we are using 3590 Magstars.  We have a
production and a test TSM server and each has about 13 drives and a total
of 5,500 tapes used for onsite and offsite tape pools between the 2
systems.  Two scenarios are being considered (either way TSM is being moved
onto our SAN environment with approximately 20 SAN backup clients and 250
LAN backup clients and will be on SUN servers instead of the mainframe)
Here is what I estimated I would need for tapes:

 3590 9840 9940A LTO
 10 GB 20 GB 60 GB 100 GB
Production
Onsite1375 689  231  140
Offsite   1600 800  268  161
Total 2975 1489 499  301

Test
Onsite963  483  163  101
Offsite   1324 664  223  135
Total 2287 1147 386  236

Grand
Total 5262 2636 885  537

1. IBM's solution is to give us a 3584 library with 3 frames and use LTO
tape drives.  This only holds 880 tapes and from my calculations I will
need about 600 tapes plus enough tapes for a scratch pool.  My concern is
that LTO cannot handle what our environment needs.  LTO holds 100 GB
(native), but when a tape is damaged or needs to be reclaimed the time it
takes to do either process would take quite some time in my estimation.
Also, I was told that LTO is good for full volume backups and restores, but
that it has a decrease in performance when doing file restores, archives
and starting and stopping of sessions, which is a majority of what our
company does with TSM.  Has anyone gone from a 3590 tape to LTO?  Isn't
this going backwards in performance and reliability?  Also, with
collocation, isn't a lot of tape space wasted because you can only put one
server  per volume?

2. STK 9840B midpoint load(20 GB) or 9940A(60 GB) in our Powderhorn silo
that would be directly attached to the SAN.  From what I gather, these
tapes are very robust like the 3590's, but the cost for this solution is
double IBM's LTO.  We would also need Gresham licenses for all of the SAN
backed up clients(20).

Does anyone know of any sites/contacts that could tell me the
advantages/disadvantages of either solution?  Any opinions would be greatly
appreciated.
Thanks


Joni Moyer
Associate Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: More on mount points

[David Longo]

For each device class there is a "Mount limit", generally this
is set to DRIVES, which allows that devclass to use as many drives
as you have.  Maybe yours is set to a specific number.  Each tape
pool you have, then uses a devclass and therefore is limited to
using no more than that many drives.

David Longo

>>> [EMAIL PROTECTED] 08/15/02 09:05AM >>>
Can anyone give me any help on the mountpoint problem I posted earlier?

>>I turned on collocation last week and now I am getting this message:
>>
>>ANR1082W Space reclamation terminated for volume 4A0023 - insufficient
number of mount points >>available for removable media.
>>
>>I looked up the error message and it tells me:User Response: If necessary,
make more mount points available
>>
>>Is this the same as mount limit for the server?  I see that you can
specify number of mount points for a
>>node.  But how can you specify this for a tape?

David Mac



"MMS " made the following
 annotations on 08/15/2002 09:32:02 AM
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: Win2k system state restore

[Seay, Paul]

The Tivoli Knowledge base does not have everything.  IBMLINK does.  You have
to have a userid to look at that information.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-Original Message-
From: Frost, Dave [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 5:15 AM
To: [EMAIL PROTECTED]
Subject: Re: Win2k system state restore


Jim,

Thanks for that.  But...

A lookup in the tivoli/support/knowledgebase/ for apar ic34015 returns 0
records.  Nor is it documented in the readmes for the 4.2 or 5.1 client in
"maintenance" or "patches" at boulder.

It would seem that this apar is not publically available.


  regards,

-=Dave=-
--
+44 (0)20 7608 7140

Know thyself.  If you need help, call the C.I.A.



-Original Message-
From: Jim Smith [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 11:55 PM
To: [EMAIL PROTECTED]
Subject: Re: Win2k system state restore


Dave,

The TSM B-A client does have a facility to not replace the hardware
dependent driver information during a system object restore.  Let me
explain:

The traditional method backup/restore of the registry was for the backup
product to export the registry files and backup the exported files.  For
restore, the backup product would simply then restore the files to a staging
area and import the information back into the registry (the activation of
the registry, if you will).  This was a pretty simple exercises for a backup
product.

When Windows 2000 arrived Microsoft changed the procedure a bit and
introduced the registry key:
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore.
The basic procedure now is the backup product restores the registry
information to the staging area (as before) but now is required to move
information from the current registry (these KeysNotToRestore) over the
information that was just restored and then activate the registry. This is
basically allowing information in the current registry to be preserved
across a restore and reboot.  Systems like Active Directory rely on this as
they write information about the log reply into the current registry which
would otherwise be overwritten by the restored copy of the registry and not
available after the reboot.  Another system which exploits this is the Plug
& Play subsystem which describes the hardware dependent driver information
about which you are inquiring.  This subsystem preserves the information in
the HKLM\SYSTEM\CurrentControlSet\Enum portion of the registry among other
things.

While TSM uses the procedures that Microsoft outlines regarding registry
restoration, we found that by default the administrator doesn't have the
proper permissions to write into Enum branch.  This information is well
documented in APAR IC34015.  The APAR will be fixed in TSM 5.1.5; a simple
work around involving using regedit to grant the proper permissions is
documented in the APAR if you are using the TSM 4.2.2 client or TSM 5.1.0
client.

Having said all this, I caution that Microsoft does not guarantee that you
can always restore from hardware a to hardware b.  If you are using
Ntbackup.exe, then it would be safe for me to say that if your particular
environment can be brought back by Ntbackup.exe then TSM should be able to
do it as well.

Hope this helps,
Jim Smith
TSM Development

>>>

Dear All,

Does anybody know if there is any plan in future releases of the TSM client
for W2K, to implement a facility to not replace the hardware dependent
driver information during a system object restore.

My reason for asking ;

We have a requirement to fully restore a W2K server back to different
hardware (ie. different RAID controller and/or different processor
architecture)
At present, our solution is to use NTBACKUP to backup the system state and
TSM to backup the remainder.

NTBACKUP is intelligent enough to not restore hardware dependent drivers
back onto a platform that is different. I cannot get TSM to emulate this.

The above solution is OK, but I am backing up the WINNT directory with TSM
as flat files, then I am backing up the System Object with TSM and finally
backing up the flat file generated by the NTBACKUP system state operation.

It all seems a bit needless really. ( I know I could exlude WINNT but as yet
I don't know of any way to exclude the systemobject).

Any thoughts or knowledge of future client releases would be welcome.

Thanks

regards,

-=Dave=-
--
+44 (0)20 7608 7140

"I'll be Bach." - Johann Sebastian Schwarzenegger



www.guardianit.com

The information contained in this email is confidential and intended only
for the use of the individual or entity named above.  If the reader of this
message is not the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is strictly
prohibited.  Guardian iT Group will accept no responsibility or liability in
respect to this email other than to the addressee.  If you have received
this communication in error, please

"FW: sql and output redirection...how to..RE: Deactivate ALL admi n sch edules? (how-to)"

[Williams, Tim P {PBSG}]

retrying posting...
"
-Original Message-
From: Williams, Tim P {PBSG}
Sent: Thursday, August 15, 2002 1:37 PM
To: 'ADSM: Dist Stor Manager'
Subject: sql and output redirection...how to..RE: Deactivate ALL admin
sch edules? (how-to)


set sqldisplaymode wide
tsm: ADSM>select 'update schedule ' || trim(schedule_name) || ' type=a
active=no ' from admin_schedules

Unnamed[1]

update schedule AM_BACKUP_DB_FULL type=a active=no
update schedule AUDIT_LICENSES type=a active=no
update schedule BACKUP_DEVCONFIG_1 type=a active=no
update schedule BACKUP_DEVCONFIG_2 type=a active=no
update schedule BACKUP_DEVCONFIG_3 type=a active=no
update schedule BACKUP_DEVCONFIG_4 type=a active=no
update schedule BACKUP_VOLHIST_1 type=a active=no

and output redirect...then execute...

FYI Thanks Tim
"


-Original Message-
From: Taylor, David [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 11:09 AM
To: [EMAIL PROTECTED]
Subject: Deactivate ALL admin schedules? (how-to)


Hi all,

Is there anyway that I can globally set all of my admin schedules to
"ACTIVE=NO"?

I was looking for something like a standard SQL UPDATE-SET type statement,
but couldn't find anything.

I want to include this in a disaster recovery script (Korn).  The problem
that I've run into is that some of my schedule-names are longer than 16
characters (and therefor wrap).   I could probably write something (ugly and
bulky) that would work around this issue, but would prefer something
cleaner.

Additional info:

TSM server 4.2.1.15
AIX 4.3.3 ML6

TIA

David


**
This email 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 email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Réf. : IBM vs. Storage Tek

[Guillaume Gilbert]

Hi Joni

What you wrote sums it up in terms of performance and reliability. I think the same 
way you do as far as LTO goes. It is very good for small enterprises and full backups.
But I don't think it fits TSM very well, espacially in a large environnement like 
yours. Almost everyday I talk about it to our analysts  so I won't have to support a
large TSM server (400 clients) with those tapes. My 9840a's are very good. The B's are 
even better. The Gresham solution is easier to implement in a lanless backup
strategy. Compare the cost of DTELM licencing to that of TSM Library Sharing. I don't 
have any figures but I bet the two are pretty close.

Sure with STK tapes you'll have more tapes but a Powderhorn can take it. Before the 
9840, we had over 3000 EE-tapes (1.6GB native) in our Powderhorn just for TSM with
only 4 drives. I was doing reclamation by copying the tapes to disk storage pool. With 
the 9840 I reclaim at 40% and do about 30 a day starting at 9:30 and it usually
finishes before I get off work. In 1 year I had 1 (one) tape failure and no drive 
failures. That's pretty reliable. I'm thinking the 3590 is as reliable.

Remember, you always get what you pay for.

Guillaume Gilbert
CGI Canada




Joni Moyer <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-08-15 09:29:48

Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Envoyé par :   "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


Pour :[EMAIL PROTECTED]
cc :
Objet :   IBM vs. Storage Tek

Hello,

I know I've asked about this before, but now I have more information so I
hope someone out there has done this.  Here is my environment for TSM.
Right now it is on the mainframe and we are using 3590 Magstars.  We have a
production and a test TSM server and each has about 13 drives and a total
of 5,500 tapes used for onsite and offsite tape pools between the 2
systems.  Two scenarios are being considered (either way TSM is being moved
onto our SAN environment with approximately 20 SAN backup clients and 250
LAN backup clients and will be on SUN servers instead of the mainframe)
Here is what I estimated I would need for tapes:

 3590 9840 9940A LTO
 10 GB 20 GB 60 GB 100 GB
Production
Onsite1375 689  231  140
Offsite   1600 800  268  161
Total 2975 1489 499  301

Test
Onsite963  483  163  101
Offsite   1324 664  223  135
Total 2287 1147 386  236

Grand
Total 5262 2636 885  537

1. IBM's solution is to give us a 3584 library with 3 frames and use LTO
tape drives.  This only holds 880 tapes and from my calculations I will
need about 600 tapes plus enough tapes for a scratch pool.  My concern is
that LTO cannot handle what our environment needs.  LTO holds 100 GB
(native), but when a tape is damaged or needs to be reclaimed the time it
takes to do either process would take quite some time in my estimation.
Also, I was told that LTO is good for full volume backups and restores, but
that it has a decrease in performance when doing file restores, archives
and starting and stopping of sessions, which is a majority of what our
company does with TSM.  Has anyone gone from a 3590 tape to LTO?  Isn't
this going backwards in performance and reliability?  Also, with
collocation, isn't a lot of tape space wasted because you can only put one
server  per volume?

2. STK 9840B midpoint load(20 GB) or 9940A(60 GB) in our Powderhorn silo
that would be directly attached to the SAN.  From what I gather, these
tapes are very robust like the 3590's, but the cost for this solution is
double IBM's LTO.  We would also need Gresham licenses for all of the SAN
backed up clients(20).

Does anyone know of any sites/contacts that could tell me the
advantages/disadvantages of either solution?  Any opinions would be greatly
appreciated.
Thanks


Joni Moyer
Associate Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[David Longo]

That was my question, what will it do?  What are the plus and
minuses of changing it?  What resources is it for?

Don't have much log pin problem on this server.

David Longo

>>> [EMAIL PROTECTED] 08/15/02 09:42AM >>>
Just be aware of what lengthening the RESOURCETIMEOUT will do, especially if
you are susceptible to "logpinned" conditions due to slow, long-running
sessions.




-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, August 15, 2002 8:17 AM
To: [EMAIL PROTECTED] 
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Richard,
I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is
set to 10.  Looked at manuals and see this is a new option with 4.2.
There is only a small paragraph about this.  What RESOURCES is this
talking about and what are the implications of changing?

It's probably not tape mounts as I can have a process waiting on a tape
that's being used by another process for well over 10 minutes. (No problem
with that, just know it doesn't apply to tape mounts.)

David Longo

>>> [EMAIL PROTECTED] 08/15/02 08:47AM >>>
I had the same problem after upgrading from 3.74 tp 5.11 on AIX 4.3. The fix
is to change the resource time out in the TSM server's dsmserv.opt file to
60 the default is 10. Hope this helps you out.

Senior TSM consultant

Richard Menides

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, August 15, 2002 7:38 AM
To: [EMAIL PROTECTED] 
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED] 
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED] 
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED] 
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]] 
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED] 
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the following error message after issuing an update
> storage pool command:
>
>
> ANRD SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
> SS
> universe lock.
> ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
> ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.
>
>  This condition seems to occur when we are in a heavy backup period, which
> since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
> upgrading to that release, we applied the 4.2.1.15 fix level at the
> recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
> running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?
>
>  Thanks for  any input.
>
>  - Brian
>

SQL timestamp not working when upgraded to 4.2.2 for summary tabl e

[L'Huillier, Denis]

Hello -
Since I upgraded our 4.1 server to 4.2.2 my sql query against the summary table no 
longer works.
Has anyone run into this problem before?
Here's the query...

/* --- Query Summary Table  */
/* ---   Run as a macro   - */
select cast(entity as varchar(12)) as "Node Name", \
cast(activity as varchar(10)) as Type, \
cast(number as varchar(8)) "Filespace", \
cast(failed as varchar(3)) "Stg", \
cast(affected as decimal(7,0)) as files, \
cast(bytes/1024/1024 as decimal(12,4)) as "Phy_MB", \
cast(bytes/1024/1024 as decimal(12,4)) as "Log_MB" \
from summary where end_time>=timestamp(current_date -1 days, '09:00:00') \
and end_time<=timestamp(current_date, '08:59:59') \
and (activity='BACKUP' or activity='ARCHIVE') \
order by "Node Name"

Here's the output from a 4.1 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB  Log_MB
  --  -  ---  -  --  --
CENKRSBACKUP  6490   26  0.0222  0.0222
CENNTNFS  BACKUP  6480   15  0.0072  0.0072
RSCH-AS1-PBACKUP  6150   90  7.3412  7.3412
RSCH-DB2-PBACKUP  6140   43  5.6337  5.6337
RSCH-DB3-PBACKUP  60810  0.  0.
RSCH-DB3-PBACKUP  6160  114   1477.5513   1477.5513
RSCH-FS1-PBACKUP  61110  0.  0.
RSCH-FS1-PBACKUP  6180   97 10.3834 10.3834
RSCH-WS5-PBACKUP  6670   29  2.5706  2.5706
RSCH-WS6-PBACKUP  6660   35  5.4812  5.4812
TPRSCHHOME01  BACKUP  62420  0.  0.
TPRSCHHOME01  BACKUP  6270 2467  16412.1675  16412.1675
TPRSCHHOME02  BACKUP  63410  0.  0.
TPRSCHHOME02  BACKUP  6370 3552  19135.1409  19135.1409

Here's the output from a 4.2 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB  Log_MB
  --  -  ---  -  --  --
REMEDY2W  BACKUP  3896   0   64  0.  0.

I only get one line back.. There should be one for each node (about 100 nodes on this 
server)

Now, for any of you who are wondering..  'Filespace' and 'Stg' are columns put in just 
as place holders.
We were using the 'q occu' to generate charge back info.  I needed to generate an sql 
query would look
Just like the q occu (same columns) so the data could be fed into an existing program 
which handled charge
Back to the clients.

Regards,

Denis L. L'Huillier
212-647-2168

unsubscribe

[Wolf, Dr. Stefan]

[EMAIL PROTECTED]

Upgrade from 3590E to 3590H

[Mahesh Tailor]

Hello, everyone.

Platform: IBM pSeries 6M1
OS: AIX 4.3.3.10
TSM: 5.1.1.1
Atape: 7.0.7.0
atldd: 5.0.7.0

I am getting ready to perform an upgrade from 3590E to 3590H drives in
my 3494.  Each of the 6-drives is directly fiber-channel attached to the
TSM server.

Has anyone gone through an upgrade such as this?  If so, can you share
you experience with me?  I guess, what I am looking for is the steps in
TSM and AIX that I need to go through to successfully do this.

TIA

Mahesh

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[MC Matt Cooper (2838)]

IBM responded to my problem log saying the problem is identified with APAR
IC34292 and the associated fixes should be available next week, (if there
testing goes well).  Maybe a little longer for us mainframers because of
packaging.
 Matt

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 9:23 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server

The default changed from 10 minutes to 60 minutes with TSM 5.1.
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> David Longo
> Sent: Thursday, August 15, 2002 3:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Richard,
> I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is
> set to 10.  Looked at manuals and see this is a new option with 4.2.
> There is only a small paragraph about this.  What RESOURCES is this
> talking about and what are the implications of changing?
>
> It's probably not tape mounts as I can have a process waiting on a tape
> that's being used by another process for well over 10 minutes.
> (No problem
> with that, just know it doesn't apply to tape mounts.)
>
> David Longo
>
> >>> [EMAIL PROTECTED] 08/15/02 08:47AM >>>
> I had the same problem after upgrading from 3.74 tp 5.11 on AIX
> 4.3. The fix
> is to change the resource time out in the TSM server's dsmserv.opt file to
> 60 the default is 10. Hope this helps you out.
>
> Senior TSM consultant
>
> Richard Menides
>
> -Original Message-
> From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Hello,
> this is obviously a known problem. See the discussion a few days earlier
> with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
> I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
> 5.1.1.2. This didn't change anything. Then I had to supply diagnostic
> information. According to the web interface to Tivoli problem
> management the
> problem was closed on August 6th without any further information.
> I haven't
> got any new information since  this day.
> Best regards
> Gerhard
>
> ---
> Gerhard Rentschleremail:[EMAIL PROTECTED]
> Regional Computing Center tel.   ++49/711/685 5806
> University of Stuttgart   fax:   ++49/711/682357
> Allmandring 30a
> D 70550
> Stuttgart
> Germany
>
>
>
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> > MC Matt Cooper (2838)
> > Sent: Thursday, August 15, 2002 1:22 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
> >
> >
> > Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> > This morning I
> > am looking at my EXPIRATION process was hung and a backup of
> local tape to
> > the copytape is hung and it all started with very similar message..
> > Matt
> > ANR0538I A resource waiter has been aborted.
> >
> > ANR0538I A resource waiter has been aborted.
> >
> > ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
> >
> > ANR0538I A resource waiter has been aborted.
> >
> > ANR0538I A resource waiter has been aborted.
> >
> > ANRD IMFS(3566): ThreadId<656> Lock conflict error in
> obtaining sLock
> > for
> > ANRD node 499, filespace 35
> >
> > ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> > processed
> > ANR0986I 3603 items for a total of 970,174,464 bytes with a
> > completion state
> > of
> > ANR0986I FAILURE at 06:06:44.
> >
> > ANRD IMFS(3566): ThreadId<662> Lock conflict error in
> obtaining sLock
> > for
> > ANRD node 499, filespace 35
> >
> >
> > -Original Message-
> > From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 15, 2002 2:25 AM
> > To: [EMAIL PROTECTED]
> > Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
> >
> > Good morning...
> >
> > Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> > Going to take it up with support.
> >
> > Regards Niklas
> >
> > -Ursprungligt meddelande-
> > Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> > Skickat: den 14 augusti 2002 16:16
> > Till: [EMAIL PROTECTED]
> > Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
> >
> > Good morning,
> >
> >  We are running TSM 4.2.1.15 on OS/390 2.10 and are having
> several issues.
> > One of these is poor performance since upgrading from 4.2.2.0
> to 4.2.1.15.
> > Also we are receiving the following error message after issuing
> an update
> > storage pool command:
> >
> >
> > ANRD SSUT

Re: Antwort: Web Admin Interface - grrr

[Prather, Wanda]

Look at all the responses on this thread, and what you see is that we are
all discussing ways we GET AROUND the admin web interface.
That should be indication enough to the developers that the product has a
problem.

Telling prospective TSM customers that "oh yeah don't worry, there are
plenty of ways AROUND the limitations in the admin interface", isn't exactly
a prime selling point.


-Original Message-
From: Kai Hintze [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 12:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Antwort: Web Admin Interface - grrr


But it is precisely because I _do_ have boatloads of clients that I prefer
the CLI. I can type "2 or 3 lines of parameters" as someone said a few
messages back much more quickly than I can
  

More, I seldom type long parameters. I have samples of anything I have
defined/updated/deleted that I can quickly copy to a text editor, change the
few characters that change, and dump into a CLI session. I specify
everything so that if the defaults change they don't take me by surprise,
and I seldom have to look back to the manuals find a syntax. The only trick
is when I change versions I do have to go through the list and compare to
the new Admin Reference.

- Kai.

> -Original Message-
> From: Kauffman, Tom [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 13 August 2002 8:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Antwort: Web Admin Interface - grrr
>
>
> I'm afraid I'm another vote for the CLI.

 . . .
>
> But I don't have boatloads of clients to administer, so I'm
> probably not
> seeing the issues the rest of you are fighting. :-)
>
> Tom Kauffman
> NIBCO, Inc
>

Re: Upgrading TSM from 3.7.x to 5.1.xx

[Gerhard Rentschler]

Do you want to upgrade a server or a client?
Regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Halvorsen Geirr Gulbrand
> Sent: Thursday, August 15, 2002 3:38 PM
> To: [EMAIL PROTECTED]
> Subject: Upgrading TSM from 3.7.x to 5.1.xx
>
>
> Hello all of You!
>
> I'm about to do an upgrade of TSM from version 3.7.x to version 5.1.x
> I know that upgrading from 3.7 to 4.1 required running a special
> tool called
> tsmfixup.cmd.
> Are there any consideration like these or other things I have to be aware
> of?
>
> Any help highly appreciated!
>
> Best Regards
> Geirr G. Halvorsen

Re: Bad performance from tape to tape

[Vos, F (Freek)]

Hi Bill,

Reclamation is not only a tape to tape copy.
The changes to the TSM database are they holding down your speed ?
The amount of tape mounts, are there many ?
Do the disks and the tapeunits share the same SCSI adapter ?

Groet,

Freek.


-Original Message-
From: Bill Boyer [mailto:[EMAIL PROTECTED]]
Sent: donderdag 15 augustus 2002 17:15
To: [EMAIL PROTECTED]
Subject: Re: Bad performance from tape to tape


The tape-to-tape operation that is adversely affected is reclamation. If the
primay location of a file is in a random access disk pool, then TSM does not
'batch' the files together. Each transaction is a single file. The primary
location can be a disk sequential access pool, but not random access. We
originally came across this with DIRMC. We had the primary a DISK pool and
then only created the copypool. The reclamation on the copypool tapes used
to take days. Opened a PMR with Tivoli and got the 'working as designed'
answer.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Joe Pendergast
Sent: Thursday, August 15, 2002 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Bad performance from tape to tape


Is the disk pool cached?
I ran into a situation where the disk pool cache instead of tape was being
used.
This slowed my LTO drives to a crawl during certain operations.
I now varyoff the disk pools before I run the process with expected results
Don't forget to vary them back on at the end..
Note: the disk pool cache is a great help in restore time, but it can
adversely
the affect of what should be a tape to tape process.





Halvorsen Geirr Gulbrand <[EMAIL PROTECTED]> on 08/15/2002 03:00:23 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: Joseph Pendergast/Corona/Watson)

Subject:  Bad performance from tape to tape



Hi All,
I have a performance problem when doing Space-Reclaamtion, or backup storage
pool, when TSM is copying data from one tape drive to the other.
Environment:
Windows 2K server, TSM 4.2.1.15.
Library, Compaq MSL5026, with 2 SDLT drives (Single Module Library).
SCSI Controller, Compaq 64-bit/66Mhz Dual Channel Wide Ultra3 SCSI Adapter
(Compaq version of Adaptec 39160)

Moving data from Disk to Tape runs with expected speed (8-10 MB/s).

>From Tape to tape speed is around 2MB/s. (50GB takes about 7-8hours.)

Does anyone know why? It is killing my daily operations.

Mvh
Geirr G. Halvorsen
TSM Enterprise Backup Specialist
WMdata Danmark A/S

==
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
==
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.


==

NDS (Netware 5.x)

[Mark Hayden]

Hi all, wanted to know if anyone has done any retores from NDS. We have a NetWare 
admin that butchered the Login script from a NetWare Server under the NDS tree. I was 
wondering what the name of this login script would be called in NDS.Cn=  
Thanks

Thanks, Mark Hayden
Informations Systems Analyst
E-Mail:  [EMAIL PROTECTED]

Réf. : Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Guillaume Gilbert]

I've been running 4.2.2.6 for a few weeks on Z/OS and I haven't seen any problems. DB 
is a little under 10 GB. On AIX I have 3 servers running 4.2.2.8 without these
problems. DBs are 500 MBs, 5 GBs and 22 GBs. The 22 GB (79% used) took 53 minutes this 
morning with the following report :

 ANR0812I Inventory file expiration process 246 completed:
  examined 3847974 objects, deleting 81979 backup objects,
  4180 archive objects, 0 DB backup volumes, and 0 recovery
  plan files. 0 errors were encountered.

The longest its run since the upgrade is 90 minutes. The server is a F80 with 4 
processers and 1,5 GB of ram. Another small TSM server runs on it too (700 MB DB). The 
DB
sits on a Hitachi 7700E subsystem with 15 GB disks (10K rpm) in RAID5. Dual fiber 
through an Inrange Director. I have 4 dbv of 6,8 GBs all on the same array on the
subsystem. Haven't had a performance problem (on the DB) since we've had this config a 
little over a year ago.

I had installed 4.2.1.15 on Z/OS but ran into a problem with the q assoc command which 
would abend the server. 4.2.2.6 looks pretty stable to me.

Guillaume Gilbert
CGI Canada




"Jolliff, Dale" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-08-15 08:26:37

Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Envoyé par :   "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


Pour :[EMAIL PROTECTED]
cc :
Objet :   Re: ANR message Lock acquisition - TSM 4.2.1.15 server

4.2.2.x servers on AIX are exhibiting the same problems, along with numerous
others.
Oddly enough, our 4.2.1.15 Solaris servers seem to be operating relatively
smoothly.
Note that I said "relatively" and they all have very small DB.

We have an open crit-sit with IBM/Tivoli on an AIX 4.2.2.x server -
We eventually suffered enough DB corruption that we were forced to rebuild
the server and we are in the process of recovering what archives we can from
the old server and importing it into the new server.

This isn't to say that the lock issues caused the corruption, I believe the
corruption was there when we upgraded to 4.2 - the issues that came along
with 4.2 exacerbated the long list of problems we already had.

All in all, if I had it to do over again, I would definitely wait on moving
to 4.2.2.x in production.




-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 6:38 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED]
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED]
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good

Sanergy

[David Gratton]

Hi Everyone, I know this is a TSM support group but I figure some of you must be
using SANERGY for LanFree to disk purposesAnyway my MDC is a WINDOWS2000
system , exporting the drives with NFS MaestroMy Sanergy host is AIX
4.3.3...I was able to mount the drives on my AIX box and even write a file to
the driveMy problem is when I go to fuse the filesystems I simply get a
message saying

Enter Command: fuse|/sanergy/volume1
++
Processing command - fuse|/sanergy/volume1...
Error not defined
|Error not defined
 1. [].
==

Enter Command:



Anyone with any Sanergy experience that could help me would be
appreciatedThanks


Dave Gratton
IBM Global Services

Re: More on mount points

[Williams, Tim P {PBSG}]

I had some issues with mount points not being available.
I also have my mount limit set to drives.
I ended up recycling my tsm server process and this
cleared the situation...
FYI

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 8:31 AM
To: [EMAIL PROTECTED]
Subject: Re: More on mount points


For each device class there is a "Mount limit", generally this
is set to DRIVES, which allows that devclass to use as many drives
as you have.  Maybe yours is set to a specific number.  Each tape
pool you have, then uses a devclass and therefore is limited to
using no more than that many drives.

David Longo

>>> [EMAIL PROTECTED] 08/15/02 09:05AM >>>
Can anyone give me any help on the mountpoint problem I posted earlier?

>>I turned on collocation last week and now I am getting this message:
>>
>>ANR1082W Space reclamation terminated for volume 4A0023 - insufficient
number of mount points >>available for removable media.
>>
>>I looked up the error message and it tells me:User Response: If necessary,
make more mount points available
>>
>>Is this the same as mount limit for the server?  I see that you can
specify number of mount points for a
>>node.  But how can you specify this for a tape?

David Mac



"MMS " made the following
 annotations on 08/15/2002 09:32:02 AM

--
This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify the
sender.  You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where the
message states such views or opinions are on behalf of a particular entity;
and (2) the sender is authorized by the entity to give such views or
opinions.


==

Re: Réf. : IBM vs. Storage Tek

[Joni Moyer]

Thank you for the input!  Every bit of information helps and your
experiences help me to justify going with STK's 9840 solution.  Thanks

Joni Moyer
Associate Systems Programmer
[EMAIL PROTECTED]
(717)975-8338


   
  
Guillaume Gilbert  
  
 cc: 
  
Sent by: "ADSM: Dist   Subject: Réf. : IBM vs. Storage 
Tek   
Stor Manager"  
  
<[EMAIL PROTECTED]> 
  
   
  
   
  
08/15/2002 03:14 PM
  
Please respond to "ADSM:   
  
Dist Stor Manager" 
  
   
  
   
  




Hi Joni

What you wrote sums it up in terms of performance and reliability. I think
the same way you do as far as LTO goes. It is very good for small
enterprises and full backups.
But I don't think it fits TSM very well, espacially in a large
environnement like yours. Almost everyday I talk about it to our analysts
so I won't have to support a
large TSM server (400 clients) with those tapes. My 9840a's are very good.
The B's are even better. The Gresham solution is easier to implement in a
lanless backup
strategy. Compare the cost of DTELM licencing to that of TSM Library
Sharing. I don't have any figures but I bet the two are pretty close.

Sure with STK tapes you'll have more tapes but a Powderhorn can take it.
Before the 9840, we had over 3000 EE-tapes (1.6GB native) in our Powderhorn
just for TSM with
only 4 drives. I was doing reclamation by copying the tapes to disk storage
pool. With the 9840 I reclaim at 40% and do about 30 a day starting at 9:30
and it usually
finishes before I get off work. In 1 year I had 1 (one) tape failure and no
drive failures. That's pretty reliable. I'm thinking the 3590 is as
reliable.

Remember, you always get what you pay for.

Guillaume Gilbert
CGI Canada




Joni Moyer <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-08-15 09:29:48

Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Envoyé par :   "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


Pour :[EMAIL PROTECTED]
cc :
Objet :   IBM vs. Storage Tek

Hello,

I know I've asked about this before, but now I have more information so I
hope someone out there has done this.  Here is my environment for TSM.
Right now it is on the mainframe and we are using 3590 Magstars.  We have a
production and a test TSM server and each has about 13 drives and a total
of 5,500 tapes used for onsite and offsite tape pools between the 2
systems.  Two scenarios are being considered (either way TSM is being moved
onto our SAN environment with approximately 20 SAN backup clients and 250
LAN backup clients and will be on SUN servers instead of the mainframe)
Here is what I estimated I would need for tapes:

 3590 9840 9940A LTO
 10 GB 20 GB 60 GB 100 GB
Production
Onsite1375 689  231  140
Offsite   1600 800  268  161
Total 2975 1489 499  301

Test
Onsite963  483  163  101
Offsite   1324 664  223  135
Total 2287 1147 386  236

Grand
Total 5262 2636 885  537

1. IBM's solution is to give us a 3584 library with 3 frames and use LTO
tape drives.  This only holds 880 tapes and from my calculations I will
need about 600 tapes plus enough tapes for a scratch pool.  My concern is
that LTO cannot handle what our environment needs.  LTO holds 100 GB
(native), but when a tape is damaged or needs to be reclaimed the time it
takes to do either process would take quite some time in my estimation.
Also, I was told that LTO is good for full volume backups and restores, but
that it has a decrease in performance when doing file restores, archives
and starting and stopping of sessions, which is a majority of what our
company does with TSM.  Has anyone gone from a 3590 tape to LTO?

Eternal Data retention brainstorming.....

[bbullock]

Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM server (duplicates of the current domains).
Move all the nodes to the new domains (using the 'update node ...
-domain=..' ). Change all the retentions for data in the old domains to
never expire. I'm kind of unclear on how the data would react to this. Would
it be re-bound to the new management classes in the new domain? If the
management classes were called the same, would the data expire anyways?

Any other great ideas out there on how to accomplish this?

Thanks,
Ben

recovering System Objects

[Marc Levitan]

When backing up a server for the first time, the System Objects are NOT
completely backed up.
Does anyone know why this is?  Is there a way to have it all backed up on
the first try?

It looks like you have to backup the system object more than once???
Here is some data from only 1 backup of the system objects.
Following is the data from a second backup.  Notice the size of the COMPDB,
EVENTLOG, and RSM all increase!
It is after the second backup that I was able to successfully restore the
system objects.

Total number of objects inspected:7,527
Total number of objects backed up:7,328
Total number of objects updated:  0
Total number of objects rebound:  0
Total number of objects deleted:  0
Total number of objects expired:  0
Total number of objects failed:   0
Total number of bytes transferred:   504.75 MB
Data transfer time:   69.29 sec
Network data transfer rate:7,459.44 KB/sec
Aggregate data transfer rate:652.23 KB/sec
Objects compressed by:   30%
Elapsed processing time:   00:00:12
tsm> q systemobject
Session established with server
  Server Version 4, Release 2, Level 1.15
  Server date/time: 08/15/2002 08:06:14  Last access: 08/14/2002 15:54:01

 Size  Backup DateMgmt Class A/I File
   ----- --- 
  376  08/14/2002 16:03:01DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\COMPDB
  376  08/14/2002 16:03:02DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\EVENTLOG
  138,902,044  08/14/2002 16:04:57DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\SYSFILES
3,972,159  08/14/2002 16:07:09DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\REGISTRY
  392  08/14/2002 16:07:11DEFAULT A  SYSTEM
OBJECT\TSMOSDRT\RSM



Total number of objects inspected:7,539
Total number of objects backed up:1,838
Total number of objects updated:  0
Total number of objects rebound:  0
Total number of objects deleted:  0
Total number of objects expired:  0
Total number of objects failed:   0
Total number of bytes transferred:   141.17 MB
Data transfer time:   30.65 sec
Network data transfer rate:4,715.24 KB/sec
Aggregate data transfer rate:309.93 KB/sec
Objects compressed by:   41%
Elapsed processing time:   00:03:46
tsm> q systemobject
 Size  Backup DateMgmt Class A/I File
   ----- --- 
7,930  08/15/2002 08:09:24DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\COMPDB
5,593  08/15/2002 08:09:25DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\EVENTLOG
  138,902,044  08/15/2002 08:11:19DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\SYSFILES
4,022,582  08/15/2002 08:14:15DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\REGISTRY
   19,936  08/15/2002 08:14:17DEFAULT A  SYSTEM
OBJECT\TSMOSDRTST\RSM
Thanks,
Marc Levitan
Storage Manager
PFPC Global Funds Services

Re: SQL timestamp not working when upgraded to 4.2.2 for summary tabl e

[Don France]

Yep... this issue had a lllooonnnggg discussion thread back when it first
occurred -- search on the APAR number for the gory details, and there are
caveats about which 5.1.? level has the fix (last I saw it was 5.1.1.5, I
think)... it's in the APAR.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
L'Huillier, Denis
Sent: Thursday, August 15, 2002 10:48 AM
To: [EMAIL PROTECTED]
Subject: Re: SQL timestamp not working when upgraded to 4.2.2 for
summary tabl e


Hey look what I found...

*
$$4225 Interim fixes delivered by patch 4.2.2.5
$$Patches are cumulative, just like PTFs.  So Interim fixes
$$delivered as "4.2.2.5" include those delivered in previous patches
*
<@>
IC33455 SUMMARY TABLE NOT BEING FULLY UPDATED


And I'm querying the summary table..

Thanks..

-Original Message-
From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 11:34 AM
To: [EMAIL PROTECTED]
Subject: Re: SQL timestamp not working when upgraded to 4.2.2 for summary
tabl e


Hi Denis,

Just for information : I tested your query on my system (4.2.2.15) and
it worked like a charm (except I had to modify "Node Name" to
"Node_Name")

Did you apply the latest PTF's to get 4.2.2.15 ? Maybe it could help ...
Good luck anyway !

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-Original Message-
From: L'Huillier, Denis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 15 August, 2002 15:39
To: [EMAIL PROTECTED]
Subject: SQL timestamp not working when upgraded to 4.2.2 for summary
tabl e


Hello -
Since I upgraded our 4.1 server to 4.2.2 my sql query against the
summary table no longer works. Has anyone run into this problem before?
Here's the query...

/* --- Query Summary Table  */
/* ---   Run as a macro   - */
select cast(entity as varchar(12)) as "Node Name", \ cast(activity as
varchar(10)) as Type, \ cast(number as varchar(8)) "Filespace", \
cast(failed as varchar(3)) "Stg", \ cast(affected as decimal(7,0)) as
files, \ cast(bytes/1024/1024 as decimal(12,4)) as "Phy_MB", \
cast(bytes/1024/1024 as decimal(12,4)) as "Log_MB" \ from summary where
end_time>=timestamp(current_date -1 days, '09:00:00') \ and
end_time<=timestamp(current_date, '08:59:59') \ and (activity='BACKUP'
or activity='ARCHIVE') \ order by "Node Name"

Here's the output from a 4.1 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB
Log_MB
  --  -  ---  -  --
--
CENKRSBACKUP  6490   26  0.0222
0.0222
CENNTNFS  BACKUP  6480   15  0.0072
0.0072
RSCH-AS1-PBACKUP  6150   90  7.3412
7.3412
RSCH-DB2-PBACKUP  6140   43  5.6337
5.6337
RSCH-DB3-PBACKUP  60810  0.
0.
RSCH-DB3-PBACKUP  6160  114   1477.5513
1477.5513
RSCH-FS1-PBACKUP  61110  0.
0.
RSCH-FS1-PBACKUP  6180   97 10.3834
10.3834
RSCH-WS5-PBACKUP  6670   29  2.5706
2.5706
RSCH-WS6-PBACKUP  6660   35  5.4812
5.4812
TPRSCHHOME01  BACKUP  62420  0.
0.
TPRSCHHOME01  BACKUP  6270 2467  16412.1675
16412.1675
TPRSCHHOME02  BACKUP  63410  0.
0.
TPRSCHHOME02  BACKUP  6370 3552  19135.1409
19135.1409

Here's the output from a 4.2 server:

Node Name TYPEFilespace  Stg  FILES  Phy_MB
Log_MB
  --  -  ---  -  --
--
REMEDY2W  BACKUP  3896   0   64  0.
0.

I only get one line back.. There should be one for each node (about 100
nodes on this server)

Now, for any of you who are wondering..  'Filespace' and 'Stg' are
columns put in just as place holders. We were using the 'q occu' to
generate charge back info.  I needed to generate an sql query would look
Just like the q occu (same columns) so the data could be fed into an
existing program which handled charge Back to the clients.

Regards,

Denis L. L'Huillier
212-647-2168

Re: Eternal Data retention brainstorming.....

[Prather, Wanda]

Well, this is an interesting "what-if" scenario for discussion!
I'll take a crack at it...

1) Painful, but may be the best solution overall.

2) I don't think that will work.  Turning off EXPIRE INVENTORY will prevent
your tapes from reclaiming, but if you have a mgmt class set to 5 versions,
I think the 6th backup will still make the 1st version invisible to the
client.  Test it and see.

3) Doesn't exist.

4) I think that would work.

5) I guess that would work, but what would be accomplished by using the new
domains?
Result is the same (I think) as just setting the existing management classes
in the existing domains to never expire/unlimited versions.
And, if you don't have the same management classes in the new domains as the
old, when you move a client to a new domain you get a lot of errors, and the
files get managed by the "grace period" numbers, anyway.  Nothing good will
happen.

Export may be the cheapest solution, overall, although it's gonna get
expensive fast since you will quickly double your tape requirements.
1) Change all your management classes to never expire/unlimited versions
2) Make sure NONE of your clients has the delete-backup-data privilege
3) Start your exports, take your time doing them.
When done, you have a complete set of data that is external to TSM.
You can set up a test server with a small TSM, and do IMPORTS of specific
clients as needed, if the investigating agencies ever figure out what they
want to look at.  (Careful to have your mgmt classes set to never
expire/unlimited versions when doing the imports.)
THEN you can reset your production system back to normal retention periods,
and TSM will purge itself of the built-up extra stuff and move on.

Besides that, the best solution I can think of, change all the management
classes to never expire/unlimited versions,
Copy the DB to your "test" server, lock all the client nodes, put your tapes
on a shelf.
Save the last DB backup, just in case.
Start your production server over with a clean DB, back up everything new
and move on.
If anybody needs their old stuff, get a copy via export (from test) and
import(back to production).

That would keep you from (immediately) doubling your tape requirements, will
cost you some hardware to make tape available for your test system..



Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert









-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 3:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.


Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM 

Re: Eternal Data retention brainstorming.....

[Doug Thorneycroft]

how about renaming the filespace, This will keep your active versions.

-Original Message-
From:   bbullock [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, August 15, 2002 12:31 PM
To: [EMAIL PROTECTED]
Subject:Eternal Data retention brainstorming.

Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM server (duplicates of the current domains).
Move all the nodes to the new domains (using the 'update node ...
-domain=..' ). Change all the retentions for data in the old domains to
never expire. I'm kind of unclear on how the data would react to this. Would
it be re-bound to the new management classes in the new domain? If the
management classes were called the same, would the data expire anyways?

Any other great ideas out there on how to accomplish this?

Thanks,
Ben

Re: Eternal Data retention brainstorming.....

[bbullock]

True, that would keep the last active versions, but in this case
they want everything that was backed up to TSM as of a certain date, even
the inactive versions. If I rename the filesystem, the inactive versions
will still drop off as the expire inventory progresses. :-(

Ben

-Original Message-
From: Doug Thorneycroft [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.


how about renaming the filespace, This will keep your active versions.

-Original Message-
From:   bbullock [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, August 15, 2002 12:31 PM
To: [EMAIL PROTECTED]
Subject:Eternal Data retention brainstorming.

Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM server (duplicates of the current domains).
Move all the nodes to the new domains (using the 'update node ...
-domain=..' ). Change all the retentions for data in the old domains to
never expire. I'm kind of unclear on how the data would react to this. Would
it be re-bound to the new management classes in the new domain? If the
management classes were called the same, would the data expire anyways?

Any other great ideas out there on how to accomplish this?

Thanks,
Ben

Re: Eternal Data retention brainstorming.....

[Ford, Phillip]

We have only done this with our exchange servers (not the basic node but the
data from the exchange TDP).  On these systems we have three nodes
base_node, base_nodeA, and base_nodeM.  The base_node is for the operation
system.  The "A" is the current exchange node.  If told to lock, we will
change to base_nodeB for that point on and then "C" and such.  The "M" node
is for the TDP but a monthly backup which we have to keep forever (for now
anyway).   We put them in their own pools (we make pools to match the last
letter of the name) and change node names when they have to be locked up as
described above.  We in effect do number (5).  Note that you do not have to
rebind/reset the management classes to longer retention because the node
that is locked will never backup again.  Thus with no backups there is no
deletes or expires.

Seems to work for us.  It is a pain.  I can not imagine if we had to do all
nodes.


--
Phillip Ford
Senior Software Specialist
Corporate Computer Center
Schering-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
[EMAIL PROTECTED]




-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.


Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM server (duplicates of the current domains).
Move all the nodes to the new domains (using the 'update node ...
-domain=..' ). Change all the retentions for data in the old domains to
never expire. I'm kind of unclear on how the data would react to this. Would
it be re-bound to the new management classes in the new domain? If the
management classes were called the same, would the data expire anyways?

Any other great ideas out there on how to accomplish this?

Thanks,
Ben

***
 This message and any attachments is solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use, or
distribution of the information included in this message is prohibited --
please immediately and permanently delete this message.

Re: Eternal Data retention brainstorming.....

[Richard Cowen]

Do you use DRM and if so, do you copy all primary pools?
If so, snapshot a DB backup and have your offsite people box up all your
current offsite tapes plus this snapshot. Very carefully mark those boxes!
Back at the TSM server, mark all these volumes as "destroyed" and let them
be re-created as your backup stg pools processes run.  Of course, the
downsides are:

1)Until the new set of copy pool tapes are complete,you are exposed to a
primary volume failure.
 (you could of course set up a new server with the old database and a new
library and get data back...)

2)Re-creating that new set of tapes will take some timemaybe more than
24hrs / day?

Maybe use the exercise as an excuse to change tape technology!


-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 3:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.


Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM server (duplicates of the current domains).
Move all the nodes to the new domains (using the 'update node ...
-domain=..' ). Change all the retentions for data in the old domains to
never expire. I'm kind of unclear on how the data would react to this. Would
it be re-bound to the new management classes in the new domain? If the
management classes were called the same, would the data expire anyways?

Any other great ideas out there on how to accomplish this?

Thanks,
Ben

Re: Eternal Data retention brainstorming.....

[Slag, Jerry B.]

If they tell you the hosts/filespaces just do a rename of the existing
filespaces.

-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.


Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location till some day.
This looks like the best way on the surface, but with over 400TB of data in
our TSM environment, it would take a long time to get done and cost a lot if
they could not come up with a list of hosts/filespaces they are interested
in.

Assuming #1 is unfeasible, I'm exploring other more complex ideas.
These are rough and perhaps not thought through all the way, so feel free to
pick them apart.

2. Turn off "expire inventory" until the investigation is complete. This one
is really scary as who knows how long an investigation will take, and the
TSM databases and tape usage would grow very rapidly.

3. Run some 'as-yet-unknown' "expire inventory" option that will only expire
data backed up ~since~ the date in question.

4. Make a copy of the TSM database and save it. Set the "reuse delay" on all
the storage pools to "999", so that old data on tapes will not be
overwritten.
In this case, the volume of tapes would still grow (and need to
perhaps be stored out side of the tape libraries), but the database would
remain stable because data is still expiring on the "real" TSM database.
To restore the data from one of those old tapes would be complex, as
I would need to restore the database to a test host, connect it to a drive
and "pretend" to be the real TSM server and restore the older data.

5. Create new domains on the TSM server (duplicates of the current domains).
Move all the nodes to the new domains (using the 'update node ...
-domain=..' ). Change all the retentions for data in the old domains to
never expire. I'm kind of unclear on how the data would react to this. Would
it be re-bound to the new management classes in the new domain? If the
management classes were called the same, would the data expire anyways?

Any other great ideas out there on how to accomplish this?

Thanks,
Ben

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

[Jolliff, Dale]

>From my somewhat limited understanding of exactly what the RESOURCETIMEOUT
does (and someone jump right in and correct me of I'm wrong) is that it is
the "contention timer" for some resource contention situations in the DB -
for example, setting the timeout to 10 minutes will purportedly only allow
threads to fight over record lock contention for a maximum of 10 minutes,
before one or both give up and abort whatever process they were executing.

And this is just my opinion, formed only by what I have observed here.




-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:15 PM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


That was my question, what will it do?  What are the plus and
minuses of changing it?  What resources is it for?

Don't have much log pin problem on this server.

David Longo

>>> [EMAIL PROTECTED] 08/15/02 09:42AM >>>
Just be aware of what lengthening the RESOURCETIMEOUT will do, especially if
you are susceptible to "logpinned" conditions due to slow, long-running
sessions.




-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 8:17 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Richard,
I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is
set to 10.  Looked at manuals and see this is a new option with 4.2.
There is only a small paragraph about this.  What RESOURCES is this
talking about and what are the implications of changing?

It's probably not tape mounts as I can have a process waiting on a tape
that's being used by another process for well over 10 minutes. (No problem
with that, just know it doesn't apply to tape mounts.)

David Longo

>>> [EMAIL PROTECTED] 08/15/02 08:47AM >>>
I had the same problem after upgrading from 3.74 tp 5.11 on AIX 4.3. The fix
is to change the resource time out in the TSM server's dsmserv.opt file to
60 the default is 10. Hope this helps you out.

Senior TSM consultant

Richard Menides

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 7:38 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ANR message Lock acquisition - TSM 4.2.1.15 server
>
>
> Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.
> This morning I
> am looking at my EXPIRATION process was hung and a backup of local tape to
> the copytape is hung and it all started with very similar message..
> Matt
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.
>
> ANR0538I A resource waiter has been aborted.
>
> ANR0538I A resource waiter has been aborted.
>
> ANRD IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
> ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
> processed
> ANR0986I 3603 items for a total of 970,174,464 bytes with a
> completion state
> of
> ANR0986I FAILURE at 06:06:44.
>
> ANRD IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
> for
> ANRD node 499, filespace 35
>
>
> -Original Message-
> From: Nilsson Niklas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 15, 2002 2:25 AM
> To: [EMAIL PROTECTED]
> Subject: SV: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning...
>
> Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
> Going to take it up with support.
>
> Regards Niklas
>
> -Ursprungligt meddelande-
> Fren: Brian L. Nick [mailto:[EMAIL PROTECTED]]
> Skickat: den 14 augusti 2002 16:16
> Till: [EMAIL PROTECTED]
> Dmne: ANR message Lock acquisition - TSM 4.2.1.15 server
>
> Good morning,
>
>  We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
> One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
> Also we are receiving the follo

Re: Eternal Data retention brainstorming.....

[Thomas A. La Porte]

As a refinement to Wanda's final suggestion, couldn't you alter
your policies for 'del volhist type=dbb' (or simply retain the
current copy of your database backup exclusive of the volume
history), and then modify your storage pool's reusedelay
parameter appropriately?

The drawback that I see is that there is no "forever" parameter
for reusedelay.  days is the maximum. Granted, that's over 27
years, but we know how long government investigations can last! :-)

-- Tom

Thomas A. La Porte, DreamWorks SKG


On Thu, 15 Aug 2002, Prather, Wanda wrote:

>Besides that, the best solution I can think of, change all the management
>classes to never expire/unlimited versions,
>Copy the DB to your "test" server, lock all the client nodes, put your tapes
>on a shelf.
>Save the last DB backup, just in case.
>Start your production server over with a clean DB, back up everything new
>and move on.
>If anybody needs their old stuff, get a copy via export (from test) and
>import(back to production).
>
>That would keep you from (immediately) doubling your tape requirements, will
>cost you some hardware to make tape available for your test system..
>
>
>
>Wanda Prather

Re: Bad performance from tape to tape

[Bill Boyer]

The original poster said his disk pool had CACHE=YES turned on. So for a
time a backed up file could reside in 3-different placesdisk pool
cache..onsite tape..offsite tape. Normally when you think of reclamation it
is a tape-to-tape process, so I/we were generalizing.

The problems is that when the primay copy of the file is on a random access
disk storage pool, TSM does not use the MOVEBATCHSIZE and MOVESIZETHRESH
parameters to 'batch' the transactions. The reclamation process
moves/reclaims 1 file..updates the DBmoves another file...updates the
DBetc.etc...

When CACHE=YES is on, then TSM will use the primary location with the best
performace...DISK. Even though the file is on the sequential onsite tape
media. CACHE=YES is good for restore performance, but when the storage pool
fills up during client backups, you have to overhead of TSM deciding which
CACHE'd files to throw away, throwing then away and then accepting the new
backup data.

A process we use is to do all the storage pool backup first thing in the
morning after the client backups are complete, but not do the migration
until later in the afternoon. This way last nights' backup data is still on
disk for restore performance, but then moved off before the next nights'
backups start. We've found that a lot of the onsey-twosy restores are
because the use hosed up his file today and needs it restored from last
nights' backup. This way it comes from disk, but you don't have the
CACHE=YES overhead and performance hit for reclamation.

Bill Boyer
DSS, Inc.
"Backup my harddrive?...How do I put it in reverse??" - ??

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Vos, F (Freek)
Sent: Thursday, August 15, 2002 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Bad performance from tape to tape


Hi Bill,

Reclamation is not only a tape to tape copy.
The changes to the TSM database are they holding down your speed ?
The amount of tape mounts, are there many ?
Do the disks and the tapeunits share the same SCSI adapter ?

Groet,

Freek.


-Original Message-
From: Bill Boyer [mailto:[EMAIL PROTECTED]]
Sent: donderdag 15 augustus 2002 17:15
To: [EMAIL PROTECTED]
Subject: Re: Bad performance from tape to tape


The tape-to-tape operation that is adversely affected is reclamation. If the
primay location of a file is in a random access disk pool, then TSM does not
'batch' the files together. Each transaction is a single file. The primary
location can be a disk sequential access pool, but not random access. We
originally came across this with DIRMC. We had the primary a DISK pool and
then only created the copypool. The reclamation on the copypool tapes used
to take days. Opened a PMR with Tivoli and got the 'working as designed'
answer.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Joe Pendergast
Sent: Thursday, August 15, 2002 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Bad performance from tape to tape


Is the disk pool cached?
I ran into a situation where the disk pool cache instead of tape was being
used.
This slowed my LTO drives to a crawl during certain operations.
I now varyoff the disk pools before I run the process with expected results
Don't forget to vary them back on at the end..
Note: the disk pool cache is a great help in restore time, but it can
adversely
the affect of what should be a tape to tape process.





Halvorsen Geirr Gulbrand <[EMAIL PROTECTED]> on 08/15/2002 03:00:23 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: Joseph Pendergast/Corona/Watson)

Subject:  Bad performance from tape to tape



Hi All,
I have a performance problem when doing Space-Reclaamtion, or backup storage
pool, when TSM is copying data from one tape drive to the other.
Environment:
Windows 2K server, TSM 4.2.1.15.
Library, Compaq MSL5026, with 2 SDLT drives (Single Module Library).
SCSI Controller, Compaq 64-bit/66Mhz Dual Channel Wide Ultra3 SCSI Adapter
(Compaq version of Adaptec 39160)

Moving data from Disk to Tape runs with expected speed (8-10 MB/s).

>From Tape to tape speed is around 2MB/s. (50GB takes about 7-8hours.)

Does anyone know why? It is killing my daily operations.

Mvh
Geirr G. Halvorsen
TSM Enterprise Backup Specialist
WMdata Danmark A/S

==
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
==
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender imm

Re: Eternal Data retention brainstorming.....

[bbullock]

Wanda,
Thanks for the input. The last suggestion of starting over had
crossed my mind, but I forgot to include it in my list. I guess the reason I
left it out was that with 800 clients, (some of them large) and with HSM in
place, starting from scratch would be difficult. Then, the hardware (8
high-end RS6000s would be hard to afford).

I have since looked at option 4 a little closer and refined it
further. All the data is duplicated in copypools, right? So, what if I took
a snapshot of the database and kept it aside. I then could change the
"reusedelay" to 999 on the tapes in the copypool so that they will not be
overwritten. That way I won't have to make an additional copy of the data as
I already have one. Sure, tape usage will still go up as the copypool tapes
are never reclaimed, but it would not instantly double as they do in the
other scenarios.

It kind of sounds like a disaster recovery test if I were to need to
restore the old data. I'd restore the DB to a test host, gather up the
copypool tapes and try to restore something. I could hit 2 birds with one
stone (meet the legal requirements and do a DR test).

Thanks,
Ben

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.


Well, this is an interesting "what-if" scenario for discussion!
I'll take a crack at it...

1) Painful, but may be the best solution overall.

2) I don't think that will work.  Turning off EXPIRE INVENTORY will prevent
your tapes from reclaiming, but if you have a mgmt class set to 5 versions,
I think the 6th backup will still make the 1st version invisible to the
client.  Test it and see.

3) Doesn't exist.

4) I think that would work.

5) I guess that would work, but what would be accomplished by using the new
domains?
Result is the same (I think) as just setting the existing management classes
in the existing domains to never expire/unlimited versions.
And, if you don't have the same management classes in the new domains as the
old, when you move a client to a new domain you get a lot of errors, and the
files get managed by the "grace period" numbers, anyway.  Nothing good will
happen.

Export may be the cheapest solution, overall, although it's gonna get
expensive fast since you will quickly double your tape requirements.
1) Change all your management classes to never expire/unlimited versions
2) Make sure NONE of your clients has the delete-backup-data privilege
3) Start your exports, take your time doing them.
When done, you have a complete set of data that is external to TSM.
You can set up a test server with a small TSM, and do IMPORTS of specific
clients as needed, if the investigating agencies ever figure out what they
want to look at.  (Careful to have your mgmt classes set to never
expire/unlimited versions when doing the imports.)
THEN you can reset your production system back to normal retention periods,
and TSM will purge itself of the built-up extra stuff and move on.

Besides that, the best solution I can think of, change all the management
classes to never expire/unlimited versions,
Copy the DB to your "test" server, lock all the client nodes, put your tapes
on a shelf.
Save the last DB backup, just in case.
Start your production server over with a clean DB, back up everything new
and move on.
If anybody needs their old stuff, get a copy via export (from test) and
import(back to production).

That would keep you from (immediately) doubling your tape requirements, will
cost you some hardware to make tape available for your test system..



Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert









-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 3:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.


Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the database.

The most obvious way to do this would be to:

1. Export the data to tapes & store them in a safe location til

Upgrades TSM/AIX

[Gill, Geoffrey L.]

Questions relating to TSM and AIX upgrades.

I was running AIX 4.3.3 TSM 5.1.1.1 as of yesterday. This morning I upgraded
atape and atldd drivers then AIX to V5 (migrate install). The system
restarted and everything came up except the 2 tape drives in TSM. I removed
the paths and then added them back and things seem to be working.

The next question is upgrading TSM to the next patch level. The last TSM
upgrade was with a version that installed on 4.3.3. When I download the tar
file and unzip it has both versions, so the question is what's going to get
installed if I just let it do it's thing? Or do I have to specifically
choose the aix5 version?

Any issues here?
Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Re: LTO Tape Status Full

[Jason Liang]

Camilo,

You can delete this volume by using

Move data A00060

Jason Liang

- Original Message -
From: "Camilo A. Marrugo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 15, 2002 11:48 AM
Subject: LTO Tape Status Full


> Do anyone ever seen when a tape goes to status full with 0.0% used. And
> every time that you try to move the data out of it, it gives you an:
>
> ANR2209W Volume A00060 contains no data.
>
> And if you try to delete the volume it gives you:
>
> ANR2406E DELETE VOLUME: Volume A00060 still contains data.
>
> Any help will be appreciated.
>
> Thanks,
> Camilo Marrugo
>
> --
> Camilo Marrugo
> Backup Solutions Administrator/Sr. Systems Administrator
> Dialtone Inc. an Interland Company
> [EMAIL PROTECTED] - http://www.dialtone.com
> Voice: (954) 581-0097 ext. 130 - Fax: (954) 581-7629
> "We are Interland... One Team, One Vision."
>

Re: LTO Tape Status Full

[bbullock]

Nope, that's not going to work, it will still error out.

This has been discussed recently in this forum and you should be
able to find a solution in the archives located at http://adsm.org

To give you a head start, it's a "audit vol.. fix=yes" command.

Ben

-Original Message-
From: Jason Liang [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:52 PM
To: [EMAIL PROTECTED]
Subject: Re: LTO Tape Status Full


Camilo,

You can delete this volume by using

Move data A00060

Jason Liang

- Original Message -
From: "Camilo A. Marrugo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 15, 2002 11:48 AM
Subject: LTO Tape Status Full


> Do anyone ever seen when a tape goes to status full with 0.0% used. And
> every time that you try to move the data out of it, it gives you an:
>
> ANR2209W Volume A00060 contains no data.
>
> And if you try to delete the volume it gives you:
>
> ANR2406E DELETE VOLUME: Volume A00060 still contains data.
>
> Any help will be appreciated.
>
> Thanks,
> Camilo Marrugo
>
> --
> Camilo Marrugo
> Backup Solutions Administrator/Sr. Systems Administrator
> Dialtone Inc. an Interland Company
> [EMAIL PROTECTED] - http://www.dialtone.com
> Voice: (954) 581-0097 ext. 130 - Fax: (954) 581-7629
> "We are Interland... One Team, One Vision."
>

Re: NDS (Netware 5.x)

[Greg Tice]

Mark,
The login script is not held in NDS as a separate object it is part of the
.OU object.  Restoring the .OU will bring it back.  This is not something
you want todo in a production environment.   If you have an isolated
test/lab environment at your facility you could easily mock up an NDS tree
and get it back that way.

This exact scenario is why I used to require my admins to copy, paste &
save the login script to a text file before making any modifications to
login scripts.

Hope this helps!


Greg Tice







Mark Hayden
<[EMAIL PROTECTED]   To: [EMAIL PROTECTED]
ATE.IL.US>cc:
Sent by: "ADSM:   Fax to:
Dist Stor Subject: NDS (Netware 5.x)
Manager"
<[EMAIL PROTECTED]
ST.EDU>


08/15/2002
11:48
Please respond
to "ADSM: Dist
Stor Manager"






Hi all, wanted to know if anyone has done any retores from NDS. We have a
NetWare admin that butchered the Login script from a NetWare Server under
the NDS tree. I was wondering what the name of this login script would be
called in NDS.Cn=  Thanks

Thanks, Mark Hayden
Informations Systems Analyst
E-Mail:  [EMAIL PROTECTED]

Re: LTO Tape Status Full

[Jason Liang]

Camilo,

If the "move data" doesn't work,

you can use the following:

1. If the volume is on offsite ,
update vol volume_name access=readw
2. audit vol volume_name fix=y
3. del vol volume_name discard=y

Jason Liang



- Original Message -
From: "Jason Liang" <[EMAIL PROTECTED]>
To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent: Thursday, August 15, 2002 4:51 PM
Subject: Re: LTO Tape Status Full


> Camilo,
>
> You can delete this volume by using
>
> Move data A00060
>
> Jason Liang
>
> - Original Message -
> From: "Camilo A. Marrugo" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, August 15, 2002 11:48 AM
> Subject: LTO Tape Status Full
>
>
> > Do anyone ever seen when a tape goes to status full with 0.0% used. And
> > every time that you try to move the data out of it, it gives you an:
> >
> > ANR2209W Volume A00060 contains no data.
> >
> > And if you try to delete the volume it gives you:
> >
> > ANR2406E DELETE VOLUME: Volume A00060 still contains data.
> >
> > Any help will be appreciated.
> >
> > Thanks,
> > Camilo Marrugo
> >
> > --
> > Camilo Marrugo
> > Backup Solutions Administrator/Sr. Systems Administrator
> > Dialtone Inc. an Interland Company
> > [EMAIL PROTECTED] - http://www.dialtone.com
> > Voice: (954) 581-0097 ext. 130 - Fax: (954) 581-7629
> > "We are Interland... One Team, One Vision."
> >
>

Upgrades AIX/TSM Error

[Gill, Geoffrey L.]

Well I take back the part that I said everything seems to be working. Since
the first system restart the TSM server and the scheduler service will not
start when the system restarts. I can start them manually and the server
does some up so that seems strange to me.  Luckily this is my test system.
Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Re: Eternal Data retention brainstorming.....

[Ochs, Duane]

I would have to agree that the export node is probably the best overall
method.

Negatives:
Tape requirements would grow at a huge factor. There is no commingling of
systems. Even if you have servers with an archive name and a backup name
each name would have to be exported separately.

They can take a very long time, per server, depends on collocation number of
files, number of versions...
I exported a node with 650GB of DB backups around 35 files. It took almost
48 hours.


Also:
It might be wise to either lease or buy an additional jukebox... granted it
maybe expensive but your company can't shutdown even if there is a
government audit. Then create a new storage pool and do all your exports to
that. It would allow you to do more than one or two exports at a time and
allow you to complete your normal processing of backups.

Wanda... or anyone... one question. When changing retention settings for a
management class, are they immediately processed by TSM or does the next
backup have to run to rebind all the files to the new class settings ?

If it is the latter, the files that no longer exist on the client, but are
still being retained, will not be rebound... They will stay with the same
retention settings, right ?

Duane Ochs
Systems Administration
Quad/Graphics Inc.
414.566.2375

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 3:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.


Well, this is an interesting "what-if" scenario for discussion!
I'll take a crack at it...

1) Painful, but may be the best solution overall.

2) I don't think that will work.  Turning off EXPIRE INVENTORY will prevent
your tapes from reclaiming, but if you have a mgmt class set to 5 versions,
I think the 6th backup will still make the 1st version invisible to the
client.  Test it and see.

3) Doesn't exist.

4) I think that would work.

5) I guess that would work, but what would be accomplished by using the new
domains?
Result is the same (I think) as just setting the existing management classes
in the existing domains to never expire/unlimited versions.
And, if you don't have the same management classes in the new domains as the
old, when you move a client to a new domain you get a lot of errors, and the
files get managed by the "grace period" numbers, anyway.  Nothing good will
happen.

Export may be the cheapest solution, overall, although it's gonna get
expensive fast since you will quickly double your tape requirements.
1) Change all your management classes to never expire/unlimited versions
2) Make sure NONE of your clients has the delete-backup-data privilege
3) Start your exports, take your time doing them.
When done, you have a complete set of data that is external to TSM.
You can set up a test server with a small TSM, and do IMPORTS of specific
clients as needed, if the investigating agencies ever figure out what they
want to look at.  (Careful to have your mgmt classes set to never
expire/unlimited versions when doing the imports.)
THEN you can reset your production system back to normal retention periods,
and TSM will purge itself of the built-up extra stuff and move on.

Besides that, the best solution I can think of, change all the management
classes to never expire/unlimited versions,
Copy the DB to your "test" server, lock all the client nodes, put your tapes
on a shelf.
Save the last DB backup, just in case.
Start your production server over with a clean DB, back up everything new
and move on.
If anybody needs their old stuff, get a copy via export (from test) and
import(back to production).

That would keep you from (immediately) doubling your tape requirements, will
cost you some hardware to make tape available for your test system..



Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert









-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 3:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.


Folks,
I have a theoretical question about retaining TSM data in an unusual
way. Let me explain.

Lets say legal comes to you and says that we need to keep all TSM
data backed up to a certain date, because of some legal investigation
(NAFTA, FBI, NSA, MIB, insert your favorite govt. entity here). They want a
snapshot saved of the data in TSM on that date.

Anybody out there ever encounter that yet?

On other backup products that are not as sophisticated as TSM, you
just pull the tapes, set them aside and use new tapes. With TSM and it's
database, it's not that simple. Pulling the tapes will do nothing, as the
data will still expire from the data

Re: LTO Tape Status Full

[Camilo A. Marrugo]

O.K. it worked. Basically I had to halt tsm and started up with the
following options:

nomigrrecl
disablescheds yes
expinterzal 0

because as soon as I tried to do the "audit volume" command on that
specific volume, I got some error saying that there was a space
reclamation already running for it, and it will not allow me to execute
anything on it.

after the restart I followed the steps that you provided me with and it
worked right away. Thanks for your help.


Regards,
Camilo Marrugo



On Thu, 2002-08-15 at 17:06, Jason Liang wrote:
>
> Camilo,
>
> If the "move data" doesn't work,
>
> you can use the following:
>
> 1. If the volume is on offsite ,
> update vol volume_name access=readw
> 2. audit vol volume_name fix=y
> 3. del vol volume_name discard=y
>
> Jason Liang
>
>
>
> - Original Message -
> From: "Jason Liang" <[EMAIL PROTECTED]>
> To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> Sent: Thursday, August 15, 2002 4:51 PM
> Subject: Re: LTO Tape Status Full
>
>
> > Camilo,
> >
> > You can delete this volume by using
> >
> > Move data A00060
> >
> > Jason Liang
> >
> > - Original Message -
> > From: "Camilo A. Marrugo" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 15, 2002 11:48 AM
> > Subject: LTO Tape Status Full
> >
> >
> > > Do anyone ever seen when a tape goes to status full with 0.0% used. And
> > > every time that you try to move the data out of it, it gives you an:
> > >
> > > ANR2209W Volume A00060 contains no data.
> > >
> > > And if you try to delete the volume it gives you:
> > >
> > > ANR2406E DELETE VOLUME: Volume A00060 still contains data.
> > >
> > > Any help will be appreciated.
> > >
> > > Thanks,
> > > Camilo Marrugo
> > >
> > > --
> > > Camilo Marrugo
> > > Backup Solutions Administrator/Sr. Systems Administrator
> > > Dialtone Inc. an Interland Company
> > > [EMAIL PROTECTED] - http://www.dialtone.com
> > > Voice: (954) 581-0097 ext. 130 - Fax: (954) 581-7629
> > > "We are Interland... One Team, One Vision."
> > >
> >
>
--
Camilo Marrugo
Backup Solutions Administrator/Sr. Systems Administrator
Dialtone Inc. an Interland Company
[EMAIL PROTECTED] - http://www.dialtone.com
Voice: (954) 581-0097 ext. 130 - Fax: (954) 581-7629
"We are Interland... One Team, One Vision."

Re: Eternal Data retention brainstorming.....

[Tab Trepagnier]

Ben,

I've had to do "permanent" retention only twice so far.

The first time we did the "keep forever" change to the management class
associated with our Lotus Notes files.  As predicted, data and tape usage
grew unbounded.  That helped us decide to migrate from 3570 technology to
LTO.

After that suit was settled we exported the data to "shelf" DLTs then
upgraded the Notes server to Domino R5.  That changed the nature of the
backups via TDP, so we essentially started over with our Domino backups
and did a DELETE FILESPACE on the old Notes data.  All gone except for the
exports to DLT and imports into R5 (current data).

We learned.

The second time this came up, I met with Legal and explained how TSM
worked with lots of pictures on the whiteboard.

With that info in hand, we exported all data of relevance (and yes that
took almost a week), along with a full database backup to DLT, and a
floppy with the config files like device config and dsmserv.dsk.  All of
that went into a sealed container along with version info:  these tapes
were created with TSM 4.1.4.0 on AIX 4.3.3.

I also got Legal to sign off on the understanding that because of TSM's
dynamic nature, if they decide to access that data after it was more than
six months old, they would have to LEASE an RS/6000 and a tape library and
we would work on a parallel system.  Three years from now I was not going
to roll our system back from TSM "7" to TSM 4.1 just to access the data on
those tapes.  And, of course, the import would take the same week that the
exports took.

Those tapes have been sitting in their sealed container in the vault for
five months now and no one has asked for their contents.

Tab Trepagnier
TSM Administrator
Laitram Corporation

Re: IBM vs. Storage Tek

[Robert Molerio]

Dump the TSM SERVER on SUN idea.. SUN"s are not as stable as RS6000's.

volume range labeling in non-barcode jukebox

[Henry Chen]

Hello,

I have a HP1200ex optical jukebox that does not have a barcode reader.  I'm
using "label libv lib.optical.01 search=yes labels=prompt checkin=scr" to
label the medias in this jukebox.  Is there a way to label medias in this
jukebox without having to manually type in the label each time?  ie. specify
a list of volume ranges in a file?  also, this jukebox has 10 drives, would
the "label" command above find and load 10 medias at a time to request for
labels?  I'm currently seeing only 1 drive in use and sequential requests
for volume names.

Thanks.

-Henry

Henry Chen
Production Engineer
Zantaz, Inc
(925) 598-3078


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: drive online=no versus path offline=no

[Don France]

Yep... the only change (for simple, single server access environments) is
that you must DEFINE PATH in order to convey the device special file address
to the TSM server... the DEFINE LIBRary and DEFine DRive no longer accept
the device parameter.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gerhard Rentschler
Sent: Thursday, August 15, 2002 8:43 AM
To: [EMAIL PROTECTED]
Subject: drive online=no versus path offline=no


Hello,
with TSM 5.1 one has to define a path for each drive. Both, update drive and
update path have an online option. Is it sufficient to set a drive offline
in a single server environment?
Regards
Gerhard
---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany

Re: IBM vs. Storage Tek

[Don France]

I am still trying to collect contacts for some of the STK sites;  I am aware
of about six customers switching "TO" 9940 (with SN6000) from something
else - one is replacing their 3590 with 9940's (not LTO).

Changing from 3590 to LTO is definitely a step "backward" in reliability;
performance is also 8-10 times slower... the basic idea behind LTO was to
provide a cost-effecting, competing product against DLT -- which is exactly
what it is.

LTO is 8-10 faster (and more reliable) than DLT;  all this, at a price point
competitive with DLT.  3590 is 8-10 times faster and worlds more reliable
than LTO (and 9840/9940 which is comparable with 3590).  I think of
3590/9940 as the industrial-strength answer for large data centers -- large
to me means moving over 1.5 TB per day, storing over 20 TB of data in their
silo;  smaller sites, more price conscious, willing to "tolerate" slower
restore speeds are the ideal target for LTO.  Most shops know that DLT is
slow;  if we can approximate 10-15 GB/hour in restoring a file server, they
know that is a good number -- and I have demo'ed that with Dell PowerVault
130 using DLT7000.  Large db's can be restored at 20-36 GB per hour;  DLT is
at the low end of that, LTO is at the high end -- you just about saturate
the 100 Mbps wire at 30 GB/hr.

LTO, like DLT, does not like alot of "back-hitch" operations;  so, I would
minimize the amount of collocation on LTO.  Every account I know that has
LTO is ecstatic about the performance;  the LTO design was based on 3590
technology, but (to cut costs) some reliability factors were sacrificed...
this is not a drive you want to run without a service contract, especially
if you're gonna beat it with the "back-hitch" action that's required to
back-space from eot, find last tape mark, start writing next data block from
end if the inter-record gap of the last one, etc.

One person's opinion, stretched over a dozen or more customer accounts.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Joni Moyer
Sent: Thursday, August 15, 2002 6:30 AM
To: [EMAIL PROTECTED]
Subject: IBM vs. Storage Tek


Hello,

I know I've asked about this before, but now I have more information so I
hope someone out there has done this.  Here is my environment for TSM.
Right now it is on the mainframe and we are using 3590 Magstars.  We have a
production and a test TSM server and each has about 13 drives and a total
of 5,500 tapes used for onsite and offsite tape pools between the 2
systems.  Two scenarios are being considered (either way TSM is being moved
onto our SAN environment with approximately 20 SAN backup clients and 250
LAN backup clients and will be on SUN servers instead of the mainframe)
Here is what I estimated I would need for tapes:

 3590 9840 9940A LTO
 10 GB 20 GB 60 GB 100 GB
Production
Onsite1375 689  231  140
Offsite   1600 800  268  161
Total 2975 1489 499  301

Test
Onsite963  483  163  101
Offsite   1324 664  223  135
Total 2287 1147 386  236

Grand
Total 5262 2636 885  537

1. IBM's solution is to give us a 3584 library with 3 frames and use LTO
tape drives.  This only holds 880 tapes and from my calculations I will
need about 600 tapes plus enough tapes for a scratch pool.  My concern is
that LTO cannot handle what our environment needs.  LTO holds 100 GB
(native), but when a tape is damaged or needs to be reclaimed the time it
takes to do either process would take quite some time in my estimation.
Also, I was told that LTO is good for full volume backups and restores, but
that it has a decrease in performance when doing file restores, archives
and starting and stopping of sessions, which is a majority of what our
company does with TSM.  Has anyone gone from a 3590 tape to LTO?  Isn't
this going backwards in performance and reliability?  Also, with
collocation, isn't a lot of tape space wasted because you can only put one
server  per volume?

2. STK 9840B midpoint load(20 GB) or 9940A(60 GB) in our Powderhorn silo
that would be directly attached to the SAN.  From what I gather, these
tapes are very robust like the 3590's, but the cost for this solution is
double IBM's LTO.  We would also need Gresham licenses for all of the SAN
backed up clients(20).

Does anyone know of any sites/contacts that could tell me the
advantages/disadvantages of either solution?  Any opinions would be greatly
appreciated.
Thanks


Joni Moyer
Associate Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: Easiest way to do a command line Full Backup.

[Don France]

This method is equivalent to the SELective and is off topic;  he wanted to
use command line.  Also, Paul's point is a good one -- selective does not
update the last-incremental date on the filespace... so, we're back to
ABSOLUTE in the management class.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
William Rosette
Sent: Wednesday, August 14, 2002 4:21 AM
To: [EMAIL PROTECTED]
Subject: Re: Easiest way to do a command line Full Backup.


We use a fourth, the manual way with the GUI and using the "Always Backup"
button.  Our 3rd shift operators key it off usually after a automatic
incremental and before some special project on that particular client.  The
client requests a "full" and we will do a manual "Always Backup."



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


|-+>
| |   Don France   |
| ||
| |   Sent by: "ADSM:  |
| |   Dist Stor|
| |   Manager" |
| |   <[EMAIL PROTECTED]|
| |   .EDU>|
| ||
| ||
| |   08/13/02 06:51 PM|
| |   Please respond to|
| |   "ADSM: Dist Stor |
| |   Manager" |
| ||
|-+>

>---
---|
  |
|
  |   To:   [EMAIL PROTECTED]
|
  |   cc:
|
  |   Subject:  Re: Easiest way to do a command line Full Backup.
|

>---
---|




There are THREE "sure" ways to trigger a (traditional) FULL backup:

1 - run "dsmc i" (incremental command) but use a management class which
maps
to a copygroup which specifies "absolute" (rather than modified) for
"mode",
AND frequency=0 (to allow on demand);  this is the "easiest" way to force
FULL (for data mapped to the appropriate management class, via INCLUDE
specs.);

2 - use the archive command (but you must specify each file system);

3 - selective will also work, but you must specify each file system.

That should do it.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)




"Gent, Chad E." <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2002-08-13 13:37
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Easiest way to do a command line Full Backup.


Hello,

Is there an easy way to do a full command line backup.   I have an NT
client
version 4.2.15 and I would like to do full backups instead of incremental.

Thanks

Chad
IMPORTANT:  The security of electronic mail  sent through the Internet
is not guaranteed.  Legg Mason therefore recommends that you do not
send confidential information to us via electronic mail, including social
security numbers, account numbers, and personal identification numbers.

Delivery, and timely delivery, of electronic mail is also not
guaranteed.  Legg Mason therefore recommends that you do not send
time-sensitive
or action-oriented messages to us via electronic mail, including
authorization to  "buy" or "sell" a security or instructions to conduct
any
other financial transaction.  Such requests, orders or instructions will
not be processed until Legg Mason can confirm your instructions or
obtain appropriate written documentation where necessary.

Re: Eternal Data retention brainstorming.....

[bbullock]

Dang, my mails are long-winded. Forgive me if I'm boring those of
you who are not interested. Fell free to use the "delete" button. :-)

There's been a lot of good suggestions sent to me. The real kicker
is that with the volume of data involved (460TB as of today), some of the
solutions do not scale well, in that they will take months to complete, or
cost $100,000s in tapes to execute.

Like most of you out there, we gradually grew to our current size,
and management can take the constant nickel and diming we do to keep ahead
of the capacity curve. A big $$ expenditure to CYA for a "what if" will not
sit well with management and they will look to me for "creative
alternatives".

I actually called Tivoli and discussed it with a level 1 & 2 and
here's what I/we came up with.

We have 2 kinds of data: Mission Critical data that we keep in a
copypool, and non-critical/old data we do not backup to a copypool.
Unfortunaly, ALL of the data needs to be retained and the non-critical
(unduplicated) portion is rather substantial in size.

Here's a 1000-ft view of what we are thinking about:

Take a backup of the TSM DB. Make it so that copypool tapes will
never be reused "reusedelay=". As production rolls on, all copypool
tapes will be taken from scratch, so the old data we are trying to retain
should remain on the copypool tapes, although at some time, the production
DB may remove their BD pointers through it's "expire inventory" process. Our
growth in copypool tapes is much more reasonable (10-20 tapes a week), and
not costly enough to freak management out.
In the case of the old data being needed, the TSM database can be
restored on a test host & the primary tape volumes marked as inactive. When
a restore is needed, the TSM server will request the copypool tapes, and the
data will still be intact because they have not been re-used. This portion
is pretty much like a disaster recovery test.

The non-critical data is a little harder, as there is only 1 copy of
the data. We could try to push it to a copypool, but there is a LOT and it
will take quite a bit of time $ money. The good thing is that this data is
~only~ being retained for the investigation and no other purpose. For this
reason, daily operations, and file restores will ~never~ need these tapes.
We will check all these primary tapes out of the library at the same
time we take the DB snapshot and box them up with BIG RED letters and put
behind a barber wire fence guarded by vicious dogs. We will then mark the
tapes as DESTROYED on our production database. We might even delete the
filespace, as they are just that useless, however we are going through all
this trouble because they are required because "ALL BACKUPS/ARCHIVES" are
required to be retained.
If we need to restore data off of one of these tapes, we will
restore the TSM DB backup to our test host. These tapes should all still be
marked as "readw" on the restored DB, so we should just be able to restore
the data by feeding it the primary tapes it requests.

Benefits:
- No need to duplicate the data with a "export data" or making a 3rd
copypool copy.
- Very little extra $$.
Problems:
- More work and time up front to make sure it works as planned.
- Care needs to be taken and procedures in place so that copypool or
primary "useless data" tapes are not accidentally reclaimed.
- Might interfere in a true disaster, as the copypool tapes might be
in the wrong place because of an "investigation related" restore.

What do you think? Does it sound like it would work? I ~think~ it
sounds do-able. Am I missing a big GOTCHA anyone can see?

Thanks,
Ben

Re: volume range labeling in non-barcode jukebox

[Mark D. Rodriguez]

Henry Chen wrote:

>Hello,
>
>I have a HP1200ex optical jukebox that does not have a barcode reader.  I'm
>using "label libv lib.optical.01 search=yes labels=prompt checkin=scr" to
>label the medias in this jukebox.  Is there a way to label medias in this
>jukebox without having to manually type in the label each time?  ie. specify
>a list of volume ranges in a file?  also, this jukebox has 10 drives, would
>the "label" command above find and load 10 medias at a time to request for
>labels?  I'm currently seeing only 1 drive in use and sequential requests
>for volume names.
>
>Thanks.
>
>-Henry
>
>Henry Chen
>Production Engineer
>Zantaz, Inc
>(925) 598-3078
>
>
>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.
>
>
Henry,

Check the command documentation by issueing a "help label libv" and you
will see there is to ways to accomplish this either using the "volrange"
option or the "volist" option and specify a file with a list of names.

Hope that helps.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===

Re: volume range labeling in non-barcode jukebox

[Henry Chen]

if i'm reading this correctly, doesn't the "volrange" and "vollist" options
only apply when i specify "search=yes labelsource=barcode"?

-Henry

-Original Message-
From: Mark D. Rodriguez [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 4:35 PM
To: [EMAIL PROTECTED]
Subject: Re: volume range labeling in non-barcode jukebox


Henry Chen wrote:

>Hello,
>
>I have a HP1200ex optical jukebox that does not have a barcode reader.  I'm
>using "label libv lib.optical.01 search=yes labels=prompt checkin=scr" to
>label the medias in this jukebox.  Is there a way to label medias in this
>jukebox without having to manually type in the label each time?  ie.
specify
>a list of volume ranges in a file?  also, this jukebox has 10 drives, would
>the "label" command above find and load 10 medias at a time to request for
>labels?  I'm currently seeing only 1 drive in use and sequential requests
>for volume names.
>
>Thanks.
>
>-Henry
>
>Henry Chen
>Production Engineer
>Zantaz, Inc
>(925) 598-3078
>
>
>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.
>
>
Henry,

Check the command documentation by issueing a "help label libv" and you
will see there is to ways to accomplish this either using the "volrange"
option or the "volist" option and specify a file with a list of names.

Hope that helps.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.


===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE

===


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: Upgrade from 3590E to 3590H

[Zlatko Krastev/ACIT]

Actually the steps are just the same as for migration from 3590B to 3590E.
IBM CE will perform the upgrade and you will do the rest.
The latter is well documented and you can also find plenty of info in list
archives (http://www.adsm.org/).

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Upgrade from 3590E to 3590H

Hello, everyone.

Platform: IBM pSeries 6M1
OS: AIX 4.3.3.10
TSM: 5.1.1.1
Atape: 7.0.7.0
atldd: 5.0.7.0

I am getting ready to perform an upgrade from 3590E to 3590H drives in
my 3494.  Each of the 6-drives is directly fiber-channel attached to the
TSM server.

Has anyone gone through an upgrade such as this?  If so, can you share
you experience with me?  I guess, what I am looking for is the steps in
TSM and AIX that I need to go through to successfully do this.

TIA

Mahesh

Re: Licensing

[mephi (劉禹賢)]

According from Tivoli Taiwan, If you have a tape library more than 2
drive or more than 20 slot, you should buy managed library license.
Share library is needed if you have more than 1 TSM server and share the
same library or if you wanna use SAN and a tape library on SAN.

-Original Message-
From: Nick Rutherford [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 10:02 PM
To: [EMAIL PROTECTED]
Subject: Licensing


Hello
 can somebody please clarrify the difference between the license for
'Managed Libraries' and the license for 'Library Sharing'.
Many thanks,
Nick Rutherford


*
This e-mail is confidential and intended solely for the use of the
individual to whom it is addressed.  Any views or opinions presented
are solely those of the author and do not necessarily represent
those of Honda of the UK Manufacturing Ltd.

If you are not the intended recipient please notify the sender
immediately by return e-mail and then delete this message from your
system.  Also be advised that any use, disclosure, forwarding,
printing or copying of this e-mail if sent in error is strictly
prohibited.  Thank you for your co-operation.
*