This is a brilliant idea.
BTW, I think easiest to restrict pools is assign explicit list of the
devices of particular jukebox to particular pool. In this case Networker
will always know what jukebox to use for that pool. Besides, if auto
media management and recycle from/to pools is turned on, then no need to
pre-lablel (or pre-load) tapes and keep track what tape should go in
what jukebox.
"Faidherbe, Thierry" wrote:
>
> Up to now, all clients have same storage node affinity
> and same clone storage node affinity causing some target
> clone streams to go over lan, source parts of the cloning
> being inititated from the SN that's filled into the
> READ HOST attribute from the jukebox.
>
> A fix ? That's quite easy : use differents pools....
>
> For pool 1, select drives from primary server's tape lib
> into pool 1 definition and load only tapes from
> pool 1 into the jukebox.
> For pool 2, select drives from SN into pool 2 definition
> and load only tapes from pool 2 into SN's jukebox.
>
> Then, distribute your 5 copies of the same client into
> different groups and assign group 1 to pool 1, .....
>
> When group1 will be lauched, tape into pool 1 will be
> requested. Networker will then look at primary server's
> jukebox and mount the tape.
>
> When group2 will be launched, tape from pool 2 will be
> requested. As primary server's jukebox has no tape from pool2,
> the request will fail and will be forwarded to SN's jukebox
> and save will be send to the SN:jukebox.
>
> HTH,
>
> Th
>
> Kind regards - Bien cordialement - Vriendelijke groeten,
>
> Thierry FAIDHERBE
>
> HPCI - Storage & Server Integration Practice
> Tru64 Unix and Legato EBS Consultant
>
> ********* ********* HEWLETT - PACKARD
> ******* h ******* 1 Rue de l'aeronef/Luchtschipstraat
> ****** h ****** 1140 Bruxelles/Brussel/Brussels
> ***** hhhh pppp *****
> ***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
> ***** h h pppp ***** 1200 Bruxelles/Brussel/Brussels
> ****** p ****** BELGIUM
> ******* p *******
> ********* ********* Phone : +32 (0)2 / 729.85.42
> Mobile : +32 (0)498/ 94.60.85
> Fax : +32 (0)2 / 729.88.30
> I N V E N T Email : thierry.faidherbe AT hp DOT com
> Internet : http://www.hp.com/
> ________________________________________________________________________
>
> MOBISTAR SA/NV
>
> SYSTEM Team Charleroi, Mermoz 2 Phone : +32 (0)2 / 745.75.81
> Avenue Jean Mermoz, 32 Fax : +32 (0)2 / 745.89.56
> 6041 GOSSELIES Email : tfhaidhe AT mail.mobistar DOT be
> BELGIUM Web : http://www.mobistar.be/
> ________________________________________________________________________
>
>
>
> -----Original Message-----
> From: Neild, Jim [mailto:Jim.Neild AT SSHA.ON DOT CA]
> Sent: Tuesday, June 24, 2003 9:42 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] How to send different savesets from same client
> to different servers?
>
> Had the same problem....I would love to know if this can be "fixed"
>
> Jim
>
> -----Original Message-----
> From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
> Sent: Tuesday, June 24, 2003 3:39 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] How to send different savesets from same client to
> different servers?
>
> Hi,
>
> I have like 5 instances of the same client, each with different
> savesets, group, schedules, etc. I would like to have one of them get
> backed up to the primary server's tape library, but the rest I want to
> back up to the storage node server's library. Currently, the Storage
> nodes field has:
>
> storage_node_server_name
> primary_server_name
>
> and this is the same for all the client instances. If I change it on the
> particular client instance to instead just say:
>
> primary_server_name
>
> then it changes it for all the instances. How can I set just that one to
> be different? Does NetWorker allow this? We're running 6.1.1 under
> Solaris 8. Storagenode server is running same but under RedHat Linux
> 7.3.
>
> Thanks.
>
> George
> George.sinclair AT noaa DOT gov
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can also
> view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
