Curtis Preston wrote: > I've seen this happen before after a failed backup job. Take a look at > the STREAMS file in /usr/openv/netbackup/db/images/<clientname>. See if > it has an ALL_LOCAL_DRIVES entry. If it does, remove it then re-run the > backup. >
Thanks Curtis. Didn't see anything in the STREAMS file like that. I've been doing some testing and if I manually include the specific filesystems in the File Selection list, it will back them up. Sort of bizarre though, if I go and switch the policy back to ALL_LOCAL_DRIVES, it will continue to only backup the filesystems I had previously manually listed, sort of like it's using some cached information for the policy. Is there anyway to see how's responding to or processing the bpmount information coming in from the client? Thanks, John -- John Meyers Computing Services Wright State University _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu