ADSM-L

Re: Help with ITSM Disk Pool/Client backup expectations

2003-07-31 10:57:12
Subject: Re: Help with ITSM Disk Pool/Client backup expectations
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 31 Jul 2003 10:56:43 -0400
The clients are all writing to the disk storage pool concurrently.
That's the cool thing about TSM -- You don't have to "schedule" tape drive
availability, and clients don't all have to start and stop backing up at
exact times.

I don't think it's round-robin, though.

The backups are driven from the client end, not the server end.

When the backup starts on the client end, each client goes noodling through
its file systems looking for files that need backing up.  The client
collects (by default) 50 files or 50 MB, whichever comes first, into a
package and sends that package via TCPIP to the TSM server.  Then the client
goes back to looking for more files to back up.

So traffic from the clients to the server is all interleaved.  And I think
like any other client-server application, it's first-come first-served for
each transaction package the clients send to the server.

Different clients will back up at different speeds, depending somewhat on
the throughput of your network, but usually affected most by factors at the
client end.

Hope that helps.
Wanda Prather
Johns Hopkins University Applied Physics Laboratory
443-778-8769

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


-----Original Message-----
From: Ken Sedlacek [mailto:Ken_Sedlacek AT KYRUS DOT COM]
Sent: Wednesday, July 30, 2003 2:13 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Help with ITSM Disk Pool/Client backup expectations


Enviro:

W2K TSM server 5.1.6.3, w/primary disk storage pool, migration to DLT tape
library.
W2k/NT client 5.1.5.15

Scenario:

2-3 client backup sessions happening at one time.

Question:

Are all the backups being serviced and written to the disk pool in some
round-robin fashion?

or, is any 1 client backup session being totally completed before another
client session is started?

or, just how does multiple concurrent client sessions operate in this
scenario?


Is there any documentation on this behavior?

TIA



Ken Sedlacek
AIX/TSM/UNIX Administrator
ksedlacek AT kyrus DOT com

IBM Certified Specialist: RS/6000 AIX v4.3 Support
IBM Certified Specialist: RS/6000 SP & PSSP 3
Tivoli Certified Consultant - Tivoli Storage Manager v4.1

<Prev in Thread] Current Thread [Next in Thread>