AW: [ADSM-L] SLES9 TSM 5.3.2 Linux Client, Unrecognized symbols

[Knoblauch, Josef]

Richard, your information solved the problem.
A new search on the system told me, that glibc-locale-32bit-9 was not
installed.
Only glibc-locale was installed, but not the 32bit version.
After the installation of glibc-locale-32bit-9-200512120222 from SLES9 SP3
everything looks well.

Thanks for your help
Josef

> -Ursprüngliche Nachricht-
> Von: Richard Sims [mailto:[EMAIL PROTECTED]
> Gesendet am: Dienstag, 14. März 2006 14:47
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: [ADSM-L] SLES9 TSM 5.3.2 Linux Client, 
> Unrecognized symbols
> 
> On Mar 14, 2006, at 3:37 AM, Knoblauch, Josef wrote:
> 
> > On SLES9 glibc-32bit-9-200512120222 is installed.
> >
> 
> Josef - This might be a case where the glibc-locale* is not
>  installed, as outlined in APAR IC47520.
> 
>a possibility,  Richard Sims
> 

Re: MSL6030 TSM write failure

[Kurt Beyers]

Jim,
 
It looks indeed to be a HW problem with the library (which is brand new, so 
that cancels option 1 and 2). I was just surprised that the tapes could be 
labelled as data is wrtten to them then too.
 
But apperantly the HW issues only pop-up when you start sending the backup 
data, which are larger then a label of course.
 
thanks,
Kurt



Van: ADSM: Dist Stor Manager namens JN
Verzonden: di 3/14/2006 18:53
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] MSL6030 TSM write failure



Hi Kurt,

   In my experience, the errors that you are seeing are primarily caused by
one of three problems:

1)  The tape drive is dirty and needs to be cleaned
2)  The tape cartridge is bad and needs to be destroyed
3)  The Tape drive has a physical problem that needs to be fixed via
replacement or maintenance.

   I hope one of these solutions works for you.



   Jim

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kurt Beyers
Sent: Tuesday, March 14, 2006 1:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] MSL6030 TSM write failure

Hello,

A quick (?) question. My setup is the following:

TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3
drives).

The library has been defined in TSM and the labelling of the tapes went
fine. However a migrate of the diskpool towards the LTOPool fails with the
following messages:

ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30.
ANR2110I MIGRATE STGPOOL started as process 42.
ANR1000I Migration process 42 started for storage pool DISKPOOL manually,
highMig=90, lowMig=0, duration=No.
ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5).
ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL.
ANR0513I Process 42 opened output volume HK3722L3.
ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3
(OP=WRITE,
Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03,
SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00.,
Description=Command aborted).  Refer to Appendix D in the 'Messages' manual
for
recommended action.
ANR1411W Access mode for volume HK3722L3 now set to "read-only" due to write
error.
ANR0515I Process 42 closed volume HK3722L3.

What am I missing here? The library configuration in TSM is as follows:

-The TSM device driver is used and the library is detected by the
tsmdlst.exe program as follows:

Tivoli Storage Manager -- Device List Utility
Licensed Materials - Property of IBM
5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
Computer Name:  TSM-server
OS Version: 5.2
OS Build #: 3790
TSM Device Driver:  TSMScsi - Running
2 HBAs were detected.
ManufacturerModel  Driver  VersionFirmware
Description


QLogic Corporation  QLA2340ql2300.sys  9.0.2.11 (w32 IP)  3.03.12
QLogic QLA2340  Fibre Channel Adapter
QLogic Corporation  QLA2340ql2300.sys  9.0.2.11 (w32 IP)  0.00.00
QLogic QLA2340  Fibre Channel Adapter
TSM Name ID   LUN  Bus  Port SSN   WWN   TSM
Type  Device Identifier


lb0.0.0.50005- -
LIBRARY   HP  MSL6000 Series  0507
mt1.0.0.51005- - LTO
HP  Ultrium 3-SCSI  G24W
mt2.0.0.52005- - LTO
HP  Ultrium 3-SCSI  G24W
Completed in: 0 days, 0 hours, 0 minutes, 1 seconds.

-The library is defined in TSM with:

tsm: SRV-SPGR-BACKUP_SERVER1>q library f=d
Library Name: MSL6030
Library Type: SCSI
WWN: 00900D06254B8000
Serial Number: 2U2527002X
AutoLabel: No
Reset Drives: No
Last Update by (administrator): ADMIN

tsm: SRV-SPGR-BACKUP_SERVER1>q drive f=d
Library Name: MSL6030
Drive Name: DRIVE1
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 480
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B34589E
Serial Number: HU105252G0

Library Name: MSL6030
Drive Name: DRIVE2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 481
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B34586E
Serial Number: HU105252FH

tsm: SRV-SPGR-BACKUP_SERVER1>q path f=d
Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: MSL6030
Destination Type: LIBRARY
Library:
Node Name:
Device: LB0.0.0.5

Source Name: SRV-SPGR-BACKUP_

Re: Backups of Intel-based Macs

[Richard Sims]

On Mar 14, 2006, at 4:44 PM, Paul Zarnowski wrote:


Intel Macs are starting to show up on our campus and we are being
asked how to back them up.  What are other TSM sites doing to backup
these new beasties?  TSM doesn't support Intel-based Macs yet.


Hi, Paul - Good question...

I recently got one of the new iMac's as a media storage and feeder
for my family room (connecting it to my A/V receiver via optical
audio and S-video). Wonderful machine.

Reading your posting, and Aaron's response about depending upon
Rosetta, I decided to try installing a TSM client (5.2.4). An
awkwardness is that the download file is in .hqx format: PowerPC Macs
are shipped with Stuffit Expander to handle that stuff, but the new
Macs are Intel, so it appears that Apple feels it inappropriate to
ship a non-PowerPC binary. I got SE off the net and installed it, and
it worked fine to generate the TSM installer, which I then ran to
install the TSM client. And the client itself ran fine, as I tried
some basic Archive and Backup operations. Apple's Rosetta is
excellent, as was promised.

I would suggest having one of your "eager adopters" go ahead and give
an existing TSM client level a full workout, with a new nodename.
Have them report back on general functionality and speed.

   Richard Sims  long time Mac guy (why settle for mediocrity?)

Re: ANR0539W messages

[Prather, Wanda]

FWIW, we've run 5.3.2 Win2K3 clients on a 5.2.2 server, no TCP/IP issues from 
the client end.
Running now on 5.3.2 servers, no TCP/IP issues from the client end.  
 
The most common thing I see that will cause a client to experience a TCP/IP 
failure, then reconnect, then TCP/IP failure, then reconnect, is a firewall 
timeout.  
 
TSM clients sometimes noodle around the file system looking for things to back 
up for quite a long time before sending data.  If there is a firewall between 
them and the TSM server, and the firewall detects a lull in traffic, it will 
close the session.  Then when the client is finally ready to send, it opens a 
other session.  Rinse, repeat.   One usually has to adjust the timeout setting 
on the firewall to allow the TSM traffic to idle longer before cutting off the 
session.



From: ADSM: Dist Stor Manager on behalf of Thomas Denier
Sent: Tue 3/14/2006 10:34 AM
To: ADSM-L@VM.MARIST.EDU
Subject: ANR0539W messages



We are seeing a strange situation with some of our clients. The trouble
starts when the client sees a TCP session fail and the server does not. The
client establishes a new session while the server keeps the old session
around with an ever-growing wait time. If the first session was writing to
disk (we use file device classes for incoming backups) the server will
assign a mount point to the replacement session and leave a mount point
assigned to the original session. At some point, the client reaches its
maximum number of mount points and we get ANR0539W messages like the
following:

ANR0539W Transaction failed for session 1234 for node NODENAME. This
node has exceeded its maximum number of mount points.

Our server is TSM 5.2.6.0 running under mainframe Linux. All of the
affected clients are using either 5.3.0.0 or 5.3.2.0 client code. Six
out of seven of the affected clients are Windows 2003 systems. The
seventh is an Intel Linux system. All of the affected clients are
managed by the same organizational unit, which has a history of
somewhat peculiar systems administration practices. I am still
waiting for information on which parts of the network infrastructure
are shared by the affected clients.

Is this a known problem? If not, does anyone have any suggestions for
trouble-shooting?

Re: Backups of Intel-based Macs

[Aaron Becar]

Does Rosetta work?

>>>[EMAIL PROTECTED] 03/14 11:14 am >>>

Intel Macs are starting to show up on our campus and we are being

asked how to back them up.  What are other TSM sites doing to backup

these new beasties?  TSM doesn't support Intel-based Macs yet.


..Paul



--

Paul ZarnowskiPh: 607-255-4757

Manager, Storage Systems  Fx: 607-255-8521

719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]

Backups of Intel-based Macs

[Paul Zarnowski]

Intel Macs are starting to show up on our campus and we are being
asked how to back them up.  What are other TSM sites doing to backup
these new beasties?  TSM doesn't support Intel-based Macs yet.

..Paul


--
Paul ZarnowskiPh: 607-255-4757
Manager, Storage Systems  Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]

Re: ANR0539W messages

[Thomas Denier]

As noted in my original posting, I have clients that see TCP
connections fail when the server does not. I found one additional
piece of possibly useful information in the error log from one of
the clients. Most of the session failures messages in the error log
give a TSM return code of -50 with no details about the underlying
TCP error. However, there was one case where a session failed and
the first attempt to reconnect failed. One of the error messages
for the reconnection failure reported a TCP error number of 10060,
indicating a timeout waiting for a response from the TSM server.

APAR IC48731

[Dennis Melburn W IT743]

Is anyone else having issues with this bug in 5.3.2.3?  Many of my space
reclamation processes and my copy storage pool processes are failing
because of this bug.  Is there any temporary fix for this that anyone
has been able to find?  We have a DR test coming up soon, and since some
of these copy storage pool processes are failing, the data is not able
to be copied for the offsite vaulting and so we may have some issues
with our DR because of missing data.  Any help would be appreciated.
 
 
Mel Dennis

TDP Domino hanging on "query domino"

[Helder Garcia]

... or any other query command that needs domino server connection.

TSM Server 5.3.2.0 on AIX 5.3
Domino Server on AIX 5.3
TSM BA Client and API - 5.3.2.0
TDP Domino - 5.3.0


Example:
---
$ domdsmc_notes query dbb xxx.nsf /inactive

IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 3, Level 0.0
(C) Copyright IBM Corporation 1999, 2004. All rights reserved.

Data Protection for Lotus Domino
Version 5, Release 3, Level 0.0
---

If I force an error, like reseting a database, I got the error message
but the client freezes again:

---
$ domdsmc_notes reset yyy.nsf

IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 3, Level 0.0
(C) Copyright IBM Corporation 1999, 2004. All rights reserved.

Database yyy.nsf reset failed:
Requested operation only allowed while database is being backed up..
---
This indicates that it seems to be able to connect to domino server.

I have to kill -9 it.



"query adsm" works fine:

---
$ domdsmc_notes query adsm

IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 3, Level 0.0
(C) Copyright IBM Corporation 1999, 2004. All rights reserved.

Tivoli Storage Manager Server Connection Information


Nodename ... MYNODE_DOMINO
NetWork Host Name of Server  192.168.0.101
TSM API Version  Version 5, Release 3, Level 2

Server Name  MYSERVER
Server Type  AIX-RS/6000
Server Version . Version 5, Release 3, Level 2.0
Compression Mode ... Client Determined
Domain Name  DOMINO
Active Policy Set .. DOMINO
Default Management Class ... DOMINO
---

My suspicious is that this starts after a failed backup due to lack of
scratch tapes (backup is direct to tape LAN Free). The database might
be marked as being backed up. But I tried to reset some of them
without success (like above).

Any suggestion?

Thanks in advance,
--
Helder Garcia

Re: TSM Server Hosting - dedicated vs. shared

[Allen S. Rout]

>> On Tue, 14 Mar 2006 10:23:38 -0600, Roger Deschner <[EMAIL PROTECTED]> said:

> But as we've grown into our present performance crunch, one thing
> has become clear - being a TSM server is a 24-hour workload. So you
> can't borrow cycles from your clients, except by forcing them to do
> the client compression work for you. Problem is, you can say the
> hard work is the backing up all night, but that's only half of
> it. We spend all day running migration, expiration, storage pool
> backup, dead filespace deletion (ouch!), DB backup, and downtime for
> maintenance. These are tasks you cannot distribute to a client
> system which has its own job to do in the daytime. If anything, our
> database is busier by day than at night.


Hm. "Me too".  I want to enlarge on what Roger is saying, but he's hit
it all.


- Allen S. Rout

Re: MSL6030 TSM write failure

[JN]

Hi Kurt,

   In my experience, the errors that you are seeing are primarily caused by
one of three problems:

1)  The tape drive is dirty and needs to be cleaned
2)  The tape cartridge is bad and needs to be destroyed
3)  The Tape drive has a physical problem that needs to be fixed via
replacement or maintenance.

   I hope one of these solutions works for you.



   Jim

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kurt Beyers
Sent: Tuesday, March 14, 2006 1:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] MSL6030 TSM write failure

Hello,

A quick (?) question. My setup is the following:

TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3
drives).

The library has been defined in TSM and the labelling of the tapes went
fine. However a migrate of the diskpool towards the LTOPool fails with the
following messages:

ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30.
ANR2110I MIGRATE STGPOOL started as process 42.
ANR1000I Migration process 42 started for storage pool DISKPOOL manually,
highMig=90, lowMig=0, duration=No.
ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5).
ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL.
ANR0513I Process 42 opened output volume HK3722L3.
ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3
(OP=WRITE,
Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03,
SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00.,
Description=Command aborted).  Refer to Appendix D in the 'Messages' manual
for
recommended action.
ANR1411W Access mode for volume HK3722L3 now set to "read-only" due to write
error.
ANR0515I Process 42 closed volume HK3722L3.

What am I missing here? The library configuration in TSM is as follows:

-The TSM device driver is used and the library is detected by the
tsmdlst.exe program as follows:

Tivoli Storage Manager -- Device List Utility
Licensed Materials - Property of IBM
5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
Computer Name:  TSM-server
OS Version: 5.2
OS Build #: 3790
TSM Device Driver:  TSMScsi - Running
2 HBAs were detected.
ManufacturerModel  Driver  VersionFirmware
Description


QLogic Corporation  QLA2340ql2300.sys  9.0.2.11 (w32 IP)  3.03.12
QLogic QLA2340  Fibre Channel Adapter
QLogic Corporation  QLA2340ql2300.sys  9.0.2.11 (w32 IP)  0.00.00
QLogic QLA2340  Fibre Channel Adapter
TSM Name ID   LUN  Bus  Port SSN   WWN   TSM
Type  Device Identifier


lb0.0.0.50005- -
LIBRARY   HP  MSL6000 Series  0507
mt1.0.0.51005- - LTO
HP  Ultrium 3-SCSI  G24W
mt2.0.0.52005- - LTO
HP  Ultrium 3-SCSI  G24W
Completed in: 0 days, 0 hours, 0 minutes, 1 seconds.

-The library is defined in TSM with:

tsm: SRV-SPGR-BACKUP_SERVER1>q library f=d
Library Name: MSL6030
Library Type: SCSI
WWN: 00900D06254B8000
Serial Number: 2U2527002X
AutoLabel: No
Reset Drives: No
Last Update by (administrator): ADMIN

tsm: SRV-SPGR-BACKUP_SERVER1>q drive f=d
Library Name: MSL6030
Drive Name: DRIVE1
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 480
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B34589E
Serial Number: HU105252G0

Library Name: MSL6030
Drive Name: DRIVE2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 481
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B34586E
Serial Number: HU105252FH

tsm: SRV-SPGR-BACKUP_SERVER1>q path f=d
Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: MSL6030
Destination Type: LIBRARY
Library:
Node Name:
Device: LB0.0.0.5

Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: DRIVE1
Destination Type: DRIVE
Library: MSL6030
Node Name:
Device: mt1.0.0.5

Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: DRIVE2
Destination Type: DRIVE
Library: MSL6030
Node Name:
Device: mt2.0.0.5

thanks,
Kurt

Re: TDP for Exchange: 0xc7fe1f42

[Del Hoobler]

Eric,

I need to ask... since you didn't indicate...

Did you add the database to the Recovery Storage Group
before performing the restore?

Does the storage group name AND database name
EXACTLY match (including casing and and all characters)
the one that was in the backup?

The Exchange Server will fail the backup if either
of those two things is not true when restoring to the
Recovery Storage Group.

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 03/14/2006
10:13:01 AM:

> Hi *SM-ers!
> A restore of a Exchange 2003 server to a Recovery Storage Group on a
> recovery server fails with the following message is the tdpexc.log:
>
> 03/14/2006 15:25:15 Restore of KL1010WF-SG1 failed.
> 03/14/2006 15:25:15 ACN5798E MS Exchange API HRESERESTORECOMPLETE()
> failed with HRESULT: 0xc7fe1f42 - Database not found. 03/14/2006
> 15:25:15 Total backups inspected:   4
> 03/14/2006 15:25:15 Total backups requested for restore:   4
> 03/14/2006 15:25:15 Total backups restored:3
> 03/14/2006 15:25:15 Throughput rate:   10,664.33
> Kb/Sec
> 03/14/2006 15:25:15 Total bytes transferred:
> 3,640,110,250
> 03/14/2006 15:25:15 Elapsed processing time:   333.34
> Secs
> 03/14/2006 15:25:15 ACN0151E Errors occurred while processing the
> request.
>
> What could be the cause of this error?
> Thank you very much for any reply in advance!
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines

Re: OFFSITE TAPES

[Bos, Karel]

The restore vol XX command will mark volume XX as destroyed.
Upd vol st=reado/readw for the volume(s) brought back will also be
needed. 

Regards,

Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bob Booth - UIUC
Sent: dinsdag 14 maart 2006 17:39
To: ADSM-L@VM.MARIST.EDU
Subject: Re: OFFSITE TAPES

On Tue, Mar 14, 2006 at 11:35:59AM -0500, Lepre, James wrote:
> Hello Everyone,
>
>I need to bring back some offsite tapes for a restore.  How do I 
> check them into the library, and then force Tivoli to use them.  I 
> have a tape that broke and now I need to bring back the offsite copy, 
> but I am not sure what how to set this up.  Should I bring back every 
> tape for that node that is offsite, any help is much appreciated.

Mark the tape that is broken as 'destroyed'

Run a restore volume XX preview=yes

This will give you the list of tapes to return (it could be a long list)

Check them into your library as 'private' volumes

Run the restore volume XX

That *should* do it.

cheers,

bob

Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel
bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd,
verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te
vernietigen.
Aangezien de integriteit van het bericht niet veilig gesteld is middels
verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden
voor de inhoud daarvan.
Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven
wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij
enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit
bericht.
 
Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder
Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle
andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing.
Deze worden u op aanvraag direct kosteloos toegezonden.
 
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does not warrant that this transmission is virus-free and will not be
liable for any damages resulting from any virus transmitted.
 
On all offers and agreements under which Atos Origin supplies goods and/or
services of whatever nature, the Terms of Delivery from Atos Origin
exclusively apply. 
The Terms of Delivery shall be promptly submitted to you on your request.

Re: OFFSITE TAPES

[Ben Bullock]

So I believe what you are saying is that a Primary copy of some
data has been destroyed and you want to recreate the onsite copy.

Here is our procedure that is somewhat specific for a 3494 tape
library, but it has all the steps:


 Note: Words in ITALICS are examples of tape/storage pool names. You
must substitute these values with the correct ones.

   1. Update TSM database to reflect volume is destroyed.
  * TSM> update vol C00252 access=destroyed

   2. Find out what tape/tapes from the offsite copypoool are needed
from vault.
  * TSM> restore vol C00252 preview=yes
  * do "q proc" until process is gone.
  * TSM> q act sear=anr1255w (to get the list of tape/tapes it
wants).
   There will be a bunch of entries that look something like
this:

04/01/98   14:27:50  ANR1233I Restore preview of volumes in primary
storage
  pool VMS_INCR_TAPEPOOL started as process 212.
04/01/98   14:27:50  ANR1255W Files on volume C00050 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:27:51  ANR1255W Files on volume C00239 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:27:51  ANR1255W Files on volume C00058 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:28:10  ANR1255W Files on volume C00032 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:28:56  ANR1255W Files on volume C00260 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:28:56  ANR1255W Files on volume C00083 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:28:56  ANR1255W Files on volume C0 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:29:16  ANR1255W Files on volume C00268 cannot be restored
-
  access mode is "unavailable" or "offsite".
04/01/98   14:29:17  ANR1235I Restore process 212 ended for volumes in
storage
  pool VMS_INCR_TAPEPOOL.
04/01/98   14:29:17  ANR1241I Restore preview of volumes in primary
storage
  pool VMS_INCR_TAPEPOOL has ended.  Files Restored:
43070,
  Bytes Restored: 27207363132.

  In this case all 8 of these tapes would need to be retrieved to
restore the data from the bad tape.

   3. Retrieve offsite tape/tapes from vault and load into the library.

   4. Check the offsite tape/tapes into library.
  * TSM> checkin libvol LIBRARYX C00016 stat=private devt=3590

   5. Update access to the tape/tapes just loaded.
  * TSM> update vol C00016 acc=readonly

   6. Restore the files back to primary tapepool.
  * TSM> restore vol C00252
  It may take a while.

   7. Check to see that primary storage pool is up to date.
  * TSM> restore stg AIX_INCR_TAPEPOOL preview=yes
  * TSM> q act (preview should say 0 files restored, if not STOP
and call ADSMONCALL.)
  * To find out what pool the destroyed tape belonged to, use
the 'q vol C00252' command.

   8. Return tape/tapes 'restored from' back into the vault.
  * TSM> update vol C00016 access=offsite
  * TSM> checkout libvol LIBRARYX C00016 remove=yes
  * tape/tapes should be put in I/O slot by robot

   9. Remove the damaged tape from the database.
  * TSM> delete vol C00252
  * If this command fails, contact ADSMoncall before removing
the tape from the library.

  10. Remove tape from tape library if not already done so.
  * TSM> checkout libvol LIBRARYX C00252 remove=yes  


Ben

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lepre, James
Sent: Tuesday, March 14, 2006 9:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: OFFSITE TAPES

Hello Everyone,

   I need to bring back some offsite tapes for a restore.  How do I
check them into the library, and then force Tivoli to use them.  I have
a tape that broke and now I need to bring back the offsite copy, but I
am not sure what how to set this up.  Should I bring back every tape for
that node that is offsite, any help is much appreciated.

Thank you 

James 

Re: OFFSITE TAPES

[Bob Booth - UIUC]

On Tue, Mar 14, 2006 at 11:35:59AM -0500, Lepre, James wrote:
> Hello Everyone,
>
>I need to bring back some offsite tapes for a restore.  How do I
> check them into the library, and then force Tivoli to use them.  I have
> a tape that broke and now I need to bring back the offsite copy, but I
> am not sure what how to set this up.  Should I bring back every tape for
> that node that is offsite, any help is much appreciated.

Mark the tape that is broken as 'destroyed'

Run a restore volume XX preview=yes

This will give you the list of tapes to return (it could be a long list)

Check them into your library as 'private' volumes

Run the restore volume XX

That *should* do it.

cheers,

bob

Re: OFFSITE TAPES

[Lepre, James]

Hello Everyone,

   I need to bring back some offsite tapes for a restore.  How do I
check them into the library, and then force Tivoli to use them.  I have
a tape that broke and now I need to bring back the offsite copy, but I
am not sure what how to set this up.  Should I bring back every tape for
that node that is offsite, any help is much appreciated.

Thank you 

James 

Re: TSM Server Hosting - dedicated vs. shared

[Roger Deschner]

Hmmm. I'm facing a similar issue, even though my database is "only" 210
GB. But mine churns a LOT. Finding time for expiration is driving me
nuts. I've been designing an approach that will let me either run
multiple images on one server, or to distribute them to separate
physical machines. Realistically, I think I'm going to wind up with six
images spread across two large AIX boxes in two separate locations a
mile apart.

Alan Rout of the University of Florida has done a lot of work towards
standardizing and rationalizing this server-splitting process. Comments,
Alan?

But as we've grown into our present performance crunch, one thing has
become clear - being a TSM server is a 24-hour workload. So you can't
borrow cycles from your clients, except by forcing them to do the client
compression work for you. Problem is, you can say the hard work is the
backing up all night, but that's only half of it. We spend all day
running migration, expiration, storage pool backup, dead filespace
deletion (ouch!), DB backup, and downtime for maintenance. These are
tasks you cannot distribute to a client system which has its own job to
do in the daytime. If anything, our database is busier by day than at
night. Furthermore, the administrator of a client system might really
resent having its potential maintenance downtime hours so badly
restricted. So I'd actually say, your greatest struggle with this notion
will be political, but as has been said, your're also going to have a
bear of a time organizing it all, especially on systems you do not
directly control. I think you will be overwhelmed.

There is no free lunch, sorry to say.

P.S. Orville is right about licensing. A license is sold based on the
number of processors - client or server. If you add a 4-processor system
to your environment, whether it serves as TSM client, TSM server, or
both, it counts as +4 towards your grand total. This slightly, but not
strongly, favors running your TSM servers on systems with extremely fast
individual processors. (IBM sells these.)

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]


On Mon, 13 Mar 2006, Orville Lantto wrote:

>TSM licenses (and pricing) has been based on the environment for some
years.  Check with your IBM Business Partner to get the details.
>
>Orville L. Lantto
>Glasshouse Technologies, Inc.
>Cell:  952-738-1933
>
>
>
>
>From: ADSM: Dist Stor Manager on behalf of Robin Sharpe
>Sent: Mon 3/13/2006 2:19 PM
>To: ADSM-L@VM.MARIST.EDU
>Subject: [ADSM-L] TSM Server Hosting - dedicated vs. shared
>
>
>
>Orville,
>Thanks for your thoughts.  We do use Control-M for all of our scheduling in
>the Unix environment, and are moving towards Windows deployment too.
>I am surprised, though, about your comment on licensing.  I thought each
>TSM server instance on a separate physical server needed a license (per
>processor).  Is this not true? Is it a new policy?
>
>Robin Sharpe
>Berlex Labs
>
>
>|-+--->
>| |   Orville Lantto  |
>| |   <[EMAIL PROTECTED]|
>| |   SHOUSE.COM> |
>| |   Sent by: "ADSM: Dist|
>| |   Stor Manager"   |
>| |   <[EMAIL PROTECTED]|
>| |   U>  |
>| |   |
>| |   |
>| |   03/13/2006 01:40 PM |
>| |   Please respond to   |
>| |   "ADSM: Dist Stor|
>| |   Manager"|
>| |   |
>|-+--->
>  
> >|
>  |
> |
>  |
> |
>  |To: ADSM-L@VM.MARIST.EDU
> |
>  |cc: 
> |
>  |Subject:
> |
>  |Re: 
> |
>  
> >|
>
>
>
>The approach is valid and can reap significant backup/restore time benefits
>for the clients.
>Two points:
>
> 1) No new licensing cost are involved.  TSM is
>licensed by the environment, not the number of TSM servers.
>
> 2) Consider the complexity of resources scheduling
>between

Re: TDP for Exchange: 0xc7fe1f42

[David W Litten]

Are you running Exchange on MS Clusters? Was the database off-line when the
backup was run?




 "Loon, E.J. van -
 SPLXM"
 <[EMAIL PROTECTED]  To
 M.COM>ADSM-L@vm.marist.edu
 Sent by: "ADSM:cc
 Dist Stor
 Manager"  Subject
 <[EMAIL PROTECTED] [ADSM-L] TDP for Exchange:
 .edu> 0xc7fe1f42


 03/14/2006 10:13
 AM


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






Hi *SM-ers!
A restore of a Exchange 2003 server to a Recovery Storage Group on a
recovery server fails with the following message is the tdpexc.log:

03/14/2006 15:25:15 Restore of KL1010WF-SG1 failed.
03/14/2006 15:25:15 ACN5798E MS Exchange API HRESERESTORECOMPLETE()
failed with HRESULT: 0xc7fe1f42 - Database not found. 03/14/2006
15:25:15 Total backups inspected:   4
03/14/2006 15:25:15 Total backups requested for restore:   4
03/14/2006 15:25:15 Total backups restored:3
03/14/2006 15:25:15 Throughput rate:   10,664.33
Kb/Sec
03/14/2006 15:25:15 Total bytes transferred:
3,640,110,250
03/14/2006 15:25:15 Elapsed processing time:   333.34
Secs
03/14/2006 15:25:15 ACN0151E Errors occurred while processing the
request.

What could be the cause of this error?
Thank you very much for any reply in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


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

Re: ANR0539W messages

[Richard Sims]

Thomas - If you don't get a good answer from that client group,
 you may have to look into server options
THROUGHPUTDatathreshold and THROUGHPUTTimethreshold as a way to
deal with the irregularities.

   Richard Sims

ANR0539W messages

[Thomas Denier]

We are seeing a strange situation with some of our clients. The trouble
starts when the client sees a TCP session fail and the server does not. The
client establishes a new session while the server keeps the old session
around with an ever-growing wait time. If the first session was writing to
disk (we use file device classes for incoming backups) the server will
assign a mount point to the replacement session and leave a mount point
assigned to the original session. At some point, the client reaches its
maximum number of mount points and we get ANR0539W messages like the
following:

ANR0539W Transaction failed for session 1234 for node NODENAME. This
node has exceeded its maximum number of mount points.

Our server is TSM 5.2.6.0 running under mainframe Linux. All of the
affected clients are using either 5.3.0.0 or 5.3.2.0 client code. Six
out of seven of the affected clients are Windows 2003 systems. The
seventh is an Intel Linux system. All of the affected clients are
managed by the same organizational unit, which has a history of
somewhat peculiar systems administration practices. I am still
waiting for information on which parts of the network infrastructure
are shared by the affected clients.

Is this a known problem? If not, does anyone have any suggestions for
trouble-shooting?

Re: restoring backup sets from one node to another

[Andrew Raibeck]

Timothy,

I do not know how to qalify or quantify what is working and what is not
working without more specific info, such as copy & paste of the command
you are running and the output you are getting.

Perhaps what you need to do is prefix the source file name with the
original server name, i.e., instead of poa:swsp/, do doqcrps\poa:swsp/ ?

Regards,

Andy

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

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

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

"ADSM: Dist Stor Manager"  wrote on 2006-03-14
07:19:55:

> William,
>
> Thanks again,
>
> Tried it the command is,
>
> restore backupset monthlydocgrppoa.410125866 poa:swsp/
> DOQCW2\poa:restore/  -subdir=yes
>
> That helps, but does not resolve the problem of restoring a backupset
> where the server from which the set was created no longer exists. Would
> this mean the client would have to rename and existing server?
> (not easy in Novell) according to the novell person or build a new
> server with the former server's name to do a backupset restore?
>
>
>
> William wrote:
>
> > Yes you can. As Andy said, you must use the original node name.
> >
> > On 3/13/06, Timothy Hughes <[EMAIL PROTECTED]> wrote:
> > >
> > > Andrew,
> > >
> > > Thanks, Does this mean that we cannot restore a backupset to a
> > > different server?
> > >
> > >
> > > Andrew Raibeck wrote:
> > >
> > > > The SET ACCESS and -FROMNODE options do not pertain to backup
sets. You
> > > > cannot use -FROMNODE to restore data from another node's backup
sets.
> > > You
> > > > must connect with the node name for which the backup set was
created.
> > > >
> > > > Also, backup sets contain backup data only; they do not contain
archive
> > > > data.
> > > >
> > > > Regards,
> > > >
> > > > Andy
> > > >
> > > > Andy Raibeck
> > > > IBM Software Group
> > > > Tivoli Storage Manager Client Development
> > > > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> > > > Internet e-mail: [EMAIL PROTECTED]
> > > >
> > > > IBM Tivoli Storage Manager support web page:
> > > >
> > > http://www-306.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
> > > >
> > > > The only dumb question is the one that goes unasked.
> > > > The command line is your friend.
> > > > "Good enough" is the enemy of excellence.
> > > >
> > > > "ADSM: Dist Stor Manager"  wrote on
2006-03-13
> > > > 09:08:34:
> > > >
> > > > > I am having problems restoring a backup set from one node to
> > > > > another. I set access archive * * on node DOQCRPS and tried to
> > > > > restore the same backupset to DOQCW2, but I get the error
> > > > > ANS1934E Backup set 'monthlydocqrppoi.410125866' not found.
> > > > > I checked the backupset name and it is still active and the name
is
> > > > > correct.
> > > > >
> > > > > If I try a set access on DOQCRPS that specifies a path (e.g.,
set
> > > > > access archive poi:/* *) I always get ANS1083E No files have
> > > previously
> > > > > been archived for 'poi:/*'
> > > > >
> > > > >
> > > > > The command used that got ANS1934E on CW2 was:
> > > > >
> > > > > restore backupset monthlydoqcrppoi.410125866 poi:swsp/
poi:restore/
> > > > > -subdir=yes
> > > > >
> > > > > This backupset was created on DOQCRPS and I issued "set access
archive
> > > > > * *" on DOQCRPS before attempting the restore on CW2. But I'm
not sure
> > > > > the command is working right because when I try to set access to
a
> > > > > specified path, e.g. "set access archive poi:/* *" I get the
other
> > > error
> > > > >
> > > > > ANS1083E.
> > > > >
> > > > >
> > > > > We should be able to restore a backupset created on one server
to a
> > > > > different server correct? Is there something I am missing?
> > > > >
> > > > > P.S. - Is it just me or is information regarding backups
extremely
> > > > > limited?
> > > > >
> > > > > Thanks for any help in advance!
> > > > >
> > > > >
> > > > > TSM 5.3.2.1
> > > > > Novell client 5.3.0.12
> > > > >
> > > > >
> > > > > Thanks
> > >

TDP for Exchange: 0xc7fe1f42

[Loon, E.J. van - SPLXM]

Hi *SM-ers!
A restore of a Exchange 2003 server to a Recovery Storage Group on a
recovery server fails with the following message is the tdpexc.log:

03/14/2006 15:25:15 Restore of KL1010WF-SG1 failed.
03/14/2006 15:25:15 ACN5798E MS Exchange API HRESERESTORECOMPLETE()
failed with HRESULT: 0xc7fe1f42 - Database not found. 03/14/2006
15:25:15 Total backups inspected:   4
03/14/2006 15:25:15 Total backups requested for restore:   4
03/14/2006 15:25:15 Total backups restored:3
03/14/2006 15:25:15 Throughput rate:   10,664.33
Kb/Sec
03/14/2006 15:25:15 Total bytes transferred:
3,640,110,250
03/14/2006 15:25:15 Elapsed processing time:   333.34
Secs
03/14/2006 15:25:15 ACN0151E Errors occurred while processing the
request. 

What could be the cause of this error?
Thank you very much for any reply in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


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

Re: restoring backup sets from one node to another

[Timothy Hughes]

William,

Thanks again,

Tried it the command is,

restore backupset monthlydocgrppoa.410125866 poa:swsp/
DOQCW2\poa:restore/  -subdir=yes

That helps, but does not resolve the problem of restoring a backupset
where the server from which the set was created no longer exists. Would
this mean the client would have to rename and existing server?
(not easy in Novell) according to the novell person or build a new
server with the former server's name to do a backupset restore?



William wrote:

> Yes you can. As Andy said, you must use the original node name.
>
> On 3/13/06, Timothy Hughes <[EMAIL PROTECTED]> wrote:
> >
> > Andrew,
> >
> > Thanks, Does this mean that we cannot restore a backupset to a
> > different server?
> >
> >
> > Andrew Raibeck wrote:
> >
> > > The SET ACCESS and -FROMNODE options do not pertain to backup sets. You
> > > cannot use -FROMNODE to restore data from another node's backup sets.
> > You
> > > must connect with the node name for which the backup set was created.
> > >
> > > Also, backup sets contain backup data only; they do not contain archive
> > > data.
> > >
> > > Regards,
> > >
> > > Andy
> > >
> > > Andy Raibeck
> > > IBM Software Group
> > > Tivoli Storage Manager Client Development
> > > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> > > Internet e-mail: [EMAIL PROTECTED]
> > >
> > > IBM Tivoli Storage Manager support web page:
> > >
> > http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
> > >
> > > The only dumb question is the one that goes unasked.
> > > The command line is your friend.
> > > "Good enough" is the enemy of excellence.
> > >
> > > "ADSM: Dist Stor Manager"  wrote on 2006-03-13
> > > 09:08:34:
> > >
> > > > I am having problems restoring a backup set from one node to
> > > > another. I set access archive * * on node DOQCRPS and tried to
> > > > restore the same backupset to DOQCW2, but I get the error
> > > > ANS1934E Backup set 'monthlydocqrppoi.410125866' not found.
> > > > I checked the backupset name and it is still active and the name is
> > > > correct.
> > > >
> > > > If I try a set access on DOQCRPS that specifies a path (e.g., set
> > > > access archive poi:/* *) I always get ANS1083E No files have
> > previously
> > > > been archived for 'poi:/*'
> > > >
> > > >
> > > > The command used that got ANS1934E on CW2 was:
> > > >
> > > > restore backupset monthlydoqcrppoi.410125866 poi:swsp/ poi:restore/
> > > > -subdir=yes
> > > >
> > > > This backupset was created on DOQCRPS and I issued "set access archive
> > > > * *" on DOQCRPS before attempting the restore on CW2. But I'm not sure
> > > > the command is working right because when I try to set access to a
> > > > specified path, e.g. "set access archive poi:/* *" I get the other
> > error
> > > >
> > > > ANS1083E.
> > > >
> > > >
> > > > We should be able to restore a backupset created on one server to a
> > > > different server correct? Is there something I am missing?
> > > >
> > > > P.S. - Is it just me or is information regarding backups extremely
> > > > limited?
> > > >
> > > > Thanks for any help in advance!
> > > >
> > > >
> > > > TSM 5.3.2.1
> > > > Novell client 5.3.0.12
> > > >
> > > >
> > > > Thanks
> >

Re: TSM client API upgrade and TDP for oracle

[Tae Kim]

Thanks for the answer!

Now I just have to get approval for the upgrade =)


Tae



"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
03/13/2006 05:43 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] TSM client API upgrade and TDP for oracle






Hi Tae!
Not, this is not nessesary. The API client is only used during a backup,
so if no backup is running, you can replace all files during
installation and no restart is required.
However, I would wait a few days before starting the upgrade. The
5.3.3.0 client will be released this month.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Tae Kim
Sent: vrijdag 10 maart 2006 17:39
To: ADSM-L@VM.MARIST.EDU
Subject: TSM client API upgrade and TDP for oracle

Hi guys and gals,

Currently I am trying to upgrade various AIX TSM clients which are
v5.2.2 or V5.1.5 to TSM client version 5.3.2.  I thought that clients
can be upgraded with out having to upgrade TSM API but I was wrong.  I
do need to upgrade both the API and the clients. The issue is that these
TSM clients also have TDP for oracle running.  Will the upgrade of the
TSM API require a restart of oracle DB (like when upgrading TDP for
oracle you need to restart oracle).

Thanks for your input.


Tae





"T. Lists" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
03/10/2006 10:56 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
[ADSM-L] What table is the "q drive"  WWN and Serial number stored in?






Q drive gives a WWN and serial number, however if you just select from
the DRIVES table you don't get that.
What table is that information stored in?

tsm: TSM02>q drive * drive01 f=d

Library Name: 3584LIB
Drive Name: DRIVE01
Device Type: LTO
On-Line: Yes
Read Formats:
ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats:
ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Element: 270
Drive State: EMPTY
Allocated to:
 *  WWN: 500507630001F012
 *  Serial Number: 9110108472
Last Update by (administrator): STACY
Last Update Date/Time: 03/09/06   16:16:17
Cleaning Frequency
(Gigabytes/ASNEEDED/NONE): NONE


tsm: TSM02>select * from drives where
drive_name='DRIVE01'

  LIBRARY_NAME: 3584LIB
DRIVE_NAME: DRIVE01
   DEVICE_TYPE: LTO
ONLINE: YES
  READ_FORMATS: ULTRIUM2C,ULTRIU
 WRITE_FORMATS: ULTRIUM2C,ULTRIU
   ELEMENT: 270
  ACS_DRIVE_ID:
   DRIVE_STATE: EMPTY
  ALLOCATED_TO:
LAST_UPDATE_BY: STACY
   LAST_UPDATE: 2006-03-09 16:16:17.00
CLEAN_FREQ:
  DRIVE_SERIAL:



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com




+=+
This message may contain confidential and/or privileged information.  If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose or take any action based on
this message or any information herein.  If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation.
+=+


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




+=+
This message may contain confidential and/or privileged
information.  If you are not the addressee or authorized to
receive this for the addressee, you must not use, copy,
disclose or take any action based on this message or any
information herein.  If you have received this message in
error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation.
+=+

Re: restoring backup sets from one node to another

[Timothy Hughes]

Thanks Chris,

This may be an option to consider.

Chris Pasztor wrote:

> There is away around this issue and I use it on occasions by defining a new 
> node
> I call ADHOC, I then by granting the ADHOC node a proxy for the source node I 
> do
> a selective backup of the files then create the backupset. Then I define the 
> new
> node on the target server define the backupset and restore it.
>
> Chris Pasztor
> S/390 Systems Programmer/DB2 Database Administrator
> Mantrack
> Payroll, HR Service Solutions and Facilities Management
>
> Phone: Ph: +61 1800 060 171
> DDL:
>
>   
>
>+61 (3) 9541 2605
> Fax:: +61 (3) 9562 98221
> Cell:   0411 229 151
> Email   : [EMAIL PROTECTED]
> URL: www.mantrack.com 

Re: SLES9 TSM 5.3.2 Linux Client, Unrecognized symbols

[Richard Sims]

On Mar 14, 2006, at 3:37 AM, Knoblauch, Josef wrote:


On SLES9 glibc-32bit-9-200512120222 is installed.



Josef - This might be a case where the glibc-locale* is not
installed, as outlined in APAR IC47520.

  a possibility,  Richard Sims

MSL6030 TSM write failure

[Kurt Beyers]

Hello,
 
A quick (?) question. My setup is the following:
 
TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3 drives).
 
The library has been defined in TSM and the labelling of the tapes went fine. 
However a migrate of the diskpool towards the LTOPool fails with the following 
messages:
 
ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30.
ANR2110I MIGRATE STGPOOL started as process 42.
ANR1000I Migration process 42 started for storage pool DISKPOOL manually,
highMig=90, lowMig=0, duration=No.
ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5).
ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL.
ANR0513I Process 42 opened output volume HK3722L3.
ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3 (OP=WRITE,
Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03,
SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00.,
Description=Command aborted).  Refer to Appendix D in the 'Messages' manual for
recommended action.
ANR1411W Access mode for volume HK3722L3 now set to "read-only" due to write
error.
ANR0515I Process 42 closed volume HK3722L3.
 
What am I missing here? The library configuration in TSM is as follows:
 
-The TSM device driver is used and the library is detected by the tsmdlst.exe 
program as follows:
 
Tivoli Storage Manager -- Device List Utility
Licensed Materials - Property of IBM
5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
Computer Name:  TSM-server
OS Version: 5.2
OS Build #: 3790
TSM Device Driver:  TSMScsi - Running
2 HBAs were detected.
ManufacturerModel  Driver  VersionFirmware 
Description

QLogic Corporation  QLA2340ql2300.sys  9.0.2.11 (w32 IP)  3.03.12  
QLogic QLA2340  Fibre Channel Adapter
QLogic Corporation  QLA2340ql2300.sys  9.0.2.11 (w32 IP)  0.00.00  
QLogic QLA2340  Fibre Channel Adapter
TSM Name ID   LUN  Bus  Port SSN   WWN   TSM 
Type  Device Identifier 

lb0.0.0.50005- - 
LIBRARY   HP  MSL6000 Series  0507  
mt1.0.0.51005- - LTO
   HP  Ultrium 3-SCSI  G24W  
mt2.0.0.52005- - LTO
   HP  Ultrium 3-SCSI  G24W  
Completed in: 0 days, 0 hours, 0 minutes, 1 seconds.
 
-The library is defined in TSM with:
 
tsm: SRV-SPGR-BACKUP_SERVER1>q library f=d
Library Name: MSL6030
Library Type: SCSI
WWN: 00900D06254B8000
Serial Number: 2U2527002X
AutoLabel: No
Reset Drives: No
Last Update by (administrator): ADMIN
 
tsm: SRV-SPGR-BACKUP_SERVER1>q drive f=d
Library Name: MSL6030
Drive Name: DRIVE1
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 480
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B34589E
Serial Number: HU105252G0

Library Name: MSL6030
Drive Name: DRIVE2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 481
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B34586E
Serial Number: HU105252FH
 
tsm: SRV-SPGR-BACKUP_SERVER1>q path f=d
Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: MSL6030
Destination Type: LIBRARY
Library:
Node Name:
Device: LB0.0.0.5

Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: DRIVE1
Destination Type: DRIVE
Library: MSL6030
Node Name:
Device: mt1.0.0.5
 
Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: DRIVE2
Destination Type: DRIVE
Library: MSL6030
Node Name:
Device: mt2.0.0.5
   
thanks,
Kurt
 
 

Re: ANS1950E -Backup using Microsoft Volume Shadow Copy Failed Error in Client 5.3.0

[Gerhard Ginzler]

Nancy,

look at APAR IC47984 and try the newest path client:
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r3/Windows/x32/v532/

regards
Gerhard

Kurt Beyers schrieb:

Nancy,

The latest news I've got from IBM is that it will be solved in the TSM 5.3.3 BA 
client. The latter will become available somewhere this month.

At the time being, I've seperated the file system and Windows system objects 
into two different schedules. The issue (VSS backup of Windows system objects 
in combination with a VSS file system backup) is not met with this workaround.

best regards,
Kurt




Van: ADSM: Dist Stor Manager namens Nancy L Backhaus
Verzonden: ma 3/13/2006 20:55
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] ANS1950E -Backup using Microsoft Volume Shadow Copy Failed 
Error in Client 5.3.0



Hello,

We are still seeing the shadow copy issue in 5.3.2.2.  Anyone else still
seeing the same issue or do I need to open a call with IBM?


TSM Server - 5.3.2.2
Op System AIX 5.3
TSM Windows 2003 Client - 5.3.2.2

snipit from dsmerror.log


03/13/2006 00:11:31 CreateSnapshotSet(): pAsync->QueryStatus() returns
hr=VSS_E_PROVIDER_VETO
03/13/2006 00:11:33 ANS1999E Incremental processing of '\\tsmclient\d$'
stopped.
03/13/2006 00:11:33 ANS1950E Backup using Microsoft volume shadow copy
failed.



Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979

CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole 
use of the intended recipient(s) and may contain proprietary, confidential, 
trade secret or privileged information.  Any unauthorized review, use, 
disclosure or distribution is prohibited and may be a violation of law.  If you 
are not the intended recipient or a person responsible for delivering this 
message to an intended recipient, please contact the sender by reply email and 
destroy all copies of the original
message.

SLES9 TSM 5.3.2 Linux Client, Unrecognized symbols

[Knoblauch, Josef]

Hi all,

when I try to backup files with german umlauts I found the following error
in dmserror.log

03/11/2006 16:04:57 fioScanDirEntry(): Object '/home/ad03062/Ätest' contains
unrecognized symbols for current locale, skipping...
03/11/2006 16:04:57 fioScanDirEntry(): Object '/home/ad03062/aäöü' contains
unrecognized symbols for current locale, skipping...
03/11/2006 16:10:50 fioScanDirEntry(): Object '/home/ad03062/Ätest' contains
unrecognized symbols for current locale, skipping...
03/11/2006 16:10:50 fioScanDirEntry(): Object '/home/ad03062/aäöü' contains
unrecognized symbols for current locale, skipping...
03/11/2006 22:16:41 fioScanDirEntry(): Object
'/usr/share/doc/sdb/en/html/keylist.VERSCHLÜSSELT.html' contains
unrecognized symbols for current locale, skipping...

Environment:
TSM Client 5.3.2-2 running on SLES9 64 bit, native on IBM zSeries
TSM Server 5.2.3 running on AIX 5.2

TSM scheduler dsmcad starting  via /etc/init.d start script within locales
set to

LANG=en_US
[EMAIL PROTECTED]

export LANG LC_CTYPE

On SLES9 glibc-32bit-9-200512120222 is installed.

Does anybody know how to get out of these problems?

Kind regards
Josef Knoblauch 

__ 
Josef Knoblauch 
ARAG IT GmbH 
mailto: josef dot knoblauch at arag dot de