Not if the storage pool is colloacted by filespace...



                    "Joshua S.
                    Bassi"
                    <jbassi@IHWY. To:    [EMAIL PROTECTED]
                    COM>          cc:    (bcc: Robin Sharpe/WA/USR/SHG)
                                  Subject:
                    08/31/01             Re: Floating Client License Period
                    07:17 AM
                    Please
                    respond to
                    "ADSM: Dist
                    Stor Manager"







Yes, we had thought of this.  Another requirement would be to place each
partition on a separate tape (including incrementals).  If we are
talking 2500 clients copying data across to disk on the TSM server (the
network people won't allow this to be done with NFS) and then backing up
each file space onto a separate tape then we would need to either 1)
create all these virtual nodes or 2) use include statements to bind each
one to it's own storage pool.

Either way would be a maintenance headache!  And of course the customer
does not want a dedicated TSM person - what else is new "Silly-cone
Valley."


--
Joshua S. Bassi
Independent IT Consultant
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Richard Sims
Sent: Friday, August 31, 2001 3:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Floating Client License Period

>I have a customer who has plans to backup thousands of small Linux
>boxes.  These boxes will be backed up incrementally until the 100GB
>partition on each is full and then they will perform a full backup.  At
>that time, the client will be decommissioned and not back up any
longer.
>Cost is a major issue for this customer.  They cannot afford to buy 1
>client license for each of these tiny hosts.

Joshua - If you *really* had to, you could possibly get by with one
         client license by using -nodename=ThatSingularNodename
and remounting subject file systems read-only on mount points like
"/ActualNodeName.TrueFilesystemName", which is to say that you would
end up with mucho filespaces under one client, but identifiable as to
the client and file system they actually came from.  Not that anyone
would *want* to warp space like this.

I also presume that the partition of interest is not a system partition,
which would be pointlessly redundant to back up from multiple systems,
except for unique configuration files.

  Richard Sims, BU

    "Think different."   - Apple

Reply via email to