ADSM-L

Re: [ADSM-L] Rename volumes or other workaround

2010-03-19 16:08:01
Subject: Re: [ADSM-L] Rename volumes or other workaround
From: Jánský Vítězslav <Vitezslav.Jansky AT T-SYSTEMS DOT CZ>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 19 Mar 2010 21:07:26 +0100
Barcode label is not TSM label. You can use barcodes as source for TSM tape 
labels (labelsource), to speed up inventory and for some other operations - but 
you dont have to if you want. So you shouldn't have any problems with old tapes.

V.J.
________________________________________
Odesílatel: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] za uživatele 
Shawn Drew [shawn.drew AT AMERICAS.BNPPARIBAS DOT COM]
Odesláno: 19. března 2010 20:19
Komu: ADSM-L AT VM.MARIST DOT EDU
Předmět: [ADSM-L] Rename volumes or other workaround

A few years ago, when TSM was first implemented here, the ADIC i2000 was
set so that the L3 suffix was not passed to TSM.
For many reasons I would like to change this to include the suffix.

The main problem I see is that when we need to read from any of the old
tapes, TSM will look for the old tape label.

The only way I could imagine doing this is by partitioning the library and
hoping that it will let me have a different barcode rule for each
partition.  Then, migrate the data from one partition (without the suffix)
to the new partition (with the suffix)
After that, I would have to redefine all of our backupsets and migrate all
of our (thousands of tapes) ndmp data.

In other words, I am NOT going to do that.   Is there any, possibly
undocumented,  way to rename the volumes in TSM 5.5?


Regards,
Shawn
________________________________________________
Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

<Prev in Thread] Current Thread [Next in Thread>