If only the Wintel boxes had/have a FC card-- I could buy a spare (or two
for compatibility with existing hardware) and go about using the 3590 tapes
for backupsets.  Perhaps this would be doable for any boxes that died here
at HQ, but for the 150 odd other boxes statewide, this isn't a feature for
them.

I have found some DVD-R with external SCSI so I could attach it to the 6M1,
and create a media that the wintel boxes (on the whole) could read without
problems.

lisa



                    Steve Harris
                    <[EMAIL PROTECTED]       To:     [EMAIL PROTECTED]
                    LD.GOV.AU>                   cc:
                    Sent by: "ADSM: Dist         Subject:     Re: Keeping an handle on 
client systems' large drives
                    Stor Manager"
                    <[EMAIL PROTECTED]>


                    06/17/2002 06:55 PM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"






Lisa,

You have SAN. Can you san attach your TSM drives?  That way you could
direct attach them to the Wintel boxes without a direct physical
attachment.

Steve Harris
AIX and TSM Admin, Queensland Health, Brisbane Australia

>>> [EMAIL PROTECTED] 17/06/2002 23:33:26 >>>
I was mucking about on Thursday, checking out the backupset option for a
server that died that day.  It appears to me that I need to find a CD/DVD
burner that will attach to a 6M1, or to a FC director to be able to make
backupsets in my environment?  I understood the documentation to mean that
the sequential media device needs to be defined as a device class on the
server, and since I am AIX in a SAN environment (well, almost SAN...we're
working on it), I don't have many options for the NT boxes that I would
like to make backupsets for  (I mean, I don't see connecting an NT box to a
3494 or a 3590 drive).  I guess I could use an 3580 that would be
"portable"?

Am I missing something, or is this the way it actually is?

thanks,
lisa



                    "Seay, Paul"
                    <seay_pd@NAPTH       To:     [EMAIL PROTECTED]
                    EON.COM>             cc:
                    Sent by:             Subject:     Re: Keeping an handle
on client systems' large drives
                    "ADSM: Dist
                    Stor Manager"
                    <[EMAIL PROTECTED]
                    IST.EDU>


                    06/13/2002
                    10:54 PM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






Actually, Dan, sorry for my remark.

What you have to do is revisit what you are saving and put in exclude.dirs
for all directories that contain software that can be rebuilt from a common
desktop image (hard drive replacment).  Have your users save their
documents
in specific folders and only back them up.  Then they just have to
customize
their desktop configure their node name in the dsm.opt and restore the
stuff
that is backed up.

This is the trade-off.

The other approach is the backupset that is a CD sent to them and
incremental restore from that point forward.

Paul D. Seay, Jr.
Technical Specialist
Naptheon, INC
757-688-8180


-----Original Message-----
From: Dan Foster [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 11:25 PM
To: [EMAIL PROTECTED]
Subject: Keeping an handle on client systems' large drives


I've always been curious about something.

How do you keep an handle on the fact that commodity PC storage is growing
at a far faster rate than tape capacity/system is?

For example, if I had a small LAN of about 300 PCs -- let's say, an
academic
or corporate departmental LAN environment... each has at least a 40 GB HD,
and probably a fair amount of apps and files on them. In the stores, I see
drives up to 160 GB, with even larger ones on the way!

So let's say, an average of 25 GB utilization per system... a single full
backup would be about 7.5 TB, which is quite a few tapes ;) Not everybody
is
using LTO or higher capacity.

So do those sites rely purely on the incrementals to save you? Or some site
specific policy such as tailoring backups to exclude (let's say) C:\Program
Files, or some such...? Just wondering.

Not every site is lucky enough to be able to convince the beancounters the
merits of having a backup system that keeps up with the needs of the end
users, even if it means one has to explain doomsday predictions on the
business bottom line -- they invariably hear that then say "Oh, pshaw,
you're just exaggerating because you want money...". It sucks to be the one
that's right ;) And the ones who warns well before a nasty event occurs may
also be the first one to be fired out of spite after something happens and
gets the blame for not having prevented it.

-Dan Foster
IP Systems Engineering (IPSE)
Global Crossing Telecommunications



**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.

Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited.  It may be subject to a statutory duty of
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail.  You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************

Reply via email to