Has anyone seen this happen?

We are at 5.1.1 (server and client) under W2K - our default MC is STANDARD
in PS STANDARD which backs up to primary pool DISKPOOL.

We created two new MCs in POLICYSET STANDARD
1. STANDARD_NC to backup to diskpool DISKPOOL_NC
2. STREAMING_NC to backup to sequential pool LTOPOOL_NC

We validated the policyset and activated it.

We scheduled a backup for a server which should have used the default MC -
no overrides were specified in DSM.OPT or in the client option set. It
started to rebind and then failed because there was no space in pool
LTOPOOL_NC.

I thought it may only be checking that all pools defined for the PS had
space available so I set MAXSCRATCH to 500 in LTOPOOL_NC and rescheduled
it.  It rebound all files from the server and backup them up to a tape in
pool LTOPOOL_NC. I did a "select hl_name,backup_date,class_name from
backups.
.." which showed that all the files on the server had rebound to MC
STREAMING_NC.

Why didn't it continue to use the default MC?

David Fosdike
Senior Technical Specialist
Elders Limited

'...despise not the day of small things...'