Author: Johan Robinson <johan.robinson AT GMAIL DOT COM>
Date: Fri, 8 Jun 2007 07:11:34 -0400
Hello, EMC could not help me with this issue, so I'll give it a try here, to see if there are others who have experienced the same behaviour. INDEX backups normally did run to the Default pool. But o
Author: "Coty, Edward" <Edward.Coty AT AIG DOT COM>
Date: Fri, 8 Jun 2007 07:53:16 -0400
Well creating a pool for indexes was the right thing to do. You shouldn't use the default pool except as a catch all. When the default stopped working did you create any other pools between when it w
Author: Johan Robinson <johan.robinson AT GMAIL DOT COM>
Date: Fri, 8 Jun 2007 08:13:16 -0400
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
Author: "Faidherbe, Thierry" <Thierry.Faidherbe AT HP DOT COM>
Date: Fri, 08 Jun 2007 09:56:41 -0500
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/ha
You don't direct backups to a pool. Instead you do a backup, and the best pool is chosen. So it's possible to add a new pool that now matches a backup better. If that happened, then the backups coul
Author: Paul Langford <plangfor AT AB.BLUECROSS DOT CA>
Date: Tue, 12 Jun 2007 16:11:07 -0600
The default pool has NO groups in it. If you create a new pool, and forget to put groups in it this becomes the new default. I use this 'feature' to capture clint side 'pushes'. Paul L. could You don
That's correct. It has no restrictions of any kind (groups, clients, levels, devices). Any backup is eligible to reach the default pool. When creating a pool, you set restrictions on it. The most re