I agree.
Several points to keep in mind.
1. File type device is treated exactly like a tape, However....
2. Each save set is saved on disk in a single file. (no multiplexing of
data).
3. Each save set is individually retrievable. (parallel random access of all
save sets)

Why do you need multiple pools?
I have a single pool (Daily HardDrive), and all clients backup to it.  Then
Networker automatically stages some of the data off to my jukebox pool
(Daily Jukebox) when it hits the high water mark.  The only reason to use
multiple pools is too seperate the data to different tapes by retention
time.  With a file device, each save set is an individual file on the hard
drive, and it gets transfered to tape one save set at a time. This greatly
simplifys the administration.

I have two groups (Nightly with Clone, and Nightly without Clone). If I want
a client cloned, I transfer it from one group to the other.  Storage nodes
at remote locations require their own groups and pools, but other than this,
it works beautifully.

Calvin Thomas
UNIX System Administrator
NACA Logistics



-----Original Message-----
From: Terry Lemons [mailto:lemons_terry AT EMC DOT COM]
Sent: Thursday, October 31, 2002 12:37 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Staging in Networker?


Hi

In some material I received from Legato, I read:

"It is also possible to establish multiple file type devices on the same
disk. Since each file type device is identified by the path to the directory
that will contain the save set data, creating multiple file type devices on
one physical device is simply a mater of creating multiple directories and
defining multiple devices"

Also, in the NetWorker for UNIX Administrator's Guide 'Save Set Staging'
section in Chapter 5, I read:

"Save set staging is a process of transferring data from one storage medium
to
another."

So, it's good to note that moving savesets from disk storage to tape storage
is just one of the possible uses for staging.

Peter, I hunted in vain for the "staging devices are officially only
supported with one device per filesystem" limitation you mentioned.  Do you
mean that only one 'file type' device can be created per file system?  If
so, I know that isn't correct, because I'm using two 'file type' devices in
a single file system in NetWorker for Windows V6.2.  Also, is it necessary
to have multiple 'file system' pools, or would only one pool meet the needs?

Thanks!
tl

Terry Lemons
CLARiiON Application Solutions Engineering
        EMC²            
where information lives

4400 Computer Drive, MS D239
Westboro MA 01580
Phone: 508 898 7312
Email: Lemons_Terry AT emc DOT com

-----Original Message-----
From: Peter L. Buschman [mailto:plb AT iotk DOT com]
Sent: Thursday, October 31, 2002 12:58 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Staging in Networker?


I've experienced several annoyances with staging as implemented in
Networker:

First, staging devices are officially only supported with one device per
filesystem.
This is very limiting if you want to stage to volumes that are in different
pools.  One
company I know turned automatic staging completely off and had to write
their own
scripts to stage savesets and then re-label volumes that were all setup in
the same
filesystem.  There was no other way to pool the diskspace they had for
staging and
they needed a lot of staging volumes.

The one-volume per file-system limitation makes for very inefficient usage
of diskspace.

--PLB

At 01:35 PM 10/30/2002 -0500, David W. Loveless wrote:

>Are you using the staging features of Legato Networker to push backups
>first to disk and later to tape?
>If you are, we'd like to hear about your experiences. What problems have
>you had? What disks are you using? Have you purchased any add-on software
>from Legato to help the staging process.
>
>We're currently running Networker 6.1.1 on Solaris 8 and are actively
>exploring this feature.
>
>
>Thanks for your help!
>
>--
>Note: To sign off this list, send a "signoff" 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.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=