This is from 4/1. Copying the NetWorker alias.
-----Original Message-----
From: Wes Ono
Sent: Tuesday, April 01, 2003 11:27 AM
To: Billy Crafton
Cc: Todd Osterbur; Holly Mullin; Carole Ellison; Janelle Espinoza; Ken Reid;
Wes Ono
Subject: RE: Wright-Patterson AFB - DX2000/NetWorker integration issues
First, I'm not really sure why they want to migrate the backup savesets. I
was given that as a requirement. I know that NCSA is doing the same thing,
only using DX/UL.
NetWorker tracks the files backed up in the device. If the file-type device
is relabeled, then the data is deleted.
A NetWorker file-type device grows until either the "default capacity" is
reached, or the underlying device becomes full. It is possible to set the
"default capacity" on a file-type device. It could be set to the size of
the DVD, then any single file-type device directory should fit on a DVD.
Savesets wouldn't have to span DVDs from DX's point of view, since NetWorker
would cut them off when the device was "full".
DX/UL has a script that will rename the directories under a file-type
device, making it work something like an autochanger (point at
directory/volume "A", then at directory/volume "B"). This allows one file
type device to mount different "volumes".
Adding a bunch of NetWorker devices isn't a good solution, since each one
creates an MMD. Too much overhead for a bunch of idle "drives".
Using a Linux server for DX/UL might be tough, since they already have
DX2000 and this DVD jukebox.
Hope this helps,
Wes
-----Original Message-----
From: Billy Crafton
Sent: Tuesday, March 25, 2003 2:19 PM
To: Wes Ono
Cc: Todd Osterbur
Subject: FW: Wright-Patterson AFB - DX2000/NetWorker integration issues
Importance: High
Hey Wes,
Todd and I were discussing this and had a few questions. (Also, we are just
south of Wright Patt)
First, what is the specific reason they only want to migrate savesets vs.
the actual data? Is this for version control to WORM media? Also, with a
file type device, is version control maintained in NW or does it overwrite
an old version of a file? I.e., do the physical devices continue to grow
until they fill the device?
If the saveset size is an issue, what about creating partitions that are
equal to the data size of a DVD? It would result in more file devices but it
sounds like they are going to continually add devices anyway.
Lastly, how tuff would it be to get a linux server in there for DX/UL as the
data mover (with DX2000) to allow spanning of media? I doubt option 1 or 2
below will happen quickly although I think DX2K needs to span media.
-----Original Message-----
From: Holly Mullin
Sent: Tuesday, March 25, 2003 2:54 PM
To: Todd Osterbur; Sam Ou; Chip Niemiller; Billy Crafton; Tom Fuldner
Cc: Janelle Espinoza
Subject: FW: Wright-Patterson AFB - DX2000/NetWorker integration issues
Importance: High
Can you guys look at this?
-----Original Message-----
From: Carole Ellison [mailto:cellison AT legato DOT com]
Sent: Tuesday, March 25, 2003 1:24 PM
To: dx AT legato DOT com; networker AT legato DOT com
Cc: cbrannan AT imss DOT com; wono AT legato DOT com; cthatcher AT legato DOT
com;
kreid AT legato DOT com
Subject: FW: Wright-Patterson AFB - DX2000/NetWorker integration issues
Importance: High
I have a customer that has been doing a proof of concept with Networker and
DX. It is the US Air Force. The current value of the opportunity is only
about $70K but the whole Air Force is a potential customer. They are at
the end of testing and are just about ready to give up. What can we offer
to help them out and sell this opportunity?
Carole
Carole Ellison
Federal Account Manager
Legato Systems
2600 Tower Oaks Blvd, 5th Floor
Rockville, MD 20852
240.747.6617 office
240.747.6209 fax
540.273.8248 NEW CELL
-----Original Message-----
From: Wes Ono [mailto:wono AT legato DOT com]
Sent: Thursday, March 20, 2003 3:14 PM
To: Ken Reid; Carole Ellison
Cc: Wes Ono
Subject: Wright-Patterson AFB - DX2000/NetWorker integration issues
Wright-Patterson (Dayton, OH) wants to use NetWorker to back up data to
file-type devices. These file-type devices would reside on DX2000 extended
drives, and these extended drives would migrate the saveset files to DVD.
There are a couple of problems that prevent this with DX2000 and NetWorker
on Windows platforms:
1) NetWorker 6 (and 7) do not allow saveset size to be restricted via the
"saveset cutoff size" attribute. This attribute was used by NetWorker 5
clients, but is no longer used by the NetWorker 6 and 7 clients. Because of
this, saveset files in the file-type device can grow quite large.
2) DX2000 will not span a file across multiple platters. So if the saveset
file is larger than the capacity of a DVD, then the file will not migrate.
For this to work, one of the following would need to occur:
1) awareness of "saveset cutoff size" would need to be built back into the
NetWorker client software
2) the ability to have a file span multiple media items would need to be
built into DX2000
I suspect that #1 would be easier to implement than #2.
A similar solution appears to be possible with DX/UL, and is being deployed
at NCSA (National Center for Supercomputer Applications). For that matter,
NCSA is also using DXDB to allow portions of a saveset file to be recalled
when NetWorker recovers a small amount of data.
So the question is, can NetWorker or DX2000 be modified to support this
capability?
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
