ADSM-L

Re: Multistreaming, Performance problems on WindowsNT

1998-11-05 15:44:51
Subject: Re: Multistreaming, Performance problems on WindowsNT
From: Jim Hunt <Jim_Hunt AT VENCOR DOT COM>
Date: Thu, 5 Nov 1998 15:44:51 -0500
I was looking more into doing a push of the data from the client instead of
polling from the
server. Thanks. Has anyone been able to write an NT script to move a
different file from vol1, vol2, and
vol3 at the same time? The key to this is after multiple 4 gig files are
created on different drives they all
can be moved to the ADSM server. Currently we have an application that
creates these files every 2 hrs and
we need to get them to tape before the next creation process takes place.


---------------------- Forwarded by Jim Hunt/IS/Vencor on 11/05/98 03:43 PM
---------------------------
---------------------------
"Kelly J. Lipp" <lipp AT STORSOL DOT COM> on 11/05/98 12:43:13 PM
"Kelly J. Lipp" <lipp AT STORSOL DOT COM> on 11/05/98 12:43:13 PM

Please respond to "lipp AT storsol DOT com" <lipp AT storsol DOT com>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Jim Hunt/IS/Vencor)
Subject:  Re: Multistreaming, Performance problems on WindowsNT




From a note yesterday from me...

Multi streaming means to have more than one job working on the problem.
 Ideally, this works best with clients that have more than one disk or
filespace, otherwise you can create big time disk contention by doing this.
 To use multi-streaming simply open more than one window on your
workstation, start dsmc and start multiple backups at the same time.
 Preferably working on different filespaces.  From this you can determine
if you might benefit from multi-streaming.  BTW, you can do the same thing
with restores.

To do this using a schedule, you will create n schedule daemons (in NT, you
use the dscmutil to create multiple services), each with a different
options file.  Each daemon will identify itself to the server as the same
node name.  Each different options file will specify a different domain to
backup.  You can either do this with the domain statement or using
include/exclude processing.  After creating the daemons, start them.  On
NT, you will have n services running.  All of them have identified
themselves as node mumblefratz and obtained the schedule from the server.
 In polling mode, they will all start their backups at the requested time.

So, in your four different options files, I would have different domains or
include/exclude options, different schedlogname and errorlogname (if you
don't do this, you don't even want to look at dsmsched.log!), the same
nodename and perhaps different server names if you want to use multiple
NICs.

This is cool.  How many of you are doing this already with success?

In prompted mode, as long as they are all on the same IP address, they will
probably start at the same time.  I didn't try prompted mode in my testing,
but common sense suggests if the IP address is the same, i.e., all will
start at the same time.  However, one reason you might undertake this
approach in the first place is to use multiple NICs in your clients and
servers.  In this case, I think you would have a problem doing this in
prompted mode.  Stick to polling.  I will cogitate on this further to see
what I think...

Kelly Lipp
Storage Solutions Specialists, Inc.
lipp AT storsol DOT com
www.storsol.com
(719) 531-5926

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