Re: TSM 5.4 cautions

2007-01-26 Thread Bob Booth
On Fri, Jan 26, 2007 at 02:33:20PM -0500, Richard Sims wrote:
> Look, before leaping into TSM 5.4 ...
> Cautionary/advisory Technotes are starting to appear for 5.4,
> as for example 1249083.  Do a search, and pore over the Readme
> file, before committing to an install.

Agreed!

I cautioned the 10 Intel Mac users to read the files and search the web for
any known problems.  They are testing it now, and have had 'no crashes' with
the client (so far).

bob


Re: Expired directories with DIRMC and restore

2007-01-26 Thread Andrew Raibeck
That sure doesn't sound right I just tried it myself with a very
current client level (Windows) and could not reproduce your results.

Do you have multiple TSM servers? Is it possible you're updating one
server and connecting GUI to another? From your email it doesn't sound
like it, but I guess it doesn't hurt to double-check.

Can you open a command line interface and do "query backup c:\testdir\
-subdir=yes -ina"? What do the results show? (Note: "c:\testdir" is
whatever play directory you used)

In answer to your question, though, the directory structure is backed up
so, if for no other reason, you can restore it. On some systems it might
not be meaningful; but on systems like Windows, where directories have
security and other settings, being able to restore the directories might
be important to your organization.

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.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 01/26/2007
09:32:03 AM:

> I ran a test backing up a directory structure with files and
> subdirectories to a reto=20 management class for the files and
> directories via DIRMC to a reto=0 management class.  After the backup I
> deleted the data and re-ran the incremental backup to expire the objects
> from TSM.  I confirmed the objects were now INACTIVE_VERSION in the
> backups table then ran expiration to purge from the DB (reto=0).
> Checking the backups table again I can see no directory objects existed,
> just the files.
>
> Next, I launched the GUI to test if I could expand the directory tree
> and restore the data.  Both worked.  Path preserved on the restore as
> well.
>
> So my confusion is, what is the directory structure for?  I would have
> suspected I would not have been able to expand the tree in the GUI or
> restore the data to its original location.
>
> We are looking to mix long term data with short term data in our TSM
> servers and want to prevent all directory objects from being bound to
> the longest retention policy mgmtclass using the DIRMC option.  This
> test was to see the implications of not having a directory structure,
> which surprisingly had no affect...  Am I missing something?
>
> Thanks.
> 
>
> If you are not an intended recipient of this e-mail, please notify
> the sender, delete it and do not read, act upon, print, disclose,
> copy, retain or redistribute it. Click here for important additional
> terms relating to this e-mail. http://www.ml.com/email_terms/
> 


Re: Expired directories with DIRMC and restore

2007-01-26 Thread Richard Sims

Denis -

The experimental results which you report certainly disagree with the
published descriptions of how the GUI should behave in the absence of
path directories.  Technote 1157531 in particular is at odds with
what you found.  I recommend at least filling in the Comments box at
the bottom of that Technote page with your findings, if not contact
TSM Support regarding the apparent discrepancy.

   Richard Sims


TSM 5.4 cautions

2007-01-26 Thread Richard Sims

Look, before leaping into TSM 5.4 ...
Cautionary/advisory Technotes are starting to appear for 5.4,
as for example 1249083.  Do a search, and pore over the Readme
file, before committing to an install.

  Richard Sims


Re: Disposition of Failed Storage Devices

2007-01-26 Thread Lamb, Charles P.
Mr. Kauffman...

How does your company handle the Disposition of Failed Storage Devices??
After further discussions with my boss, we have many camps with
differing points of view. 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kauffman, Tom
Sent: Friday, January 26, 2007 10:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Disposition of Failed Storage Devices

Given the security group's position, I think your options are
sledghammer or iron smelter. And you'll really need to put everything
you've got into the sledgehammer, if you go that route. A thermal lance
or oxygen cutting torch might also fill the requirements.

I doubt you'll get anything in writing from either IBM or EMC that will
be satisfactory. You'll also need to get quotes from both on how much
the maintenance fees will increase if the failed media device is
rendered non-salvageable before return.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lamb, Charles P.
Sent: Friday, January 26, 2007 11:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Disposition of Failed Storage Devices

Hi

Our IT management is looking at implementing a process for disposition
of failed storage devices. We have a hardware contract with both IBM and
EMC.  Our IT management is not sure that our data would be secured and
deleted correctly.  

Here is an excerpt from our security group.

>From my perspective, what we have from IBM/EMC so far isn't sufficient.
My opinion is that in order for us to consider a vendor's approach
suitable- there needs to be more focus on data breach law compliance
support.  For example, if we can confirm that their approach (or related
optional enhancements) is audited, secured, traceable,
employee/subcontractor vetting/background checking, and includes
appropriate notification of potential data breach, etc and that their
program is also periodically third party audited (& ideally court case
tested).. we're in a much better position. If/when they notify us of
loss, we also would need full cooperation in related investigation
efforts and confirming ultimate disposition.

Your company's process would be appreciated. Thoughts??  Tnx's a bunch
for your input. 
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are
not
the intended recipient, please do not read, distribute or take action in

reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.


Re: Disposition of Failed Storage Devices

2007-01-26 Thread Schaub, Steve
Or the US Marine Corp.
"When it absolutely, positively has to be destroyed overnight" 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thorneycroft, Doug
Sent: Friday, January 26, 2007 12:34 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Disposition of Failed Storage Devices

You might take a look at this site,
their members specialize in totally
destroying things like tapes and disk drives.
(National Associating for information destruction)
http://www.naidonline.org/



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kauffman, Tom
Sent: Friday, January 26, 2007 8:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Disposition of Failed Storage Devices


Given the security group's position, I think your options are
sledghammer or iron smelter. And you'll really need to put everything
you've got into the sledgehammer, if you go that route. A thermal lance
or oxygen cutting torch might also fill the requirements.

I doubt you'll get anything in writing from either IBM or EMC that will
be satisfactory. You'll also need to get quotes from both on how much
the maintenance fees will increase if the failed media device is
rendered non-salvageable before return.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lamb, Charles P.
Sent: Friday, January 26, 2007 11:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Disposition of Failed Storage Devices

Hi

Our IT management is looking at implementing a process for disposition
of failed storage devices. We have a hardware contract with both IBM and
EMC.  Our IT management is not sure that our data would be secured and
deleted correctly.  

Here is an excerpt from our security group.

>From my perspective, what we have from IBM/EMC so far isn't sufficient.
My opinion is that in order for us to consider a vendor's approach
suitable- there needs to be more focus on data breach law compliance
support.  For example, if we can confirm that their approach (or related
optional enhancements) is audited, secured, traceable,
employee/subcontractor vetting/background checking, and includes
appropriate notification of potential data breach, etc and that their
program is also periodically third party audited (& ideally court case
tested).. we're in a much better position. If/when they notify us of
loss, we also would need full cooperation in related investigation
efforts and confirming ultimate disposition.

Your company's process would be appreciated. Thoughts??  Tnx's a bunch
for your input. 
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are
not
the intended recipient, please do not read, distribute or take action in

reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm


Re: Disposition of Failed Storage Devices

2007-01-26 Thread Thorneycroft, Doug
You might take a look at this site,
their members specialize in totally 
destroying things like tapes and disk drives.
(National Associating for information destruction)
http://www.naidonline.org/



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kauffman, Tom
Sent: Friday, January 26, 2007 8:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Disposition of Failed Storage Devices


Given the security group's position, I think your options are
sledghammer or iron smelter. And you'll really need to put everything
you've got into the sledgehammer, if you go that route. A thermal lance
or oxygen cutting torch might also fill the requirements.

I doubt you'll get anything in writing from either IBM or EMC that will
be satisfactory. You'll also need to get quotes from both on how much
the maintenance fees will increase if the failed media device is
rendered non-salvageable before return.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lamb, Charles P.
Sent: Friday, January 26, 2007 11:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Disposition of Failed Storage Devices

Hi

Our IT management is looking at implementing a process for disposition
of failed storage devices. We have a hardware contract with both IBM and
EMC.  Our IT management is not sure that our data would be secured and
deleted correctly.  

Here is an excerpt from our security group.

>From my perspective, what we have from IBM/EMC so far isn't sufficient.
My opinion is that in order for us to consider a vendor's approach
suitable- there needs to be more focus on data breach law compliance
support.  For example, if we can confirm that their approach (or related
optional enhancements) is audited, secured, traceable,
employee/subcontractor vetting/background checking, and includes
appropriate notification of potential data breach, etc and that their
program is also periodically third party audited (& ideally court case
tested).. we're in a much better position. If/when they notify us of
loss, we also would need full cooperation in related investigation
efforts and confirming ultimate disposition.

Your company's process would be appreciated. Thoughts??  Tnx's a bunch
for your input. 
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.


TSM 5.4 client appears

2007-01-26 Thread Bob Booth
The 5.4 TSM client is now on the IBM ftp site.  It does appear to have the
long awaited 'native' support for Intel based Macs.  Hope it works.

cheers,

bob


Re: exporting scripts

2007-01-26 Thread Gill, Geoffrey L.
>why not just create a profile on the Server with the scripts in it and
then
>create a subscription on the TSM-server you want the script on? This
way
>you can keep scripts neatly aligned with almost no administrative or
manual
>overhead, as changes are replicated automatically. Works well at our
sites,
>cross-platform an all the stuff you could stumble over with the macros!

Hi Markus,
I had thought about this some time back but my attempts to set it up
were unsuccessful. Probably me not ever seeing it implemented. I'm sure
support would help me out but if you have the commands and an order to
run them I'd certainly give it another go.

Also an FYI on the scripts macro implementation. If you have scripts
already assigned with the same name the macro quits and fails to copy
anything in. I was able to rename the scripts in the macro file and
successfully import them all.

 
Geoff Gill 
TSM Administrator 
PeopleSoft Sr. Systems Administrator 
SAIC M/S-G1b 
(858)826-4062 
Email: [EMAIL PROTECTED] 


Re: Disposition of Failed Storage Devices

2007-01-26 Thread Kauffman, Tom
Given the security group's position, I think your options are
sledghammer or iron smelter. And you'll really need to put everything
you've got into the sledgehammer, if you go that route. A thermal lance
or oxygen cutting torch might also fill the requirements.

I doubt you'll get anything in writing from either IBM or EMC that will
be satisfactory. You'll also need to get quotes from both on how much
the maintenance fees will increase if the failed media device is
rendered non-salvageable before return.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lamb, Charles P.
Sent: Friday, January 26, 2007 11:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Disposition of Failed Storage Devices

Hi

Our IT management is looking at implementing a process for disposition
of failed storage devices. We have a hardware contract with both IBM and
EMC.  Our IT management is not sure that our data would be secured and
deleted correctly.  

Here is an excerpt from our security group.

>From my perspective, what we have from IBM/EMC so far isn't sufficient.
My opinion is that in order for us to consider a vendor's approach
suitable- there needs to be more focus on data breach law compliance
support.  For example, if we can confirm that their approach (or related
optional enhancements) is audited, secured, traceable,
employee/subcontractor vetting/background checking, and includes
appropriate notification of potential data breach, etc and that their
program is also periodically third party audited (& ideally court case
tested).. we're in a much better position. If/when they notify us of
loss, we also would need full cooperation in related investigation
efforts and confirming ultimate disposition.

Your company's process would be appreciated. Thoughts??  Tnx's a bunch
for your input. 
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.



Expired directories with DIRMC and restore

2007-01-26 Thread L'Huillier, Denis (GTI)
I ran a test backing up a directory structure with files and
subdirectories to a reto=20 management class for the files and
directories via DIRMC to a reto=0 management class.  After the backup I
deleted the data and re-ran the incremental backup to expire the objects
from TSM.  I confirmed the objects were now INACTIVE_VERSION in the
backups table then ran expiration to purge from the DB (reto=0).
Checking the backups table again I can see no directory objects existed,
just the files.

Next, I launched the GUI to test if I could expand the directory tree
and restore the data.  Both worked.  Path preserved on the restore as
well.

So my confusion is, what is the directory structure for?  I would have
suspected I would not have been able to expand the tree in the GUI or
restore the data to its original location.

We are looking to mix long term data with short term data in our TSM
servers and want to prevent all directory objects from being bound to
the longest retention policy mgmtclass using the DIRMC option.  This
test was to see the implications of not having a directory structure,
which surprisingly had no affect...  Am I missing something?

Thanks.


If you are not an intended recipient of this e-mail, please notify the sender, 
delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail. http://www.ml.com/email_terms/



Re: Disposition of Failed Storage Devices

2007-01-26 Thread Prather, Wanda
You can buy a big degausser. 
Looks like a large-size microwave.
Zap the disks before returning them.

I think your hardware contract costs more because of that, but it's
probably cheaper than a lawsuit!



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lamb, Charles P.
Sent: Friday, January 26, 2007 11:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Disposition of Failed Storage Devices

Hi

Our IT management is looking at implementing a process for disposition
of failed storage devices. We have a hardware contract with both IBM and
EMC.  Our IT management is not sure that our data would be secured and
deleted correctly.  

Here is an excerpt from our security group.

>From my perspective, what we have from IBM/EMC so far isn't sufficient.
My opinion is that in order for us to consider a vendor's approach
suitable- there needs to be more focus on data breach law compliance
support.  For example, if we can confirm that their approach (or related
optional enhancements) is audited, secured, traceable,
employee/subcontractor vetting/background checking, and includes
appropriate notification of potential data breach, etc and that their
program is also periodically third party audited (& ideally court case
tested).. we're in a much better position. If/when they notify us of
loss, we also would need full cooperation in related investigation
efforts and confirming ultimate disposition.

Your company's process would be appreciated. Thoughts??  Tnx's a bunch
for your input. 


Disposition of Failed Storage Devices

2007-01-26 Thread Lamb, Charles P.
Hi

Our IT management is looking at implementing a process for disposition
of failed storage devices. We have a hardware contract with both IBM and
EMC.  Our IT management is not sure that our data would be secured and
deleted correctly.  

Here is an excerpt from our security group.

>From my perspective, what we have from IBM/EMC so far isn't sufficient.
My opinion is that in order for us to consider a vendor's approach
suitable- there needs to be more focus on data breach law compliance
support.  For example, if we can confirm that their approach (or related
optional enhancements) is audited, secured, traceable,
employee/subcontractor vetting/background checking, and includes
appropriate notification of potential data breach, etc and that their
program is also periodically third party audited (& ideally court case
tested).. we're in a much better position. If/when they notify us of
loss, we also would need full cooperation in related investigation
efforts and confirming ultimate disposition.

Your company's process would be appreciated. Thoughts??  Tnx's a bunch
for your input. 


SV: INCLUDE.DIR in SUN 5.10

2007-01-26 Thread Christian Svensson
Hi Remco,
INCLUDE.DIR works fine in Linux, Mac and Windows.

/C

-Ursprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Remco Post
Skickat: den 26 januari 2007 15:35
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: INCLUDE.DIR in SUN 5.10

Christian Svensson wrote:
> Hi Everyone,
> 
> Has anyone realize that INCLUDE.DIR doesn't exist in TSM BA Client
> version 5.3.4.4 for SUN Solaris 5.10?
> 

It doesn't exist on any other platform either, it never has.

> We have setup a generic INCLEXCL list for all UNIX boxes and everyone
> can use it accept the SUN Servers where they can't use the lines
> INCLUDE.DIR. The EXCLUDE.DIR works fine but not the INCLUDE.DIR.
> 
> 
> 
> Any comments anyone?
> 

use include and exclude.dir only for those dirs that don't have anything
in them that wil get backed-up.

> 
> 
> 
> 
> Best Regards/ Med vänlig hälsning Christian Svensson Product
> Specialist
> 
> Cristie Nordic AB Cell : +46-70-325 1577 Office: +46-8-718 4330 
> Support : +44-1453-84 7009 E-Mail : [EMAIL PROTECTED]
> 
> 


-- 
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten  http://www.sara.nl
High Performance Computing  Tel. +31 20 592 3000Fax. +31 20 668 3167
PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16  B3F6 048A 02BF DC93 94EC

"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: INCLUDE.DIR in SUN 5.10

2007-01-26 Thread Remco Post
Christian Svensson wrote:
> Hi Everyone,
> 
> Has anyone realize that INCLUDE.DIR doesn't exist in TSM BA Client
> version 5.3.4.4 for SUN Solaris 5.10?
> 

It doesn't exist on any other platform either, it never has.

> We have setup a generic INCLEXCL list for all UNIX boxes and everyone
> can use it accept the SUN Servers where they can't use the lines
> INCLUDE.DIR. The EXCLUDE.DIR works fine but not the INCLUDE.DIR.
> 
> 
> 
> Any comments anyone?
> 

use include and exclude.dir only for those dirs that don't have anything
in them that wil get backed-up.

> 
> 
> 
> 
> Best Regards/ Med vänlig hälsning Christian Svensson Product
> Specialist
> 
> Cristie Nordic AB Cell : +46-70-325 1577 Office: +46-8-718 4330 
> Support : +44-1453-84 7009 E-Mail : [EMAIL PROTECTED]
> 
> 


-- 
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten  http://www.sara.nl
High Performance Computing  Tel. +31 20 592 3000Fax. +31 20 668 3167
PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16  B3F6 048A 02BF DC93 94EC

"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


INCLUDE.DIR in SUN 5.10

2007-01-26 Thread Christian Svensson
Hi Everyone,

Has anyone realize that INCLUDE.DIR doesn't exist in TSM BA Client version 
5.3.4.4 for SUN Solaris 5.10?

We have setup a generic INCLEXCL list for all UNIX boxes and everyone can use 
it accept the SUN Servers where they can't use the lines INCLUDE.DIR. The 
EXCLUDE.DIR works fine but not the INCLUDE.DIR.

 

Any comments anyone?

 

 

Best Regards/ Med vänlig hälsning
Christian Svensson
Product Specialist  

 Cristie Nordic AB
 Cell : +46-70-325 1577
 Office: +46-8-718 4330
 Support : +44-1453-84 7009
 E-Mail : [EMAIL PROTECTED]

 


Re: exporting scripts

2007-01-26 Thread David E Ehresman
I've never done any config manager stuff.  is this as simple as:

tsm1> set configman on
tsm1>def profile scriptprof desc='tsm scripts'
tsm1>def profassoc scriptprof scripts=*
..
tsm2>def subscript scriptprof server=tsm1

This would require all changes and additions to scripts to be made on server 
tsm1, right?

David

>>> Markus Engelhard <[EMAIL PROTECTED]> 1/26/2007 2:30 AM >>>
Hi Geoffrey,

why not just create a profile on the Server with the scripts in it and then
create a subscription on the TSM-server you want the script on? This way
you can keep scripts neatly aligned with almost no administrative or manual
overhead, as changes are replicated automatically. Works well at our sites,
cross-platform an all the stuff you could stumble over with the macros!

Regards,
Markus


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
__

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

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.


Question

2007-01-26 Thread Darcy Roberto Ganga Ponce
Hi List


I have de little problem, i use tsm client 5.2.3.0 and tsm storage agent
5.2.3.0, the tsm server is identical version.

The AIX Client (5.3 with Veritas FS, Veritas Cluster and volume shared) the
slow transfer rate 7MB/s the backup or archive.

If use volume no shared the transfer rate is entry 32MB/s and 42MB/s

How solve the slow transfer rate to 42MB/s using volume shared???



Darcy Roberto Ganga Ponce
Ingeniero de Sistemas
IBM Certified Deployment Professional
Tivoli Storage Manager
Cientec Computación
Presidente Riesco 5711 Piso 7
http://www.cientec.com
email:[EMAIL PROTECTED]


tsm-database Volumes on zfs

2007-01-26 Thread Rainer Wolf

Dear TSMers,
we have tsm server 5.3.4.0 on solaris10 and already using zfs
for all backup-diskPools and filepools on disk.
We currently use the tsm-db-volumes ( define dbvol ) on UFS .

Because we just got a new raid for the tsm-db we now want to use
the new one with 'zfs' and move the tsmdb-volumes onto that.

The question now is: are there any special things/settings
to think about when using 'zfs' for the tsmdb-volumes instead of 'ufs' ?
... any caveats ?

best regards
 and thanks in advance !
Rainer



--

Rainer Wolf  eMail:   [EMAIL PROTECTED]
kiz - Abt. Infrastruktur   Tel/Fax:  ++49 731 50-22482/22471
Universitaet Ulm wwweb:http://kiz.uni-ulm.de


Re: TSM and disk volumes of more than 1 TB...

2007-01-26 Thread PAC Brion Arnaud
Hi Iban,

>From http://people.bu.edu/rbs/ADSM.QuickFacts :

Volume, maximum sizePer 2004/05/27 IBM TechNote 1170255
("Maximum capacity of an ITSM disk
volume"), the maximum size of an ITSM
disk volume is 8 Terabytes (TB). 


Arnaud 

**
Panalpina Management Ltd., Basle, Switzerland, 
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]
**

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ibán 
Bernaldo de Quirós y Márquez
Sent: Friday, 26 January, 2007 17:52
To: ADSM-L@VM.MARIST.EDU
Subject: TSM and disk volumes of more than 1 TB...

Hi everyone,

Did anyone know if TSM could hold disk volumes of 1TB or more for a disk 
STGPOOL ¿?

Thanks in advance,
Ibán Bernaldo de Quirós
Technical Specialist


TSM and disk volumes of more than 1 TB...

2007-01-26 Thread Ibán Bernaldo de Quirós y Márquez

Hi everyone,

Did anyone know if TSM could hold disk volumes of 1TB or more for a disk 
STGPOOL ¿?


Thanks in advance,
Ibán Bernaldo de Quirós
Technical Specialist


TSM and TS3200 tape library

2007-01-26 Thread richard kupca
Hello TSM consultants,
my conf: TSM server 5.3.4 on Windows 2003 (HP server), TS3200 library with 1 
LTO3 drive, SCSI.
I installed IBM device drivers for the tape library and drives. IBM drivers 
were installed succesfully and I can see now  in device manager two medium 
changers and two tape devices. Does it mean I must configure pathes to both 
libraries (medium changers) in TSM? I think there is only one medium changer in 
TS3200 but windows see two. Why? I've tried to configure only one library and 
both drives. Pathes were set correcly. Checkin command was succesfull but when 
I try to backup I get an error message "ANR0535W - insufficient mount points 
available to satisfy the request. " It seems that TSM can't manipulate with the 
changer.