The target sessions is 5. This means that NetWorker will allocate
5 sessions to the drive, before it uses another drive.
In your scenario, once the other clients have finished, there
are only the 4 sessions at a time from the one client left to go to
the tape. So it will only use one tape drive.
Before you change anything, check that the drive is streaming (running
at maximum speed). If not, then the client is not generating the
backup streams fast enough, and you need to reconsider the resources
on the client machine.
You may also wish to change the priority of the client that finishes
last. (Perhaps you could set the priority of the Solaris machine with
only 2 save sets to be last, perhaps a priority of 600, and the AIX
machine to be 400).
The numbers below assume you have counted the server as a client, if
not then you have 6 clients and you need to adjust some of the figures
below, but the principle is the same.
With your list NetWorker will start 1 save set from all 5 clients,
then it will start an additional 3 save sets from 3 clients, and 1
additional save set from a 4th client, giving 15 save sets.
As a save set finishes, another save set from the same client will
start until all save sets on that client finishes. Only when a
client has run out of save sets, will additional save sets be started
for other clients.
So the 5th client will only run one save set at a time, until one of
the other clients completes, at which point it will run two save sets
in parallel until another client is nearly finished.
One way to even out this behaviour would be to reduce the client
parallelism for the smaller clients, leaving the sessions for the
larger clients.
On 24/11/2005, at 8:44 AM, Manel Rodero wrote:
Hello,
I would like to know if is it possible to use two or more simultaneous
devices (tapes) to backup different savesets from a same machine.
I ask this because I have a "problem" in this environment:
- 1 Server:
Windows 2000 7.1.2.Build.325
- 5 Clients:
AixOS 7.1.2.Build.325
2 x Solaris 7.1.2.Build.325
Linux 7.1.2.Build.325
Windows 2000 7.1.2.Build.325
The server has 3 SDLT320 drives, Server parallelism = 15, Target
sessions
per tape = 5, Client parallelism = 4 and Priority = 500 for all five
clients.
I run a group with these five clients to do a full backup of these
savesets:
- Aix: 14 savesets
- Solaris: 2 savesets
- Solaris: 10 savesets
- Linux: 8 savesets
- Windows: 6 savesets
The backup starts ok, it runs at full speed using the maximum
bandwith of
the Legato server (at this moment 100Mbps) and USING THE 3 DRIVES!
After some hours, all but one client -the Aix one- has finished the
backup.
The "problem" is that at this time, Legato is doing the backup of 4
sessions
using ONLY 1 DRIVE (the other 2 doesn't have nothing to do). This
client has
8 more savesets pending.
The questions is: why Legato doesn't use the other 2 drives to
backup the
remaining 8 savesets instead of waiting for the current sessions
and use
only 1 drive again? The selection of a drive isn't done by saveset?
Is this
selection done by client? At the begining of the group backup?
Any idea about this situation will be very helpful.
Thank you very much.
--
o o o Manel Rodero | LCFIB - UPC
o o o Helpdesk Manager | Campus Nord - Modul B6
o o o Laboratori de Calcul | Jordi Girona, 1-3
U P C Facultat Informatica Barcelona | 08034 Barcelona (Spain)
|
manel AT fib.upc DOT edu | Tel: +00 34 93 401 6940
http://www.fib.upc.edu/~manel | Fax: +00 34 93 401 7040
To sign off this list, send email to listserv AT listserv.temple DOT edu
and type "signoff networker" in the
body of the email. Please write to networker-
request AT listserv.temple DOT edu if you have any problems
wit this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
