AW: SQL TDP lan free backup on VMWARE

[Stefan Holzwarth]

We backup 3 different Exchange Servers (DL380 G5) one after one - all with 
identical results over 1 GB ethernet nic - see example:
TSM Server is also windows x86 using only disks.

01/18/2009 18:05:06 
=
01/18/2009 18:05:06 Request   : Backup
01/18/2009 18:05:06 SG List   : *  
01/18/2009 18:05:06 Backup Type   : FULL  
01/18/2009 18:05:06 Database Name :   
01/18/2009 18:05:06 Buffers   : 3  
01/18/2009 18:05:06 Buffersize: 1024  
01/18/2009 18:05:06 Exchange Server   : VEX01003  
01/18/2009 18:05:06 TSM Node Name :   
01/18/2009 18:05:06 TSM Options File  : 
c:\adsm32\TDPExchange\dsm_VEX01003EXCH.opt  
01/18/2009 18:05:06 Mount Wait: Yes  
01/18/2009 18:05:06 Quiet : No  
01/18/2009 18:05:06 
-
01/18/2009 19:19:37 Total storage groups requested for backup:  2
01/18/2009 19:19:37 Total storage groups backed up: 2
01/18/2009 19:19:37 Total storage groups expired:   52
01/18/2009 19:19:37 Total storage groups excluded:  0
01/18/2009 19:19:37 Throughput rate:52,493.79 Kb/Sec
01/18/2009 19:19:37 Total bytes transferred:240,195,943,048
01/18/2009 19:19:37 Elapsed processing time:4,468.46 Secs
01/18/2009 19:19:37 --- SCHEDULEREC OBJECT END EXCHBACKUP 01/18/2009 19:19:37


Optfile used:
NODename  VEX01003EXCH
CLUSTERnode   YES
COMMMethodTCPip
TCPPort   1502
TCPServeraddress  SDE14001-GB4
TCPWindowsize 256
TCPBuffSize   512
COMPRESSION   OFF
RESOURCEUTILIZATION   3
...

Regards,
Stefan Holzwarth

> -Ursprüngliche Nachricht-
> Von: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] Im 
> Auftrag von Schaub, Steve
> Gesendet: Dienstag, 27. Januar 2009 18:02
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: SQL TDP lan free backup on VMWARE
> 
> Howard,
> 
> Can you share the Exchange server physical config 
> (cpu/mem/disk) as well
> as the .cfg you use for these Exchange servers?  Are they x86 
> Ex2003 or
> x64?  Did it run this well out of the box or did you need to 
> tweak it to
> reach this point?  We have several Ex2003 servers, one of which has a
> total of 909gb in 4 SG's and is taking 16.5hrs to do a full 
> backup (.857
> gb/min).  it is gig attached, and the tsm server is using a multi-gig
> trunked line.  I just cant seem to squeeze any more speed out of this
> backup and I would love to find out how you are doing it.
> 
> Thanks,
> 
> Steve Schaub
> Systems Engineer, Windows
> BlueCross BlueShield of Tennessee
> steve_sch...@bcbst.com
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] 
> On Behalf Of
> Howard Coles
> Sent: Monday, January 26, 2009 5:13 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] SQL TDP lan free backup on VMWARE
> 
> We have 4 Storage Groups per Node, and 3 nodes.  However, 1 node is
> about 600 GB, the other two add up to about 600 GB.  They all 
> backup at
> the same time of the night, when they do a full backup on 
> each box.  We
> have other Exchange nodes that backup at various times but these three
> (being the largest) I have backing up at a time when they can 
> have more
> bandwidth.  We back them up via the LAN (1 GB NICS each) directly to
> disk.  They all take about 4 (sometimes 5) hours each to backup unless
> the LAN is congested which means the total backup time for 
> the 1.2 TB is
> around 4 to 4.5 hours, which is about 4.5 - 5 GB per Min.  Which means
> we're pushing the TSM Server's NIC to about the edge. :-D
> 
> The TSM server has 1, 1GB NIC (Teamed in Failover mode).  Note: The 1
> Largest node only takes 4 hours to do a full backup.  We used to have
> them in a direct to SAN backup, but discovered that doesn't work much
> faster than doing the LAN backup, and has the added burden of 
> tying up 1
> or more Tape drives per node, which could be doing other things.  Now,
> if I had a 1.2 TB single system, this would be a no brainer for Direct
> over SAN backup. But until it gets bigger than 8-9 hundred GB 
> it really
> does work out to be equal either way.  
> 
> See Ya'
> Howard
> 
> 
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] 
> On Behalf
> > Of Len Boyle
> > Sent: Monday, January 26, 2009 3:11 PM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: [ADSM-L] SQL TDP lan free backup on VMWARE
> > 
> > Howard,
> > 
> > Can you give the list a little more details on the Exchange system
> > backup of 1.2 TB in about 4 or so hours.
> > 
> > How many exchange storage groups do you have and how many of them
> > backup up in parallel?
> > How large are they?
> > Are you using multi

Hardware upgrade question(s)

[goc]

hi all, i'm sure you can help me ...
we are getting ready for hardware upgrade of our old TSM servers , old servers
are IBM p640 and new ones are p520 or something like that i really don't know
because management simply forgets to forward this information :-) ... anyhow
i know there was a lot of discussion here on list about migration of TSM to new
hardware and i was always missing a part ... the procedure should go
something like
this i believe (please correct me and add stuff)

- install new servers
- cable connections to switches
- install TSM server software
- define TSM db and logs
- define drives (can i define drives if they are already defined to
old TSM server?)
- ?
- ?
- when and how should i import the database ?
- can i have 2 TSM server running parallel using same drives in tape
library (3584 with LTO3) ?

sheesh. so many questions !

thanks in advance ... and i'll check the list for additional answers

//
goran

Re: Hardware upgrade question(s)

[KIRAN-SYSTEMS]

Please find my suggestions in RED Color



Regards,

Kiran M.





-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of goc
Sent: Wednesday, January 28, 2009 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Hardware upgrade question(s)



hi all, i'm sure you can help me ...

we are getting ready for hardware upgrade of our old TSM servers , old
servers

are IBM p640 and new ones are p520 or something like that i really don't
know

because management simply forgets to forward this information :-) ... anyhow

i know there was a lot of discussion here on list about migration of TSM to
new

hardware and i was always missing a part ... the procedure should go

something like

this i believe (please correct me and add stuff)



- install new servers

- cable connections to switches

Install IBM  device drivers for the Library

- install TSM server software

- define TSM db and logs

- define drives (can i define drives if they are already defined to

old TSM server?)



Enable Library Sharing by defining shared library for the new TSM server.

- ?

- ?

- when and how should i import the database ?



Restore Database by taking the Old server Latest DB tape

- can i have 2 TSM server running parallel using same drives in tape

library (3584 with LTO3) ?



You can use Library Sharing Among two TSM instances



http://www-01.ibm.com/support/docview.wss?rs=1019

&context=SSSQWC&dc=DB520&dc=DB560&uid=swg21145017&loc=en_US&cs=UTF-8&lang=en
&rss=ct1019tivoli



I think the above link helps you



sheesh. so many questions !



thanks in advance ... and i'll check the list for additional answers



//

goran

Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail address

Re: Hardware upgrade question(s)

[Bos, Karel]

Only black and white found in text. :P


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
KIRAN-SYSTEMS
Sent: woensdag 28 januari 2009 10:26
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Hardware upgrade question(s)

Please find my suggestions in RED Color



Regards,

Kiran M.





-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
goc
Sent: Wednesday, January 28, 2009 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Hardware upgrade question(s)



hi all, i'm sure you can help me ...

we are getting ready for hardware upgrade of our old TSM servers , old
servers

are IBM p640 and new ones are p520 or something like that i really don't
know

because management simply forgets to forward this information :-) ...
anyhow

i know there was a lot of discussion here on list about migration of TSM
to new

hardware and i was always missing a part ... the procedure should go

something like

this i believe (please correct me and add stuff)



- install new servers

- cable connections to switches

Install IBM  device drivers for the Library

- install TSM server software

- define TSM db and logs

- define drives (can i define drives if they are already defined to

old TSM server?)



Enable Library Sharing by defining shared library for the new TSM
server.

- ?

- ?

- when and how should i import the database ?



Restore Database by taking the Old server Latest DB tape

- can i have 2 TSM server running parallel using same drives in tape

library (3584 with LTO3) ?



You can use Library Sharing Among two TSM instances



http://www-01.ibm.com/support/docview.wss?rs=1019

&context=SSSQWC&dc=DB520&dc=DB560&uid=swg21145017&loc=en_US&cs=UTF-8&lan
g=en
&rss=ct1019tivoli



I think the above link helps you



sheesh. so many questions !



thanks in advance ... and i'll check the list for additional answers



//

goran

Disclaimer:
This email message (including attachments if any) may contain
privileged, proprietary, confidential information, which may be exempt
from any kind of disclosure whatsoever and is intended solely for the
use of addressee (s). If you are not the intended recipient, kindly
inform us by return e-mail and also kindly disregard the contents of the
e-mail, delete the original message and destroy any copies thereof
immediately. You are notified that any dissemination, distribution or
copying of this communication is strictly prohibited unless approved by
the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is
not liable for any damage you may sustain as a result of any virus in
this e-mail. DQE shall not be liable for the views expressed in the
e-mail. DQE reserves the right to monitor and review the content of all
messages sent to or from this e-mail address

ÿþ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

Re: Hardware upgrade question(s)

[KIRAN-SYSTEMS]

Sorry, check the black one





Kiran M

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Bos, Karel
Sent: Wednesday, January 28, 2009 2:59 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Hardware upgrade question(s)

Only black and white found in text. :P


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
KIRAN-SYSTEMS
Sent: woensdag 28 januari 2009 10:26
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Hardware upgrade question(s)

Please find my suggestions in RED Color



Regards,

Kiran M.





-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of goc
Sent: Wednesday, January 28, 2009 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Hardware upgrade question(s)



hi all, i'm sure you can help me ...

we are getting ready for hardware upgrade of our old TSM servers , old
servers

are IBM p640 and new ones are p520 or something like that i really don't
know

because management simply forgets to forward this information :-) ...
anyhow

i know there was a lot of discussion here on list about migration of TSM to
new

hardware and i was always missing a part ... the procedure should go

something like

this i believe (please correct me and add stuff)



- install new servers

- cable connections to switches

Install IBM  device drivers for the Library

- install TSM server software

- define TSM db and logs

- define drives (can i define drives if they are already defined to

old TSM server?)



Enable Library Sharing by defining shared library for the new TSM server.

- ?

- ?

- when and how should i import the database ?



Restore Database by taking the Old server Latest DB tape

- can i have 2 TSM server running parallel using same drives in tape

library (3584 with LTO3) ?



You can use Library Sharing Among two TSM instances



http://www-01.ibm.com/support/docview.wss?rs=1019

&context=SSSQWC&dc=DB520&dc=DB560&uid=swg21145017&loc=en_US&cs=UTF-8&lan
g=en
&rss=ct1019tivoli



I think the above link helps you



sheesh. so many questions !



thanks in advance ... and i'll check the list for additional answers



//

goran

Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of addressee (s).
If you are not the intended recipient, kindly inform us by return e-mail and
also kindly disregard the contents of the e-mail, delete the original
message and destroy any copies thereof immediately. You are notified that
any dissemination, distribution or copying of this communication is strictly
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the
risk of transmission of computer viruses with this e-mail; DQE is not liable
for any damage you may sustain as a result of any virus in this e-mail. DQE
shall not be liable for the views expressed in the e-mail. DQE reserves the
right to monitor and review the content of all messages sent to or from this
e-mail address



Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail address

Re: Hardware upgrade question(s)

[Richard Sims]

There's various info available in IBM doc, such as their Technote
1114874.

   Richard Sims

Re: Hardware upgrade question(s)

[goc]

yes, thank you ... really straightforward technote,

i'm really more interested specific migration with db and logs on SAN storage,
libraries stay the same , drives stay the same ... and like that,
and of course minimal downtime :-)

as i understand, having db and logs on SAN storage simplifies the thing
in a way that i don't need to restore db , am i right ?

thanks again



On Wed, Jan 28, 2009 at 1:54 PM, Richard Sims  wrote:
> There's various info available in IBM doc, such as their Technote
> 1114874.
>
>   Richard Sims
>



--

Marilyn Monroe  - "It's not true that I had nothing on. I had the radio on."

Re: Hardware upgrade question(s)

[Richard Rhodes]

Do you currently have SAN storage on the old server?
Do you boot from the SAN storage, or is your rootvg on local/internal
drives?
Are you keeping that SAN storage, or replacing it also?
If you currently use SAN storage, is your entire TSM db/log and any other
filesystems on the SAN storage?

For example, we use internal disks for our boot volume (rootvg), so TSM is
installed and lives on the internal drives.  Our TSM server db/log and
other related filesystems are all on external SAN storage.

Depending on your answers, your migration to the new server could be very
easy . . . just a storage swing.

Rick








 goc
   To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
  Re: Hardware upgrade question(s)


 01/28/2009 09:14
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






yes, thank you ... really straightforward technote,

i'm really more interested specific migration with db and logs on SAN
storage,
libraries stay the same , drives stay the same ... and like that,
and of course minimal downtime :-)

as i understand, having db and logs on SAN storage simplifies the thing
in a way that i don't need to restore db , am i right ?

thanks again



On Wed, Jan 28, 2009 at 1:54 PM, Richard Sims  wrote:
> There's various info available in IBM doc, such as their Technote
> 1114874.
>
>   Richard Sims
>



--

Marilyn Monroe  - "It's not true that I had nothing on. I had the radio
on."



-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.

Re: TSM admin processes

[Schneider, John]

For those of you with Servergraph, there is a standard report on missed
filespaces.  If you sort it by days since last backup, it often shows
you filespaces that missed even though the rest of the machine backed
up.  Those tend to be filespaces that have been removed from a system or
renamed.  We have cleaned up TB of wasted TSM space that way. 


Best Regards,

John D. Schneider 
Phone: 314-364-3150 
Cell: 314-750-8721
Email:  john.schnei...@mercy.net 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Wanda Prather
Sent: Tuesday, January 27, 2009 4:40 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM admin processes

I you are concerned about storage space, then every now and then you
should
look at the "last backup" date/time on all your file spaces, find any
old
ones that can be discarded.


On Mon, Jan 26, 2009 at 10:35 PM, Paul Dudley 
wrote:

> I would like to make sure that I have all the relevant TSM admin
> processes running as I am concerned about running out of space on the
> tapes in the tape library.
>
> Currently we have the following admin processes running on a daily
> basis:
>
>
>
> Delete volhist
>
> Expire inventory
>
> Reclaimation
>
> Migration
>
>
>
> Is there anything we are missing?
>
>
>
> If there are thousands of files backed up via TSM which will stay on
the
> backup tapes in the library for a number of years probably without
being
> required for a restore, is there a way of moving these files to tapes
> which can then be checked out of the library, thereby freeing up slots
> in the library for more scratch tapes?
>
>
>
>
>
> Thanks & Regards
>
> Paul
>
>
>
> Paul Dudley
>
> Senior IT Systems Administrator
>
> ANL Container Line Pty Limited
>
> Email: pdud...@anl.com.au
>
>
>
>
>
>
>
>
>
>
>
>
> ANL DISCLAIMER
>
> This e-mail and any file attached is confidential, and intended solely
to
> the named addressees. Any unauthorised dissemination or use is
strictly
> prohibited. If you received this e-mail in error, please immediately
notify
> the sender by return e-mail from your system. Please do not copy, use
or
> make reference to it for any purpose, or disclose its contents to any
> person.
>
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.

Re: Hardware upgrade question(s)

[goc]

> Do you currently have SAN storage on the old server?

me : yes (xp12000)

> Do you boot from the SAN storage, or is your rootvg on local/internal
> drives?

me : no (hdisk0/hdisk1)

> Are you keeping that SAN storage, or replacing it also?

me : keeping

> If you currently use SAN storage, is your entire TSM db/log and any other
> filesystems on the SAN storage?

me : yes

> For example, we use internal disks for our boot volume (rootvg), so TSM is
> installed and lives on the internal drives.  Our TSM server db/log and
> other related filesystems are all on external SAN storage.
>
> Depending on your answers, your migration to the new server could be very
> easy . . . just a storage swing.
>
> Rick
>

me : thank you, can you help me some more ? :-)

Data Rention Settings: Unintended Consequences

[Nick Laflamme]

A client's TSM server has the following copygroup settings:

tsm: SERVER1>q copygroup * active f=d

 Policy Domain Name: OPEN_SYSTEM_ENVIRONMENT
Policy Set Name: ACTIVE
Mgmt Class Name: BACKUP_SHARK
Copy Group Name: STANDARD
Copy Group Type: Backup
   Versions Data Exists: 3
  Versions Data Deleted: 3
  Retain Extra Versions: No Limit
Retain Only Version: 91


Because "Versions Data Deleted" is more than 1, and because "Retain
Extra Versions" is set to "No Limit," am I correct in deducing that
TSM will keep three copies of deleted files forever, because "Retain
Only Version" will never become relevant?

Or does TSM use "Retain Only Version" for all versions (copies) once
there isn't an active file? (That's not what the doc says, of course.)

Thanks,
Nick

Re: Data Retention Settings: Unintended Consequences

[Kelly Lipp]

Boy, it sure looks like you'll have three versions forever on this one.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick 
Laflamme
Sent: Wednesday, January 28, 2009 12:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Data Rention Settings: Unintended Consequences

A client's TSM server has the following copygroup settings:

tsm: SERVER1>q copygroup * active f=d

 Policy Domain Name: OPEN_SYSTEM_ENVIRONMENT
Policy Set Name: ACTIVE
Mgmt Class Name: BACKUP_SHARK
Copy Group Name: STANDARD
Copy Group Type: Backup
   Versions Data Exists: 3
  Versions Data Deleted: 3
  Retain Extra Versions: No Limit
Retain Only Version: 91


Because "Versions Data Deleted" is more than 1, and because "Retain
Extra Versions" is set to "No Limit," am I correct in deducing that
TSM will keep three copies of deleted files forever, because "Retain
Only Version" will never become relevant?

Or does TSM use "Retain Only Version" for all versions (copies) once
there isn't an active file? (That's not what the doc says, of course.)

Thanks,
Nick

Best practices Managing a Full Library?

[David E Mussulman]

It was inevitable - I've got more tapes and data than I can keep 'hot'
in my current library.  Paul's question about "TSM admin processes"
seems like a nice lead-in to this conversation:

Any best practices for using overflow/MountableNotInLib conditions?
I've read the 'Managing a Full Library" page in the Admin guide, but it
seems like there are lots of dependencies that make 'move media'
commands need some thought.  I'm not as worried about restores, as those
are manual and observed anyway.  I'm more concerned about the basic,
automatic storage pool operations and what overflow means to my overall
maintenance, and its impacts (for example, reclaims not running as well
or using more tapes).

Here's my core dump of thoughts and questions; maybe we can get a good
discussion here.  If I missed a redbook or white paper, please point it
out.

The days=X flag on the "q media" and "move media" seems handy.  I can
say "only move tapes that haven't been written to in 28 days" or
something.  That means I should make sure I've done a 'backup stg' of
those tapes in the last 28 days so that they aren't needed for the
'backup stg' command.

Because I'm tight on library space, I keep my reclaimation values pretty
high on the stgpool I'm migrating.  What happens when a
MountableNotInLib volume is eligible for reclaimation?  Does anything
tell me, or do I need to be monitoring the logs for failed reclaims or
the volumes for ones that should be reclaimable but aren't.  I'm
guessing I need a cleanup process somewhere that finds MountableNotinLib
volumes below the threshhold and reminds me to move them back to the
library.

What about reclaimations of copypool volumes that source
MountableNotInLib volumes?  I'm guessing my copypool tapes reclaims will
fail (so I need to watch for that?) or I need to watch for those tapes
sticking below their reclaim threshhold as well?  Is this going to be a
common problem, or is the nature of copies of cold data also stay pretty
cold going to keep the copypool reclaims close to the stgpool reclaim
frequencies?  (As I hinted, I've been tight on library slots for a
while, so these stgpools are colloc=no, which probably works against me
here.)

'move drm' and 'move media' are independent from each other.  Got it.
Too bad -- a VaultRetrieve state for 'move media' would be nice, based
on how its needed.  Or is this the type of thing that ServerGraph helps
identify/manage/visualize?

I'm also thinking about active pools, although because it's "yet another
copy" scenario, that might cause even more library slot contention.

Thoughts?

Dave

--
David Mussulman mussu...@uiuc.edu
SysAdmin, NetAdmin for the Technology Services Group2330 Siebel Center
Department of Computer Science  office: 217.333.6231
 -- See https://agora.cs.uiuc.edu for CS Intranet and TSG support info --

Re: Best practices Managing a Full Library?

[Thomas Denier]

-David E Mussulman wrote: -

>Because I'm tight on library space, I keep my reclaimation values
>pretty high on the stgpool I'm migrating.

A high reclamation threshold means you will leave a volume
unreclaimed even though a large part of its capacity is being
used for expired files. If you are short on tape slots I would
think you would want reclamation thresholds as low as tape
drive throughput will allow in order to increase the average
amount of unexpired data per volume.

why am I getting this drive failure

[Erwin Zavala]

  LIBVOL i500  (SESSION: 3)
01/28/2009 18:20:57  ANR8840E Unable to open device lb0.1.0.2 with error 2.
  (SESSION: 3, PROCESS: 5)
01/28/2009 18:20:57  ANR8441E Initialization failed for SCSI library I500.
  (SESSION: 3, PROCESS: 5)
01/28/2009 18:20:57  ANR8460E AUDIT LIBRARY process for library I500 failed.
  (SESSION: 3, PROCESS: 5)
01/28/2009 18:20:57  ANR0985I Process 5 for AUDIT LIBRARY running in the
  BACKGROUND completed with completion state FAILURE at
  18:20:57. (SESSION: 3, PROCESS: 5)
01/28/2009 18:21:13  ANR2017I Administrator EZAVALA3 issued command: QUERY

Re: why am I getting this drive failure

[Richard Sims]

Why not?  ;-)

Realize that you're asking us, when we have no context for the
failure condition or operating environment.
What operating system is it?  If it's Unix, the error 2 would likely
be an ENOENT errno, as in no device there, as addressed.
Presumably, you've performed the basic diagnostic steps that would be
done at the operating system level to test for whether the hardware
is intact (as in cabling) and operating (is everything turned on?)
and responding...  What did you find at that level?  Does the library
respond to its Web page or SNMP or similar probes?  Any errors in the
operating system error log?  Was any work performed by operators or
vendors (as in repairing or replacing a key drive)?  Did your
operating system people make any configuration changes?  Were there
any site power problems which may have damaged equipment?

  Richard Sims

On Jan 28, 2009, at 6:26 PM, Erwin Zavala wrote:


  LIBVOL i500  (SESSION: 3)
01/28/2009 18:20:57  ANR8840E Unable to open device lb0.1.0.2 with
error 2.
  (SESSION: 3, PROCESS: 5)
01/28/2009 18:20:57  ANR8441E Initialization failed for SCSI
library I500.
  (SESSION: 3, PROCESS: 5)
01/28/2009 18:20:57  ANR8460E AUDIT LIBRARY process for library
I500 failed.
  (SESSION: 3, PROCESS: 5)
01/28/2009 18:20:57  ANR0985I Process 5 for AUDIT LIBRARY running
in the
  BACKGROUND completed with completion state
FAILURE at
  18:20:57. (SESSION: 3, PROCESS: 5)
01/28/2009 18:21:13  ANR2017I Administrator EZAVALA3 issued
command: QUERY

Re: TSM admin processes

[Paul Dudley]

On Jan 26, 2009, at 10:35 PM, Paul Dudley wrote:

>> ...
>> If there are thousands of files backed up via TSM which will stay on
>> the
>> backup tapes in the library for a number of years probably without
>> being
>> required for a restore, is there a way of moving these files to tapes
>> which can then be checked out of the library, thereby freeing up
slots
>> in the library for more scratch tapes?
>>
>
> You could employ a two-level storage pool hierarch and MIGDelay in the
> upper level in conjunction with periodic migration, which would
> migrate old files (actually, Aggregates) which had not been recently
> used in restorals.  Thereafter you would use the principle described
> in Admin Guide topic "Managing a Full Library" to externalize the
> lower level volumes.  But: getting operators to respond to mount
> messages to return tapes to the library is problematic.
>
>Richard Sims  http://people.bu.edu/rbs/

Fortunately I have the use of a second IBM Tape Library for TSM which
uses LTO2 tapes. If I understand you correctly this is what I could set
up:

Currently my BKPPOOL is on disk and the Next Storage Pool for that is
BKPLTO3POOL (LTO3 tapes). I create a new storage pool called
BKPLTO2POOL on the second LTO2 tape library and make that the Next
Storage Pool for BKPLTO3POOL. I then set the MIGDelay parameter for
BKPLTO3POOL to 180 so that any file that has not been written or read in
the past 180 days gets migrated to BKPLTO2POOL.

Is that feasible?


Thanks & Regards
Paul

Paul Dudley
Senior IT Systems Administrator
ANL Container Line Pty Limited
Email: pdud...@anl.com.au
Web: http://www.anl.com.au







ANL DISCLAIMER

This e-mail and any file attached is confidential, and intended solely to the 
named addressees. Any unauthorised dissemination or use is strictly prohibited. 
If you received this e-mail in error, please immediately notify the sender by 
return e-mail from your system. Please do not copy, use or make reference to it 
for any purpose, or disclose its contents to any person.

filespace is write protected

[ashish sharma]

Hello,

While trying to retrieve data , i am getting error

"Filespace is write protected"

Could anyone help?


--
Best Regards
Ashish Sharma
ST Microelectronics Ltd.
919717003853