Re: Seeking wisdom on dedupe..filepool file size client compression and reclaims

2009-08-31 Thread Mark Scott
Good Morning
We have been in the planning stages of moving our
production backup server to our non prod site and setting up cross site
vaulting.

The more I think about it, the more it makes sense to build a new server
and point the clients to the server running TSM6.*.

Our prod server is currently running 5.5.1 and the clients are also
updated to this level across AIX, Linux, Windows and TDP for RMAN.

Can someone point me to the documentation for supported clients etc as
in the short term I was hoping to build the server as rev6 and leave the
clients for the short term?

Any gotchas running TSM6* on AIX would be appreciated. 

Look forward to your response

Warm Regards 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Allen S. Rout
Sent: Monday, 31 August 2009 9:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Seeking wisdom on dedupe..filepool file size
client compression and reclaims

>> On Sun, 30 Aug 2009 08:34:47 +0200, Stefan Folkerts
 said:


> Interesting ideas and a simulator would be fun for this purpose.
> You could be right and your example does make sense in a way but
> still..  I do wonder if it works out in the real world.

> Let's say you have normal data that expires (user files etc) and
> large databases, some you keep for many months and sometimes even
> years.

I understand the case you're making, and I agree that the size of your
files has an impact.  I'm suggesting that the impact isn't huge, and
that it evens out in a reasonably short timeframe.

Eventually, whatever the volume size, you wind up with a library full
of volumes more or less randomly distributed between 0% and 50%
reclaimable.  If you're keeping up with reclamation, that means you're
_in_ a steady state, so you're _doing_ the same amount of work per
unit time.


So when I say "To a first approximation, it's irrelevant", focus on
the "First appoximation" bit; Yes, there are variations here, but
don't sweat them too much.

It's certainly possible to back yourself into corners with very large
or very small volumes.



- Allen S. Rout


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: TDP for Oracle - multi channel restore

2009-01-14 Thread Mark Scott
Afternoon all

   Does anyone know when TSM 6 is to be released?

Regards 


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Fast Back

2008-12-15 Thread Mark Scott
Howdy

Looking at trialling Fast Back can anyone point me to the
appropriate documentation?

 

Look froward to your response

 

Regards 

 

 

 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Fastback has me stumped

2008-12-09 Thread Mark Scott
Howdy
I believe your last questioned answered your question.

By memory this product is for SQL and Exchange?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Stapleton
Sent: Tuesday, 9 December 2008 2:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Fastback has me stumped

AD can be integrated, but is not necessary.

Try using IP addresses only for configurations on the server and client.
It should be a slamdunk for installation.
 
--
Mark Stapleton ([EMAIL PROTECTED])
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Nicholas Rodolfich
> Sent: Monday, December 08, 2008 10:47 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Fastback has me stumped
> 
> Hello All,
> 
> 
> Thanks for your help!!
> 
> I am trying to install the new Fastback product to familiarize myself
> with
> it before I have to implement it at a client site. After several
> install/reinstall I found out the default login by accident and now I
> can
> get into the product but not much further.
> 
> I am using a blade that boots from a SAN and the disk I will be using
> for a
> repository is also a SAN LUN.
> 
> I have the Fastback manager, Control Station, Mount and the
> Administrative
> client installed on a lab machine that will act as the Fastback
server.
> This lab has no AD. I have installed the client code on a workstation
> for a
> test client and the only entry in the Fastback Client Configurator is
> basically the IP of the Fastback server.  When I go back to the server
> I
> cannot see the Fastback client I just installed. According to the doc
I
> should see it under the Storage Pool branch of the tree. Additionally
> when
> I try to do a manual snapshot there is no field for the client to be
> snapshotted only a group field.
> 
> I have heard that this product is easy to configure but I am not
seeing
> it
> yet. Is the product designed to work with AD only.  Is there no notion
> of a
> client system on the server? What am I missing?
> 
> Nicholas


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Library Manager and Migration question

2008-10-15 Thread Mark Scott
Morning can you point me to the library manager Redbook please?

Regards 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, 16 October 2008 3:41 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Library Manager and Migration question

Thanks, hadn't thought about the restartable restores, good idea.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Howard Coles
Sent: Wednesday, October 15, 2008 1:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Library Manager and Migration question


Sounds like you signed with the wrong group, you know more than they do.
I've been in this same boat with TSM and other apps.  Drives you up the
wall.  We had one vendor put in a TSM system at a former workplace.  He
told us we only had to run reclamation on the onsite pools and the
offsite stuff would just "take care of itself".  

Anyway, All you really need, from my understanding, is to setup a new
TSM server LPAR and make it the Library manager, and make the current
TSM instance another Library client.  Then setup your other TSM
instances as you desire, and perform node exports.  I would upgrade to
TSM 5.5.1 first, so that you can do restartable exports and imports,
etc.  From my perspective and what I've seen in this no data loss should
be expected, and you can do a good dB backup ahead of time to give you a
go back to spot.  But in all honesty a TSM consultant should not be
overwhelmed by any environment (noticeably that is).

See Ya'
Howard


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Haberstroh, Debbie (IT)
> Sent: Wednesday, October 15, 2008 12:52 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Library Manager and Migration question
> 
> Hi All,
> 
> We currently have 1 TSM server ver 5.3.3 on AIX 5.3, with a large
> database, 228GB.  We have finally received approval to move this to a
> new server, upgrade to 5.5 and split the clients up to reduce the DB
> size.  We would like to have 4 LPAR's created on the new server, 1 for
> a Library manager and the other 3 for client databases. Our library is
> a TS3584 with 12 LTO2 drives.  We are adding another expansion cabinet
> and adding 4 LTO3 drives but are staying with LTO2 tapes for now.  Our
> current library configuration has the library shared but it is not a
> library manager since we only had one server.
> 
> Due to the size and complexity of our environment, we contracted with
a
> vendor to do the setup and start the process.  Now that the contract
> has been signed and we have started our planning sessions, the vendor
> is having a problem with the library manager/client configuration.  At
> first he said that there was no such thing.  I sent him documentation
> and they also found an IBM redbook on the subject but now says that it
> is too complicated since our server is so large and that I will need
to
> partition the library, with some data loss!!  I am strongly against
> this setup and would like to know if I am wrong.  How difficult would
> it be to create a library manager and client setup for an existing
> environment?  I currently have over 1000 tapes onsite and as many
> offsite and naturally do not want to lose any data.  Thanks for the
> feedback.
> 
> Debbie Haberstroh
> Server Administration


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: TSM 5.5 (CLIENT/SERVER)

2008-09-10 Thread Mark Scott
Go to 5.5.1 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Killam, 
Perpetua
Sent: Wednesday, 10 September 2008 8:57 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM 5.5 (CLIENT/SERVER)

We will be upgrading our server and clients to tsm server version. Has
anyone experienced any issues with it or should watch out for?  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: 2008, September, 10 8:53 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP MS SQL X32 / X64

Boris,

Officially, Data Protection for SQL only supports the x64 version while
running on an x64 operating system and the x32 version while running on
an x64 operating system.

I am still trying to understand why you would want to run SQL Server
32-bit on a 64-bit OS.

Thanks,

Del



>
> "ADSM: Dist Stor Manager" 
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Hello all,
>
> we've got a Windows 2003 64 Bit System with a MS SQL Database (32
Bit).
> We've installed TSM BA Client 5.5.1 (64 Bit).
>
> But which version of TDP must we use (32 Bit or 64 Bit?)
>
> With kind regards,
> Boris
___

This e-mail may be privileged and/or confidential, and the sender does not 
waive any related rights and obligations.
Any distribution, use or copying of this e-mail or the information it contains 
by other than an intended recipient is unauthorized.
If you received this e-mail in error, please advise me (by return e-mail or 
otherwise) immediately.  

Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce 
pas aux droits et obligations qui s'y rapportent.
Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il 
contient par une personne autre que le (les) destinataire(s) désigné(s) est 
interdite.
Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser 
immédiatement, par retour de courrier électronique ou par un autre moyen.


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: TSM library master for two tape libraries causes problems

2008-09-10 Thread Mark Scott
Afternoon
We had similar issues sometime ago now, when we had non IBM
carts in our library and the picker drive was an LTO1 path.

We have since removed all non IBM carts especially EMTEC and moved the
picker drive to a LTO2 drive.

Touch would it has been stable.

Regards 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Wednesday, 10 September 2008 2:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM library master for two tape libraries causes
problems

Robert,
Thanks for your note.  The tape drive wasn't the library control
path.  Since we have two control paths, and the ALT path turned on in
the AIX driver, I would hope that wouldn't be a problem anyway.
But our Atape drivers are about a year old.  It would not hurt
to update them.  
Also, or IBM3584 firmware level is 7360, and 7363 is available.
I know that isn't very far from current, but one of the patches in 7363
sound similar to what is happening to us.  So I think we are due to
update them both. 


Best Regards,

John D. Schneider 
Phone: 314-364-3150 
Cell: 314-750-8721
Email:  [EMAIL PROTECTED] 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Clark, Robert A
Sent: Friday, September 05, 2008 7:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM library master for two tape libraries causes
problems

Was the single tape drive that had an error your library control path?

Is Atape up to date?

What OS is the TSM server running?

Are there any errors in the errpt / error log / syslog, etc?

[RC]
 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Friday, September 05, 2008 9:14 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM library master for two tape libraries causes
problems

Greetings,
We have a TSM instance that serves as the library master for two
tape libraries.  One is a IBM3584 tape library with 24 LTO4 drives.  The
second is a virtual tape library, an EMC EDL configured as a IBM3584
with 128 LTO1 tape drives.  The library master has 9 other TSM instances
and 4 Lan-free clients that are library clients, and appeal to it for
tape mounts.  Most of the time this works just fine. 
All the TSM instances are running TSM 5.4.3.0.  A few weeks ago we
upgraded them from 5.4.2.0 in order to pick up a patch to provide the
LIBSHRTIMEOUT parameter.  This may not have anything to do with our
problem, but it IS a recent change.  
The problem comes when we have any problem with the real IBM3584
tape library.  Two weeks ago a tape got stuck in the gripper.  Last week
the gripper itself actually broke, so no tapes could get mounted.  Last
night it was a single tape drive that got an error and went Polling.
For some reason, in each one of these cases, after an hour or two all
tape mounts start hanging, even those belonging to the virtual tape
library.  When we would do a 'q mount'  they all showed up in Reserved
status.  So before long all backups going to the virtual tape library
ground to a halt.
 
Can any of you see a reason why the TSM library master should get
into such a problem?  Shouldn't all tape mounts be asynchronous?  It
seems like to me a single tape drive getting into problems should not
keep all other mounts from proceeding.  And it doesn't happen instantly.
It seems to happen gradually.  
I probably should also mention that this is a fairly busy
environment during the night.  It isn't unusual for us to have over 100
virtual tape mounts simultaneously.  That is the reason we needed the
LIBSHRTIMEOUT parameter (mentioned above).  Before we had that, we
sometimes would get timeouts that caused tape mount failures, because
the TSM library master's queue of tape mounts polls would get overrun.
Since we put on that patch, and added 'LIBSHRTIMEOUT 60' to the options
file, that problem has gone away.  But now this problem seems to have
taken it's place.

Best Regards,

John D. Schneider
Lead Systems Administrator - Storage
Sisters of Mercy Health Systems
3637 South Geyer Road
St. Louis, MO  63127
Phone: 314-364-3150
Cell: 314-750-8721
Email:  [EMAIL PROTECTED]

 
This e-mail contains information which (a) may be PROPRIETARY IN NATURE
OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only
for the use of the addressee(s) named above. If you are not the
addressee, or the person responsible for delivering this to the
addressee(s), you are notified that reading, copying or distributing
this e-mail is prohibited. If you have received this e-mail in error,
please contact the sender immediately.


DISCLAIMER:
This message is intended for the sole use of the addressee, and may
contain information that is privileged, confidential and exempt from
disclosure under applicable law. If you are not the addressee you are
hereby notified that you may not use, copy, disclose, or distribute to
anyone

Cross Site Vaulting

2008-09-05 Thread Mark Scott
Good Morning

   

   I am looking for direction on which way to go. We are
in the process of setting up cross site vaulting and not 100% sure on
how to incorporate both nodes and libraries to share the libraries.

 

I assume the most efficient way would be to have a library manager
instance that controls both libraries from our remote site? If we were
to loose the library manager we would then configure the libraries to
each LPAR to manage their own libraries? Also consider library
partitioning.

 

Our implementation has a restricted budget where as we are attempting to
set this up with existing infrastructure besides a couple of new 595
LPARS. 

 

An overview of what we have is x2 3584's one with an expansion and the
other as standalone. A CWDM link with a 8gb trunked link over 15klm's
and two 595 LPARS 1 cpu and 8gb mem. Two HBA's for disk and four HBA's
for tape drives.  Prod data will go across the wire to our non prod site
which will have our prod backup server and vice versa.

 

We are limited to 4 drive slots in the smaller frame library and have 4
LTO3 drives and 9 LTO2 drives in total to manage the data.

 

We are planning on using two LTO3 and two LTO2 drives in the smaller
library which will hold prod primary storage pool data and the rest in
the non prod library. As the restriction of the size of the prod library
we are only planning on copying prod data across sites and copying non
prod data within the non prod library. Currently hold approximately
200TB's backed up data across two servers.

 

The current two instances are 5.5.1 and all associated clients.

 

Can someone point me to a doco or have a similar experience? I have been
trawling through redbooks and google is my friend.

 

Look forward to any responses

 

Regards 

 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Time to reclaim LTO tapes

2008-04-23 Thread Mark Scott
We have reclamation set up to 70 using our LTO3 drives which only hold
Oracle data and usually consists of largeish files. They usually reclaim
faster due to higher transfer rates etc then LTO2 and LTO. It is one of
those how long is a piece of string questions depends on the variables
including the server. 

We also run LTO4 on another site. As the price of LTO4 comes down I
would consider LTO4's over LTO3. 

One to two occasionally three hours reclamation is complete. 

I don't think LTO5 is that far away either


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thorneycroft, Doug
Sent: Thursday, 24 April 2008 5:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Time to reclaim LTO tapes

We may be going to LTO 3 or 4 in the near future.
How long does it take to reclaim a LTO3 tape at 50% full,
and how long for a LTO4?


Doug Thorneycroft
Senior Systems Analyst
Computer Technology Section
County Sanitation Districts of Los Angeles County
1955 Workman Mill Road
Whittier, CA 90601
(562) 699-7411 Ext. 1058
Fax. (562)695-6756
[EMAIL PROTECTED]


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Tape Drive Block Size

2008-03-04 Thread Mark Scott
Morning
  The following will give you an indication if nothing else.
Also look at your fabric switch for indications on what you are pushing
through your fabric.  Note you have to let the process move a few files
before you can see any stats.

select process_num as "Number",process,-
current_timestamp-start_time as "Elapsed Time", -
cast(((BYTES_PROCESSED/1024)/1024) as decimal(18,2)) as "Total MB
Processed", -
FILES_PROCESSED as "Total Files Processed", -
cast((cast(files_processed as
decimal(18,0))/cast((current_timestamp-start_time)-
seconds as decimal(18,0))) as decimal(18,2)) as "Files/second",-
cast((cast(((bytes_processed/1024)/1024) as
decimal(18,0))/cast((current_timestamp-start_time)-
seconds as decimal(18,0)))as decimal(18,2))as "MB/second",STATUS as
"Status" -
from processes

Regards 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Tuesday, 4 March 2008 11:48 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Tape Drive Block Size

TSM manages tape block size itself, through the device driver.  Avoid
interfering with that.

Richard Sims


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Archiving

2008-03-04 Thread Mark Scott
Evening

 

I am about to import archive data into a server that does not have the
same management classes defined meaning the data will go to the default
archive management class.  I'm happy with this as it will provide the 5
year retention that I need and the archive date seems to have been
retained on the archived files but does anyone know if it will it still
expire after the right time?

 

Using the example of a 5 year retention period:  Will a file that is 4
years old on the source server expire after 1 year on the importing
server or will the importing server reset the expiry data and retain the
archive for 5 years after importing?

 

Look forward to your response

 

Regards 

Mark Scott

Enterprise Storage & Monitoring Team Leader

Bunnings Group Limited 

126 Pilbara Street, Welshpool WA 6106

Locked Bag 20, Welshpool DC WA 6985

Phone : (08) 9365 1779

Fax :(08) 9358 6053

Mobile : 0408925402

E-mail : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



L500

2008-02-03 Thread Mark Scott
Afternoon

  We are currently attempting to implement a new STK L500
library. 

 

Has LTO4 IBM drives installed, which the drivers have been successfully
installed. 

 

Windows 2003 TSM 5.4.2

 

04-02-2008 16:06:10   ANR8843E Initialization failed for SCSI library
STK_SL500 
   - the library will be inaccessible.

04-02-2008 16:06:10   ANR8441E Initialization failed for SCSI library
STK_SL500.
 
04-02-2008 16:24:55   ANR2017I Administrator JMENIL issued command:
DEFINE PATH 
   VICPRODTSM1 STK_SL500 SRCTYPE=SERVER
DESTTYPE=LIBRARY
   DEVICE=lb1.0.0.4 ONLINE=YES AUTODETECT=NO
(SESSION: 13) 
04-02-2008 16:24:55   ANR8310E An I/O error occurred while accessing
library
   STK_SL500. (SESSION: 13)

04-02-2008 16:24:55   ANR8418E DEFINE PATH: An I/O error occurred while

   accessing library STK_SL500. (SESSION: 13)

04-02-2008 16:26:51   ANR0407I Session 24 started for administrator
JMENIL  
   (WebBrowser) (HTTP 172.30.3.2(4092)). (SESSION:
24)  
04-02-2008 16:26:51   ANR2017I Administrator JMENIL issued command:
DEFINE PATH 
   VICPRODTSM1 STK_SL500 SRCTYPE=SERVER
DESTTYPE=LIBRARY
   DEVICE=lb1.0.0.4 ONLINE=YES AUTODETECT=NO
(SESSION: 24) 
04-02-2008 16:26:51   ANR8310E An I/O error occurred while accessing
library
   STK_SL500. (SESSION: 24)

04-02-2008 16:26:51   ANR8418E DEFINE PATH: An I/O error occurred while

   accessing library STK_SL500. (SESSION: 24)

 
 
We believe it is a driver issue. Can anyone point us in the direction of
a TSM driver for the L500?
 
Any thoughts would be appreciated.
 
Regards 

 Mark Scott

Enterprise Storage & Monitoring Team Leader

Bunnings Group Limited 

126 Pilbara Street, Welshpool WA 6106

Locked Bag 20, Welshpool DC WA 6985

Phone : (08) 9365 1779

Fax :(08) 9358 6053

Mobile : 0408925402

E-mail : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: TSM performance very poor, Recovery log is being pinned

2007-07-31 Thread Mark Scott
Evening I have been watching these comments with interest as we are
currently in the process of building a new TSM server. 
Discussing with colleagues we are baffled by how you create the TSM log
or DB on a raw presented Lun without creating at least a JFS for a mount
point first. We are running AIX 5.3. 

Look forward to your response

Regards 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Craig Ross
Sent: Tuesday, 31 July 2007 7:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performance very poor, Recovery log is being
pinned

Thanks guys.

All this advise is much appreciated.
For the record my TSM servers seems to have returned to more normal
routines.
However the log is still being pinned and log fills up to about 12% then
flushes, not ideal but acceptable.
I am starting to wonder if my install has always had the log pinning
issue I
just did not know!!
I will keep close eye on it.   But I feel ultimately I will install 2nd
TSM
server and migrate some Node's to new server.
I did find a bad configured batch of new SAN storage which is promoting
the
slowdown/pinning. I have stopped using this particular disk and
performance
has returned to norm.  However this was not obvious before because
server
was busy, I could not pin point easy as once stopping the trouble spot
TSM
was not jumping into life straight away it had too process the back log
of
requests And of course I could not afford to leave server on go slow for
long periods.

As result I am currently in review of all new Storage installed to
ensure
its running optimally.

I will propose to management to install new fast disk for log and DB as
the
pinning still issue.

However this is where the debate continues, I have experimented with DB
volumes log volumes and storage volumes with FS and raw volumes and have
not
seen any performance difference (on the same disks) ie have deleted
volumes
created RAW and FS and seen no difference.
I have read material on both sides of this story and no seems more
convincing than the other except I remember reading somewhere the only
eyebrow raiser was with RAW on solaris you can have issues, I cannot
remember exact issue but potential is there. So after testing both
formats
finding no difference. I use FS for everything, if this is an
indisputable
mistake please let me know.
Also we have 10 10 Gb volumes for DB should I create more smaller ones?

While I am here though I have another cloudy area, since upgrading
server
from 5.1 to 5.3 installing IBM tape device driver and adding 4 LTO3
drives I
swear my 6 old LTO 1 drives are running slower than previous is there
some
gotchas when installing IBM Tape to get drives running well!

6 LTO 1 drives are SCSI attached and 4 new LTO 3 are fibre.

Cheers

A happier TSM administrator the last 2 days  :>




On 7/31/07, Roger Deschner <[EMAIL PROTECTED]> wrote:
>
> .
> I think you are right about the Log - it need not be spread across
> multiple volumes. It's only got one writer.
>
> Your RAID type can affect the performance of the Disk Storage Pools
and
> the Database dramatically. In particular, RAID5 is very poorly suited
> for this, because it is 50% writes. RAID5 is also not ideal for the
> Database, though it can be tolerated for the Log. RAID10 is much
better.
>
> You should be using fast disks, not SATA, for the primary Disk Storage
> Pools. I've got 10,000rpm IBM SSA disks for these.
>
> I use RAID10 for the Disk Storage Pools. I use JBOD disks with TSM
> mirroring for the Log and Database. This is slightly slower than OS
> mirroring or RAID-array mirroring, but it is somewhat safer. Each
> physical volume for Storage Pools and Database is broken into many
> Logical Volumes.
>
> You should be saving your fastest disks for the Database. I've got
> 15,000prm disks for the Database. When I moved the Database from
> 10,000rpm disks to 15,000rpm disks, everything in TSM got noticeably
> faster. For instance, DB backups now take 1/3 less time. RAID boxes
just
> get in the way for the Database; it really runs best on JBOD disks
with
> TSM doing the mirroring.
>
> Here's a controversial paper written by a guy at Oracle. He says you
> should "Stripe And Mirror Everything" (S.A.M.E.) I've read and reread
> this several times, and while I definitely do not agree with
everything
> said, it does raise some very interesting points that definitely apply
> to TSM. For one thing he strongly advocates RAID10, as do I.
>
http://www.oracle.com/technology/deploy/availability/pdf/oow2000_same.pd
f
>
> Most of my Log pinning problems have been caused by clients. If a
client
> suffers a networking problem (typically a half-duplex vs. full-duplex
> conflict) and if that client tries to back up a large file such as a
> movie, that can pin the log on our system until it fills completely.
> Minimum throughput controls in TSM can help here, though it can still
> happen. I wrote a daemon that watches the Log fullness and if it gets
to
> ab

Re: TSM Server DB Backups

2007-07-18 Thread Mark Scott
I believe the best practise is

Backup
Migration
Backup primary to copy
Backup db
Expiration
Reclamation
Start all over again

:)

Cheers 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Wednesday, 18 July 2007 9:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Server DB Backups

We actually backup ours after nightly backups complete and before
migration. Is there a
specific recommended order or is it up to each individual site and it's
environment?

Helder Garcia wrote:

> You should backup db after migration and before expiration.
>
> On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote:
>
>>
>> Hello all,
>>
>> How many times a day should I be backing up the TSM DB and should it
be
>> after migration?
>>
>>
>> Thanks
>>
>> Greg
>>
>>
>> ***
>> Gregory Lynch
>> Lead Programmer Analyst
>> IT Infrastructure/Systems Administration
>> Stony Brook University Medical Center
>> HSC Level 3, Room 121  ZIP 8037
>> Phone: 631-444-9783
>> [EMAIL PROTECTED]
>>
>> This e- mail message, including any attachments,
>> is for the sole use of the intended recipient(s) and may
>> contain confidential and privileged information.
>> Any unauthorized review, use, disclosure or distribution is
prohibited.
>> If you are not the intended recipient, please contact the sender
>> by e-mail and destroy all copies of the original.
>>
>
>
>
> --
> Helder Garcia


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



TDP Exchange

2007-06-27 Thread Mark Scott
Evening 

Currently looking at upgrading one of our TSM servers! There
are even requests to replace it with another vendors software as there
has not been a lot of satisfaction from the current infrastructure.

 

We are running TSM 5.2 Level 6.0.

 

We are looking at upgrading the Server to 5.4 and 5.3.4 clients. 

The server predominately backs up windows clients and a handful of Linux
and Aix clients. 

 

Data consists of a group drive and a exchange server..

 

The exchange data is currently dumped into a directory locally on the
exchange server using NT backup, then TSM backs this up. Why it is done
like this I believe dates back to cost restraints.

 

The biggest issue I am aware of why the admins want to dump the software
is to restore ACL's and individual mail boxes.

 

So I believe the answer would be TDP for MS Exchange? 

 

Is anyone currently successfully achieving what I am looking at?

 

Look forward to your responses

 

Regards Mark 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



5.4 default pwd

2007-04-16 Thread Mark Scott
Afternoon all

   Currently attempting to install TSM 5.4 AIX Server,
ran smitty, bounced node now attempting to log into server using admin
admin the user account works though the pwd does not. Has the default
pwd changed for 5.4?

 

 

Regards Mark 

 

 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Windows vs. AIX Server

2007-03-14 Thread Mark Scott
I believe it depends on the size of your environment. For example what I
have seen instances with roughly up to 20GB DB runs fine on Windows.
 After that AIX or the dinosaur.  

My thoughts 

Regards 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gregory Lynch
Sent: Thursday, 15 March 2007 5:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Windows vs. AIX Server

Hello all,

I just wanted to get some opinions on which people prefer, having a TSM
Server on a Windows server or AIX. Currently our TSM environment is on
AIX
and I just wanted to know if it is worth while to migrate to a Windows
platform. Thanks

Greg


***
Gregory Lynch
Lead Programmer Analyst
IT Infrastructure/Systems Administration
Stony Brook University Medical Center
HSC Level 3, Room 121  ZIP 8037
Phone: 631-444-9783
[EMAIL PROTECTED]

This e- mail message, including any attachments,
is for the sole use of the intended recipient(s) and may
contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender
by e-mail and destroy all copies of the original.


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



TSM and Linux

2007-02-26 Thread Mark Scott
Morning all

Does anyone have any experiences good or bad running
Linux as a TSM Server? We are a reasonable size environment currently
running AIX as our server and Linux/Windows and Aix clients. 

The question has been asked for various reasons to change
processors and flavour.

 

All feed back would be appreciated.

 

Regards Mark 

 

Mark Scott

Enterprise Storage & Tivoli Team Leader

Bunnings Group Limited 

126 Pilbara Street, Welshpool WA 6106

Locked Bag 20, Welshpool DC WA 6985

Phone : (08) 9365 1779

Fax :(08) 9350 6686

Mobile : 0408925402

E-mail : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

 



Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Tape drive zones for FC drives - best practices

2007-02-07 Thread Mark Scott
I agree with the best practice though it generally depends on your budget
infrastructure. Eg 20 HBA's in a P595 Series would pretty much be a draw. If
you want to be pedantic you should have separate HBA's for host as well if
running LAN free.
My experience to date if you have separate HBA's for your disk
generally two for dual paths. And for example 5 separate HBA's for tape
drives you will still get the desired throughput etc. The only time I have
seen multiple failures because of one device is with the 3584 as the picker
is controlled through the first drive.
My two cents worth, good luck.

Cheers

I also agree with soft zoning best for masking simplicity etc
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian
Smith
Sent: Wednesday, 7 February 2007 7:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Tape drive zones for FC drives - best practices

I second what John wrote. We have never experienced a device taking out all
devices in a zone - because we went with the best practice of one adapter
<->
one target per zone from the beginning.
For clarity and sanity sake, use aliases for each device host side and
target
side and a naming convention like: 'host-fcs2'  or 'switch2-rmt12' for the
aliases, create the zones using the alias names and roll up everything into
a
'config' that you enable (load into flash memory on the switch).
Thus 6 months down the line when an adapter or  device fails and is replaced
and you are scratching your head at the schema you drew for yourself on a
scrap of A4 ...
you just login to the switch(es) and do:
 admin> alishow# list your device aliases
 admin> aliadd # add new WWN
 admin> aliremove# remove the old WWN
 admin> cfgshow  # show the new alias in the defined config
 admin> cfgsave  # save the config to internal flash
 admin> cfgenable# enable the changed config
 admin> cfgactvshow  # sanity check

HTH
Ian Smith
Oxford University Computing Services
England.


On Wednesday 07 Feb 2007 1:57 am, John Monahan wrote:
> It is best practice to put one initiator and one target in each zone.  It
> may seem cumbersome but its really not that bad.  You'll be happy you did
> it if you ever have SAN problems down the road.  I have seen one device
> take out all other devices within the same zone before, more than once.
> Just pick a good naming convention for your zones so you can tell exactly
> what is in each zone just from the name.  I also prefer to use aliases so
> when you replace a HBA or tape drive you just update the alias with the
> new PWWN instead of going in and changing 20 different zones.
>
>
> ***Please note new address, phone number, and email below***
> __
> John Monahan
> Consultant
> Logicalis
> 5500 Wayzata Blvd Suite 315
> Golden Valley, MN 55416
> Office: 763-417-0552
> Cell: 952-221-6938
> Fax:  952-833-0931
> [EMAIL PROTECTED]
> http://www.us.logicalis.com
>
>
>
>
> "Schneider, John" <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" 
> 02/06/2007 05:05 PM
> Please respond to
> "ADSM: Dist Stor Manager" 
>
>
> To
> ADSM-L@VM.MARIST.EDU
> cc
>
> Subject
> Tape drive zones for FC drives - best practices
>
>
>
>
>
>
> Greetings,
> My habit in regards to zoning FC tape drives has always been to
> put
> one host HBA in a zone with all the tape drives it should see, and to have
> a
> separate zone for each host HBA.  For example, in a situation with 2 host
> HBAs and 10 tape drives, I would have two zones, one with one host HBA and
> 5
> tape drives, and the other with the other host HBA and 5 tape drives.
> Pretty simple.
>
> But an IBM consultant working here is telling me that the best
> practice is to have a separate zone for each HBA/tape drive pair.  So in
> my
> example above, I would have 20 zones instead of two.   His claim is that
> an
> individual tape drive can hang all the other drives if they are in the
> same
> zone, but not if they are in separate ones.  Has anyone seen this in real
> life?
>
> This becomes important to me because I am about to put in new SAN
> switches, and he wants me to follow this recommendation.  I have 2 TSM
> servers with 4 HBAs each, 4 NDMP nodes, and 14 tape drives.  Using my
> scheme, I would have 12 zones, with his scheme I would have 56 zones. That
> seems like a lot of zones, and unnecessarily cumbersome.
>
> Is it really necessary to isolate each HBA/Tape drive into a
> separate zone?  Do individual tape drives really hang other drives in
> their
> zone?
>
> Best Regards,
>
> John D. Schneider
> Sr. System Administrator - Storage
> Sisters of Mercy Health System
> 3637 South Geyer Road
> St. Louis, MO.  63127
> Email:  [EMAIL PROTECTED]
> Office: 314-364-3150, Cell:  314-486-2359


Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
informatio

Re: TSM inventory of empty slots becomes inconsistent wi th IBM3584 li brary.

2006-11-25 Thread Mark Scott
Hi
What is the library you are using? 3583? Look at drivers.

Show slots  will give you a good idea where your tapes are.
This cmd has to be run when there are no sessions mounts proc etc for it to
work. Remove any tapes except for the tapes the vendor recommend eg IBM use
IBM. I have had a PMR open on one of our libraries for months which has
slowly got better though every now and then it will give the exact same
problem, with slots. Easiest way to get around it is to power cycle remove
paths and the add, add the carts and it runs ok again. Add the scratch
first. Obviously we have scripted all this. The library in question is a
3583 scsi library which we are looking at replacing anyway.  Or maybe you
just have to run a audit.

Regards Mark

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Sunday, 26 November 2006 12:17 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM inventory of empty slots becomes inconsistent wi
th IBM3584 li brary.

Richard,
Thanks for your reply.
I had already read the Technotes you referred to. I try to hit the
knowledgebase before I go to the list; of course, I am certainly capable of
overlooking something.
The element numbers being misassigned would cause mounts to be done
incorrectly; where TSM tells the library to mount a tape in drive element
257, expecting that to match up to /dev/rmt3, but instead /dev/rmt3 is
really drive element 258.  If that were my mistake, I would be getting
ANR8300E errors during a mount, but instead it is always a dismount, where
TSM finds the slot full trying to put the tape back where it got it from.
And as I mentioned, I can sometimes go for days, with 50-100 mounts for each
tape drive, before the problem suddenly appears.  So a basic configuration
mistake like would show up right away, not after days.
The ANR8469E can certainly be a stuck tape, or other hardware
problems caused by a drive, but if you look at the ANR8300E that comes just
before it, it tells us that the destination slot is full during the
dismount. So I think the ANR8469E is in response to that.
I should clarify that, although I am doing library sharing, there is
only one library master.  All mounts and dismounts are done by him; the
others just make the request.  So the errors I am seeing all appear in the
library master's activity log.

Best Regards,

John D. Schneider
Sr. System Administrator - Storage
Sisters of Mercy Health System
3637 South Geyer Road
St. Louis, MO.  63127
Email:  [EMAIL PROTECTED]
Office: 314-364-3150, Cell:  314-486-2359


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Saturday, November 25, 2006 7:28 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM inventory of empty slots becomes inconsistent with
IBM3584 li brary.


John -

The joy of inherited environments, where you have no solid information on
how things were configured by your predecessors...

In my experience, an ANR8469E unload failure is always due to a tape drive
hardware problem (possibly a sensor or motor problem).  Check your records
or logs to gauge whether one or two drives are troublemakers and need work.
A tape stuck in a drive tends to stay in the drive, where it subsequently
being put away in a strange place
*might* be due to human actions.  Sometimes, a seeming unload failure can be
a timing problem in the drive microcode, where not enough time is being
allowed for the operation.

See IBM Technotes (1143428, 1212674) on the possible causes of ANR8356E.  An
insidious problem is where the barcode is inconsistent with the magnetic
labeling of the volume.  Element number inconsistencies are another gem.

Beyond that, I would activate TapeAlert and review AIX Error Log entries.
You also say that you are doing library sharing, so I would review the logs
of both sharers and see if both are experiencing the same kind of problems,
which may illuminate configuration or software issues.

   what I can think of,  Richard Sims

Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: How to start Reclamation

2006-09-28 Thread Mark Scott
For example

UPDATE STGPOOL TAPE RECLAIM=60

h upd stgpool

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Norita binti Hassan
Sent: Friday, 29 September 2006 11:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to start Reclamation

Hi,

How to start the reclamation process? Can anyone explain to me pl...

NORITA BINTI HASAN
Senior Programmer
Enterprise Systems Services
Information Communications Tech. Div
6th Floor,Pos Malaysia HQ
50670 Kuala Lumpur

* :  03 - 22756638
*:  016 - 6090530




Pos Malaysia Berhad is Malaysia's national postal company
Visit us online at www.pos.com.my

NOTICE
This message may contain privileged and/or confidential
information. If  you are  not the addressee  or authorised
to  receive this email, you must not use, copy,  disclose
or take any  action based  on this email. If you  have
received this  email in  error, please advise  the sender
immediately by  reply e-mail and delete  this message.
Pos Malaysia  Berhad takes  no responsibility  for  the
contents of this email.


Email scanned and protected by POS Malaysia

Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



TSM Data Refresh

2006-05-31 Thread Mark Scott
Afternoon all



We are currently contemplating the best way forward in a
data refresh test at a remote site onto a node that is running the same
version of AIX 5.3.* and TSM 5.2.6



Our three scenarios we are contemplating are a backup set, image backup and
group backup.

The pros and cons of both the backup set can be created from the backup
server and image from the client.



As the site on which we would like to perform the refresh does not have a
concurrent TSM server so we would have to do a db restore so the image or
the backup set could be read. There also only a stand alone a single drive
to restore the data from.



Any thoughts would be greatly appreciated.



Regards Mark






Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Configuring tape drives in TSM - Document Available

2006-03-28 Thread Mark Scott
So would I - Cheers


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Prather, Wanda
Sent: Wednesday, 29 March 2006 3:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Configuring tape drives in TSM - Document Available

Would love to have a copy - thanks!

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Miles Purdy
Sent: Thursday, March 23, 2006 12:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Configuring tape drives in TSM - Document Available


Serval years ago a wrote a document on configuring tape drives in TSM
for performance/redundancy. We had some problems today and I had to dig
out the document. I looked through it and made a couple of minor
updates. It still seems pretty relevant. I have not made updates to the
sections on SCSI drives, but they are still included. The document
includes a detailed example for AIX using fibre drives in an IBM 3584.

Please email me directly if you would like the document.

Miles






Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.



Re: Lock and unlock TSM client manually

2006-03-22 Thread Mark Scott
Or why not just run reclamation during quite periods and update to stop an
hour before your busy periods.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
nghiatd
Sent: Thursday, 16 March 2006 5:55 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Lock and unlock TSM client manually

Thanks you for your help,

Nghiatd,

- Original Message -
From: "Bill Dourado" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, March 16, 2006 4:33 PM
Subject: Re: Lock and unlock TSM client manually


> Hi,
>
> You could use a single commandDISABLE SESSIONS   to prevent
> client node access o the server.
>
> Then ENABLE SESSIONSwhen reclamation is finished.
>
> Bill
>
>
>
>
>
>
>
>
> nghiatd <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" 
> 16/03/2006 09:32
> Please respond to "ADSM: Dist Stor Manager"
>
> To: ADSM-L@VM.MARIST.EDU
> cc:
> Subject:[ADSM-L] Lock and unlock TSM client manually
>
>
> Hi all,
>
> I want to lock all TSM client when I implement reclamation tape. I have to
> lock and unlock TSM client manually, it is so inconvenience because there
> are 30 TSM client.
> Does anyone know the way or script to lock (and unlock) TSM client
> automatically?
>
> Thanks you so much
>
>
>
> *** Disclaimer ***
> This email and any files transmitted with it contains privileged and
> confidential information and is intended for the addressee only. If you
> are not the intended recipient you must not disseminate, distribute or
> copy this email. Please notify the sender at once that you have received
> it by mistake and then delete it from your system.
>
> Any views expressed in this email are those of the sender and not
> necessarily those of ALSTEC or its associated companies.
>
> Whereas ALSTEC takes reasonable precautions to ensure this email is virus
> free, no responsibility will be accepted by it for any loss or damage
> whether direct or indirect which results from the contents of this email
> or its attachments.
>
> ALSTEC Group Limited - Registered in England No.3939840 - www.alstec.com
> Registered office: Cambridge Road, Whetstone, Leicester. LE8 6LH. England.
> Telephone: +44 (0)116 275 0750
>

Bunnings Legal Disclaimer:

1) This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.