I remember to have seen that kind of behaviour.
If I remember correctly, it was caused by DNS
troubles or by an extra alias on backup server.
Have once a check at your dns or use hosts file.

Check/hardcode at least your backup server ips,
all of your storage nodes and verify alias field
for each client resources of these components.

HTH

Th 




Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
                                  
 *********       *********   HEWLETT - PACKARD
 *******    h      *******   1 Rue de l'aeronef/Luchtschipstraat
 ******    h        ******   1140 Bruxelles/Brussel/Brussels
 *****    hhhh  pppp *****  
 *****   h  h  p  p  *****   100/102 Blv de la Woluwe/Woluwedal
 *****  h  h  pppp   *****   1200 Bruxelles/Brussel/Brussels
 ******      p      ******   BELGIUM
 *******    p      *******                             
 *********       *********   Phone :    +32 (0)2  / 729.85.42  
                             Mobile :   +32 (0)498/  94.60.85
                             Fax :      +32 (0)2  / 729.88.30  
     I  N  V  E  N  T        Email/MSN : thierry.faidherbe(at)hp.com
                             Internet  : http://www.hp.com/
Enterprise number 0402.220.594 - RPM/RPR Brussels
 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Johan Robinson
Sent: vendredi 8 juin 2007 14:13
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Default pool suddenly stopped working correctly

Thanks Edward!

Yes, creating an INDEX pool might be the correct way. There are many 
schools and thoughts about that. What I am interested in, is how this
could 
ever happen?

We have many pools defined and sometimes we create new pools and remove 
others. 

Why doesn't a normal 'save' without arguments stop going to the Default 
pool?

I'll check on those dates if we did any pool changes.

//JOHAN

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