Kent, Yes that works to the extent that client data is collocated on the tapes. If there is another client's data on that tape, that client's data will move too.
Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Kent Monthei Sent: Wednesday, November 14, 2001 9:53 AM To: [EMAIL PROTECTED] Subject: Need to move old/misdirected backups of a filespace from one tape storage pool to another A node has been misdirecting a huge amount of data into our on-site TAPEPOOL because of missing management class bindings in an inclexcl file (several missing 'include <filespace> <management class>' statements). Several of the node's filespaces should have been backed up directly to another tape storage pool that goes off-site daily. Instead, they now occupy a lot of TAPEPOOL tapes/slots in an already-crowded tape library. We corrected the management class bindings, ran a backup, and confirmed the new backups are now going to the proper storage pool. However, we also confirmed that all the old backups still occupy tapes/slots in the tape library's TAPEPOOL. Is there a way to move old filespace backups out of TAPEPOOL and & merge them into another storage pool ? This applies to a subset of filespaces for 1 node. I vaguely recall someone suggesting this (or a very similar) procedure: 1) identify volumes containing data for the node/filespace 2) define a diskpool whose migration destination is the correct tapepool 2) use MOVE DATA to move the content of those volumes back to that diskpool 3) use MIGRATION to move all the data to the correct destination pool(s). Will this work? Does it presume or rely upon collocation by node or by filespace? What happens to any data on those volumes from other filespaces or other nodes? Will existing/undesired content presently in COPYPOOL be removed immediately? I emphasize that the backups are valid, just in the wrong pool, and need to be preserved. Duplication to COPYPOOL was never intended and we'd like to ensure both the TAPEPOOL and COPYPOOL content for these filespaces is removed. -rsvp, thanks Kent Monthei GlaxoSmithKline
