Also check your "Override policy storage selection" marked on each of your 
schedules. Normally it's unchecked and will inherit from the policy setting.

~ Robin

-----Original Message-----
Subject: Re: [Veritas-bu] Incorrect Storage Unit

If you did it too fast, changes to policies can take up to 10 minutes to
be implemented (by default).    



-----Original Message-----
Subject: [Veritas-bu] Incorrect Storage Unit

I have installed a new tape library(tld1). I still have my original library 
(tld0) connected. I've taken a couple of policies, copied them to new policies 
and changed only the storage unit within the policy from

media-server-tld0 to media-server-tld1. I manually executed a test backup of 
PolicyA-TLD1 and saw exactly what I expected to see: The policy contacted the 
new robot, mounted a new tape and ran the backup on

the new library, finishing with status code 0.

When I do the same thing with a second policy, PolicyB-TLD1 is contacting the 
original library, mounting tapes in the original library... etc. It finishes 
successfully, but I can't figure out why it isn't contacting the new library. 
I've gone back in and made sure that the storage unit in PolicyB-TLD1 is TLD1 
and not TLD0, and it is set correctly.

Any thoughts while I dig around the Symantec website?

Thank you.

  - Heathe Kyle Yeakley
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu