ADSM-L

Re: [ADSM-L]

2008-11-25 06:07:57
Subject: Re: [ADSM-L]
From: "Minns, Farren - Chichester" <fminns AT WILEY DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 25 Nov 2008 11:06:42 +0000
Thank you :-)

Was that in the Admin Guide? And if so, why couldn't I find it ? :-0)

Many thanks again

Farren



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Otto Chvosta
Sent: 25 November 2008 11:04
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L]

  HI-MB.w i le!
              <49254D18.8020801 AT uni-ulm DOT de>            
<40F507919CB02E4AA5A48A4F2517A5E810276D3018 AT CHI-MB.wiley DOT com>            
<D4B07980AD4F044FAF5BAC9720BF54A50163C4BB AT VHEXCHANGE3.corp.cdw DOT com>      
      A<40F507919CB02E4AA5A48A4F2517A5E810276D3232 AT CHI-MB.wiley DOT com>     
       <5C78244F05844D40970238D9716501CF17C1FA AT tecexch.godalming.tectrade.co 
DOT uk>  <40F507919CB02E4AA5A48A4F2517A5E8102AD70C4E AT CHI-MB.wiley DOT com>
X-ASG-Orig-Subj: AW: [ADSM-L] Question about group collocation
Subject: AW: [ADSM-L] Question about group collocation
Date: Tue, 25 Nov 2008 12:02:51 +0100
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To:  <40F507919CB02E4AA5A48A4F2517A5E8102AD70C4E AT CHI-MB.wiley DOT 
com>
Thread-Index: AclLCPutulWfoZefRTeCteX968Jr/wAC2v/rAPXuQQAAAEH64A==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Virus-Scanned: ClamAV 0.93.3/8677/Tue Nov 25 04:52:25 2008 on 
maud.srv.meduniwien.ac.at
X-Virus-Status: Clean
X-PMX-Version: 5.4.3.345767, Antispam-Engine: 2.6.0.325393, Antispam-Data: 
2008.11.25.104923
Message-Id: <20081125110251.4E7B320027 AT smtpa.meduniwien.ac DOT at>
X-Barracuda-Connect: maud.srv.meduniwien.ac.at[149.148.224.13]
X-Barracuda-Start-Time: 1227610972
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at marist.edu
X-Barracuda-Spam-Score: -2.02
X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=3.5 
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.11110
        Rule breakdown below
         pts rule name              description
        ---- ---------------------- 
--------------------------------------------------

Nodes who are not in a group are collocated by node.

---------
If you specify COLLOCATE=3DGROUP but do not define any collocation
groups or if you specify COLLOCATE=3DGROUP but do not add nodes to a
collocation group, data is collocated by node. Be sure to consider
tape usage when organizing client nodes into collocation groups.
For example, if a tape-based storage pool consists of data from
grouped and ungrouped nodes and you specify COLLOCATE=3DGROUP, the
server does the following:
   + Collocates by group the data for grouped nodes only. Whenever
     possible, the server collocates data belonging to a group of
     nodes on a single tape or on as few tapes as possible. Data
     for a single node can also be spread across several tapes
     associated with a group.
   + Collocates by node the data for ungrouped nodes. Whenever
     possible, the server stores the data for a single node on a
     single tape. All available tapes that already have data for
     the node are used before available space on any other tape is
     used.

---------=20

-----Urspr=FCngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag =
von
Minns, Farren - Chichester
Gesendet: Dienstag, 25. November 2008 11:57
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: [ADSM-L] Question about group collocation

Hi all

I currently have a tapepool collocated by node.

I have created my first collocation group and added three client nodes =
to
it.

So, if I now update the tapepool to collocate by 'group', am I right in
thinking it will still collocate all nodes NOT in the collocation group =
by
node?

Thanks

Farren Minns

-------------------------------------------------------------------------=
---
--------------------------------
This email (and any attachment) is confidential, may be legally =
privileged
and is intended solely for the use of the individual or entity to whom =
it is
addressed. If you are not the intended recipient please do not disclose,
copy or take any action in reliance on it. If you have received this =
message
in error please tell us by reply and delete all copies on your system.
=20
Although this email has been scanned for viruses you should rely on your =
own
virus check as the sender accepts no liability for any damage arising =
out of
any bug or virus infection. Please note that email traffic data may be
monitored and that emails may be viewed for security reasons.

John Wiley & Sons Limited is a private limited company registered in =
England
with registered number 641132.

Registered office address: The Atrium, Southern Gate, Chichester, West
Sussex, PO19 8SQ.
-------------------------------------------------------------------------=
---
--------------------------------
------------------------------------------------------------------------------------------------------------
This email (and any attachment) is confidential, may be legally privileged and 
is intended solely for the 
use of the individual or entity to whom it is addressed. If you are not the 
intended recipient please do 
not disclose, copy or take any action in reliance on it. If you have received 
this message in error please 
tell us by reply and delete all copies on your system.
 
Although this email has been scanned for viruses you should rely on your own 
virus check as the sender 
accepts no liability for any damage arising out of any bug or virus infection. 
Please note that email 
traffic data may be monitored and that emails may be viewed for security 
reasons.

John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.

Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
PO19 8SQ.
------------------------------------------------------------------------------------------------------------

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