You cannot mark primary stgpool volume as offsite. As per the help/Reference Guide: "3. This value is valid only for volumes in copy storage pools." You cannot overcome the TSM design. Still can use MOVe MEDia OVFLOcation='Your off-site vault'. However think twice is this what you want good enough! You are talking about archives, i.e. long-term storage. And what if tape ages and gets unreadable or courier drop it and is broken?! That is the idea behind primary and copy pools. And you can check out primary pools from the library if are short on slots. Backupsets are again providing you same non-duplicate (not secured) scenario. Their main goal is quick restore not long-term archiving.
Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: How does Archiving and Backupsets work??? When I archive a file space to ARCHIVEPOOL (a primary storage pool) I can't change the status of the volume to OFFSITE. Is there a way to archive files spaces to tape and sent them out without keeping a copy on a primary storage pool? In other words I would like my archives to be sent directly to a tape that will be going to the vault. Is this possible? Must I use a backupset to do this? I have created a backupset to try it out and I can't tell which tapes is used with which backupset... How or where can you track your backupset volumes? This is all I get when I query backupsets for the node in question: Node Name HAL Backup Set Name DOMHAL.502394 Server object ID for the client object 502394 Date/Time 2002-05-04 12:00:08.000000 Retention Period 365 Description No Description Device Class Name LTOCLASSOFF It doesn't tell me which volume it is on!!! Thanks for the help, Etienne Brodeur