Hi list!

Thanks again!
Pete

Werth, Dave wrote:

Personally I would leave all levels unchecked as that means allow any
level.  Most of the time in the past when I've had problems with backups
wanting to go to the default pool it's because I tried to place
restrictions on the backup level for that pool.  One other thing to keep
in mind is that the index is backed up from the Networker Server, not
the client the index is tied to.  Also, anything you put in the save
sets field other than "All" will restrict that client instance to only
what's in the save sets field so putting "index:" in there would
restrict it to only that.

David Werth
Garmin AT, Inc
Salem, Oregon
dave.werth<at>garmin.com

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Peter Grace
Sent: Tuesday, January 08, 2008 7:47 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] indexes want to save to pool "Default"

Peter Grace wrote:

In my case, in my "windows" definitions, I have the Save Sets field completely empty, but I have hosts defined with our windows hosts and our levels all checked. Should I have "index: " in the save sets

field?

Thanks!

Pete

Faidherbe, Thierry wrote:

Hello,

If it goes to default pool, it means that the pool you expect
to be used is too restrictive. It may be in term of allowed device

list from pool "windows", backup level, ..... or availability in jukebox ....

Anyway, check definition of pool "windows" at first stage.
Maybe is that pool not available or not authorized to be

mounted by the devices attached to backup server (or different media type)

As best situation, avoid index/bootstrap to be processed during night

when
io activity is at the highest level. To do so, turn on option
"NO INDEX SAVE" from each groups) and create a first group where all
clients are member of (eg call it "INDEX_AND_BOOTSTRAP").
Schedule that group once/twice a day then dataload is lower and
force the pool to be used by flagging group.
Finally, create a second group (eg "BACKUP_SERVER_OS"), put only
backup server, enable auto scheduling by legato.

Doing so, you will get coherent view of mediadb and 1 backup with
all client file indexes at a time.

HTH

TH



Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant

 *********       *********  HEWLETT - PACKARD SPRL/BVBA
 *******    h      *******  Hermeslaan, 1a
 ******    h        ******  B-1831 Diegem
 *****    hhhh  pppp *****  BELGIUM
 *****   h  h  p  p  *****
 *****  h  h  pppp   *****  Phone :    +32 (0)2  / 729.85.42
 ******      p      ******  Mobile :   +32 (0)498/  94.60.85
 *******    p      *******  Fax :      +32 (0)2  / 290.15.49
 *********       *********  Email/MSN : thierry.faidherbe(at)hp.com
                                  Internet  : http://www.hp.com/
      I  N  V  E  N  T

      Enterprise number 0402.220.594  RPM/RPR Brussels

Winners don't do different things, ... they do just things

differently!

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]

On Behalf Of Peter Grace
Sent: mardi 8 janvier 2008 15:41
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] indexes want to save to pool "Default"

Hi List!

When setting up our fresh 7.4 install, I was under the impression

that I

set up my savegroup correctly such that everything saves to the same
pool (in this case, 'windows'.)  However, every time the savegroup

runs

it attempts to save the indexes to pool 'Default'.  Could someone

point

me in the direction of which setting I need to change to fix this?
RTFM's are fine in this case if you tell me whereabouts in the admin
manual I can find it :)  I've done a bit of searching but as of yet

not

found where I might fix this.

Thanks!

Pete

To sign off this list, send email to listserv AT listserv.temple DOT edu and

type "signoff networker" in the body of the email. Please write to networker-request AT listserv.temple DOT edu if you have any problems with this list. You can access the archives at http://listserv.temple.edu/archives/networker.html or via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER <http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>

To sign off this list, send email to listserv AT listserv.temple DOT edu and

type "signoff networker" in the body of the email. Please write to networker-request AT listserv.temple DOT edu if you have any problems with this list. You can access the archives at http://listserv.temple.edu/archives/networker.html or via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER <http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

-------------------------
This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.
Thank you for your cooperation

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER