Re: [Networker] Limiting a client to one of two tape drives

Dave,

You're probably correct in that a cron job is probably my only option.
Fortunately, this isn't an important thing. The server that I want to back
up in this manner will be decommissioned this October, so I think I will
make due the way things are now.

On 6/6/2011 1:34 PM, "Werth, Dave" <dave.werth AT garmin DOT com> wrote:

>Stan,
>
>I've been following this thread with interest.  It's apparent that there
>probably is no solution within NetWorker for your problem.
>
>Perhaps you could write a cron job that monitors that status of the tape
>drives, say every 5 minutes, and modifies whether they are enabled or
>disabled as necessary.  That's a poor substitute for something built into
>NetWorker but it may get the job done.
>
>Dave
>
>Dave Werth
>Garmin AT, Inc.
>Salem, Oregon
>-----Original Message-----
>From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
>Behalf Of STANLEY R. HORWITZ
>Sent: Sunday, June 05, 2011 5:49 PM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: Re: [Networker] Limiting a client to one of two tape drives
>
>Unfortunately, that would not work because I need to have the other tape
>drive available for group cloning.
>
>On 6/5/11 3:41 PM, "denis.mail.list AT free DOT fr" <denis.mail.list AT free 
>DOT fr>
>wrote:
>
>>Hello,
>>
>>what about providing only one or two tapes available to the server ?
>>Making the others read-only with nsrmm (under Linux, you can script this
>>in an easy way).
>>
>>Denis
>>
>>----- "STANLEY R. HORWITZ" <stan AT TEMPLE DOT EDU> a écrit :
>>
>>> Greetings everyone,
>>>
>>> I have one Linux client with four TB worth of data spread over four
>>> mount
>>> points. This client is in its own savegroup, which has a tape pool
>>> devoted
>>> exclusively to it. I want its backup to be limited to only one of the
>>> two
>>> tape drives in my tape library. I have been playing around with
>>> different
>>> settings, but every time I try it, the backup mounts two tapes even
>>> though
>>> each drive has 16 as its target sessions value. This is with NetWorker
>>> 7.6
>>> SP1 on a Linux box.
>>>
>>> If anyone has any ideas on how I can do this without setting a pool
>>> target
>>> limit of 1, please let me know.
>>>
>>> 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
>
>
>This e-mail and any attachments may contain confidential material for the
>sole use of the intended recipient. If you are not the intended
>recipient, please be aware that any disclosure, copying, distribution or
>use of this e-mail or any attachment is prohibited. If you have received
>this e-mail in error, please contact the sender and delete all copies.
>
>Thank you for your cooperation.
>

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