Re: DISASTER Client Restores Slow

2002-05-17 Thread Nikolai Sonin

Nikolai Sonin
System Architect
ESI Group
28381 Encina Drive Suite 100
Winters CA, 95694-9007
530-795-0200 ext. 235




Talafous, John G. [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
05/17/2002 07:33 AM
Please respond to ADSM: Dist Stor Manager


To: [EMAIL PROTECTED]
cc:
Subject:Re: DISASTER  Client Restores Slow


You can use backup sets to create point in time restores of machines. Also
with that few tape drives have you considered collocation.  That way
especially with LTO a small server and several incrementals will fit on
one tape.
Our CEO's PC is backed up using TSM with Collocation to an LTO drive and
after a month of incrementals all his data sits on one tape.  A test
restore of his workstation took less than 3 hours.  Also if you have over
100 servers you need to get more tape drives.




I am sure TSM will wait. And while we're on this subject, we are looking
at
Disaster Recovery plans and the path we must take using TSM to recover a
couple hundred servers.  It looks bleak.

We are finding that, due to incremental forever backups, recovery times
are
extremely long because of tape mount after tape mount after tape mount. In
a
real disaster, we expect to take an entire day or more to recover a single
server. With a limited number of tape drives the recovery time required
for
100 servers could take weeks.

Has anyone else run into this dilemma? What is TSM's direction? How can I
speed up the recovery process?

John G. Talafous  IS Technical Principal
The Timken CompanyGlobal Software Support
P.O. Box 6927 Data Management
1835 Dueber Ave. S.W. Phone: (330)-471-3390
Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034
[EMAIL PROTECTED]   http://www.timken.com



Re: Expanding our system

2002-05-17 Thread Nikolai Sonin

Nikolai Sonin
System Architect
ESI Group
28381 Encina Drive Suite 100
Winters CA, 95694-9007
530-795-0200 ext. 235




Tyree, David [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
05/17/2002 12:21 PM
Please respond to ADSM: Dist Stor Manager


To: [EMAIL PROTECTED]
cc:
Subject:Expanding our system


We currently have a 3494 library with two 3490E1A drives
attached to a WinNT4 box running quad Xeon 550's and a gig of RAM. TSM is
version 4.2. We have about 30-40gig of data coming in over about an eight
hour time window each evening and night. Things are fine for now. We are
looking to do some improvements in the next several months.

The 3494 can be upgraded to 3590E1A using direct Fibre Channel attach.  I
do not know if the 3490's can coexist with the Fibre Channel 3590's, but I
do have customers that have 3494's with both SCSI 3490's and SCSI 3590's
in the same library.  They can not be in the same frame, but if they are
in separate frames it works well.

First thing we would like to do is to reload the server with
Win
2000 and TSM version 5.xx. In our shop, we can only speak MS. Other OS's
aren't an option. This we would like to do in 3-4 months. I think we can
handle this ourselves.

Next on the agenda, we are working towards getting some kind
of
a SAN in the budget for the first of the year. I don't know all of the
details at the moment but they are talking about 3-4 terabyte capacity.
Don't know how this will impact on new data coming into TSM. But the boss
man wants to see about adding another complete library with two more tape
drives.

For 3-4 Terabytes in 8 hours you would need 10 SCSI attached 3590E1A's.
For fibre channel you might be able to use less, but realistically you are
probably running what 20 - 30 Windows servers.  You will 10 drives just to
be able to do the tape copy pools and DRM management

The people we that installed our original system are gone so
we
can't go back to them for more hardware. Any suggestions on someone to do
this for us?





David Tyree
Microcomputer Specialist
South Georgia Medical Center
229.333.1155

Confidential Notice:  This e-mail message, including any attachments, is
for
the sole use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, use,  disclosure or
distribution is prohibited.  If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.



Re: Ordering license upgrades

2002-05-17 Thread Nikolai Sonin

Nikolai Sonin
System Architect
ESI Group
28381 Encina Drive Suite 100
Winters CA, 95694-9007
530-795-0200 ext. 235




Thomas Denier [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
05/17/2002 12:35 PM
Please respond to ADSM: Dist Stor Manager


To: [EMAIL PROTECTED]
cc:
Subject:Ordering license upgrades


We have a TSM 4.2.1.9 server running under OS/390. We are about to order
more client licenses. The last time we did this IBM and/or Tivoli required
us to tell them how the new licenses would be divided among different
platforms: how many for Windows NT, how many for AIX, and so on. The
charge per client license is the same regardless of operating system. The
'register license' command does not provide any means for distinguishing
between Windows NT licenses, AIX licenses, and so on. Why in the world
do we need to provide platform information in order to get more client
licenses?

So that Tivoli can know what clients are being used the most in customer
sites.  This allows them to get the right mix of support people and what
clients should be patched and tested first.  It also helps Tivoli
developers develop business cases for improving clients.  The Novel client
is not as popular as the NT client, and look where all the development
dollars are going.



Re: Sloooow Novell Backups

2002-05-16 Thread Nikolai Sonin

Nikolai Sonin
System Architect
ESI Group
28381 Encina Drive Suite 100
Winters CA, 95694-9007
530-795-0200 ext. 235




Firmes, Stephen [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
05/16/2002 03:03 PM
Please respond to ADSM: Dist Stor Manager


To: [EMAIL PROTECTED]
cc:
Subject:Slw Novell Backups


TSM server 4.2.1.9 on Solaris 8

TSM 5.1 client on Novell 5.1

Backing up a volume with 500,000 files approx 1k each.  The files are
being transfered to the tsm server approx 1/sec.  This is just a little
too sloow.  When using ftp to transfer these same files, either by
getting/putting the transfers fly.  This is leading me to believe that the
issue is with the TSM server/client settings.

Does anybody have any ideas on any settings in the dsm.opt that could be
changed to enhance performance?  Also I want to bind all objects in two of
the volumes to a specific mgt class.  All that is being bound to it is the
dirs.  Long day.  What am I doing wrong???

Here is the dsm.opt

***
COMMMETHODTCPip
TCPSERVERADDRESS catamount
TCPPORT  1500
tcpclientaddressxxx.yy.z.zzz

NODENAME  novell_test


INCLUDE sys:* tape9940
INCLUDE extravol1:* tape9940

This will work for the files.
INCLUDE extravol1:\...\*.* tape9940
INCLUDE extravol1:\...\* tape9940

EXCLUDE  sys:\system\secaudit.log
EXCLUDE  sys:\system\events.log
EXCLUDE  sys:\system\system.log
EXCLUDE  sys:\system\btrieve.trn
EXCLUDE  SYS:\system\tsa\err$hst.*
EXCLUDE  sys:\system\tsa\err$log.*
EXCLUDE  sys:\system\tsa\skip$log.*
EXCLUDE  sys:\system\tsa\tsa$temp.*
EXCLUDE  sys:\system\sys$log.err
EXCLUDE  sys:\_swap_.mem
EXCLUDE  sys:\vol$log.err
EXCLUDE  sys:\tts$log.err


NWPWFILE YES

passwordaccess generate
managedservices schedule webclient

Performance Parameters Try these first
TXNBYTEL  25600
TCPWINDOW 63
USELARGECOM YES
Process 15



Thanks.

Stephen Firmes
TSM Engineer
Tivoli Certified TSM Consultant
StorageNetworks, Inc
Work:  781-622-6287
http://www.storagenetworks.com