Charles, I'm going with "can't" at this point. I would have tried everything you did.
The question then is what do going forward. Obviously split the clients into two domains with one pointing at one library and the other at the other. To move those client's data from the original library to the new will require a move nodedata command. Or let that data die a normal death in the other pool... I'm sure your goal is to get the environment balanced as quickly as possible so the move nodedata command will be your option. The good news about that is you can specify multiple nodes. With reasonable tape performance this should work out fine. Thanks, Kelly J. Lipp VP Manufacturing & CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Charles A Hart Sent: Friday, January 12, 2007 12:38 PM To: [email protected] Subject: [ADSM-L] Updating a Volume's Devclass ? We had a situation where the same devclass was used for two different Libraries. We then created two devclasses and associated one lib with the original devclass and the other with a new devclass. The library with the new devclass can not mount any volumes becuae the volumes are still associated with the old devclass and won't mount. I looked @ upd volhist to change the devclass bu that's only good for DB and Export vols. I did try and associate the lib with a new devclass, then checkin the vols which worked, but then when we tried to mount the vol we get 01/12/07 13:11:35 ANR2336W Audit Volume terminated for volume P10058 - insufficient number of mount points available for removable media. (SESSION: 19664, PROCESS: 152) Any ideas on how to re-associate reg vols with a different devclass? Charles Hart UHT - Data Protection (763)744-2263 Sharepoint: http://unitedteams.uhc.com/uht/EnterpriseStorage/DataProtection/default. aspx This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
