Hi
I'll admit to having not read all of the notes in this thread, so apologize if
this is not germane to the discussion.
If you have two tape drives, both set with 'target sessions' of 4, and send 10
backups to those tape drives, here's how NetWorker will allocate the backups:
Tape Drive A - 1, 2, 3, 4, 9
Tape Drive B - 5, 6, 7, 8, 10
NetWorker will allocate backups to the first tape drive until the 'target
sessions' value is reached, and will then allocate backups to the next tape
drive until its target sessions value is reached, until all target devices
usable by the target pool have reached their 'target sessions' value. Then,
NetWorker will round-robin backups to each of the tape drives until the 'max
sessions' value for the tape drive is reached, or some other maximum (server
parallelism, etc.) is reached.
Is this helpful?
Thanks
tl
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of STANLEY R. HORWITZ
Sent: Friday, June 03, 2011 7:50 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Limiting a client to one of two tape drives
Yup. All savesets are in the same pool. I still don't see why a single
tape drive out of two tape drives with a target sessions value much higher
than what is required cannot receive four concurrent savesets instead of
having them spread across both tape drives.
On 6/3/11 7:47 AM, "bingo" <networker-forum AT BACKUPCENTRAL DOT COM> wrote:
>Let me suggest to walk away from the parallelism for a moment. As i
>mentioned already, NW should not behave that way.
>
>The question is whether all save sets go to media of the same pool. If
>not, then it is obvious tha NW must use both drives.
>
>+----------------------------------------------------------------------
>|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
>|Forward SPAM to abuse AT backupcentral DOT com.
>+----------------------------------------------------------------------
>
>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 with 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 with 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 with 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
|
