Ahh, one of my real TSM wishes. I want a GIVE FILESPACE command, to
simply transfer ownership of a filespace from node A to node B, where A
and B are on the same server. GIVE FILESPACE could also help with
export/import issues of name collisions.
But lacking that, I agree with Kelly that by the time you (over)think
of, develop, and test something ingenious, a fresh backup would have
already been done. If this data is huge, and you really don't have space
for more copies of inactive files than your current policy would allow
for a single node with this much data, then you could make a separate
management class and gradually adjust the number of inactive copies on
the old node downward to correspond to the averave number of inactive
copies that are building up naturally on the new node, so that the total
number of inactive copies remains relatively stable. This will be fuzzy,
not exact - the goal is only to avoid running out of scratch tapes, so
precision isn't needed.
Roger Deschner University of Illinois at Chicago rogerd AT uic DOT edu
Academic Computing & Communications Center
============== "java" and "slow" are both 4-letter words ===============
On Mon, 14 Dec 2009, Kelly Lipp wrote:
>I think it will certainly be easier to re-backup the data. Faster? Not sure,
>but probably as fast as an export would go.
>
>I guess I wouldn't over think this: set up new client after the data is moved
>and do the backup. Probably be done before you know it. You will obviously
>lose the previous versions of files, but you could keep the old filespaces
>around until the data expires. If this is mostly on tape I'd opt for this
>approach.
>
>Kelly Lipp
>Chief Technology Officer
>www.storserver.com
>719-266-8777 x7105
>STORServer solves your data backup challenges.
>Once and for all.
>
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
>Of David Longo
>Sent: Monday, December 14, 2009 1:40 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: [ADSM-L] Move Windows filespaces
>
>I have TSM sever 5.5.2.0. Also have a W2K3 client with
>version 5.5.0.0 BA client, doing backups only. This has
>about 2 dozen drives and therefore filespaces. There is
>many TB of data involved in total and these are all SAN disks.
>(Also many TB of data that is left, so not easy to say redo that
>either.)
>
>For several technical reasons, they need to move about half the
>SAN disks to another server and leave half on existing server.
>They will just rezone those disks to the new server, no copying
>involved. I certainly don't want to backup all this "moved" data
>again. If was ALL being moved to new server, I could just
>RENAME NODE and FILESPACES and be done with it, have done that
>before. But is not the case.
>
>As I see it, my only option is to EXPORT NODE for the filespaces that
>are being moved and then import again into new node. I have
>never used Export Node, but have almost a few times over the years.
>
>Am I correct that this is my only option? Other than backing up in new
>location and deleting in old - or would that be faster and easier? NO
>idea on the speed this works. I have 3584 library with LTO2 and 3
>drives/tapes.
>
>Thanks,
>David Longo
>
>Health First, Inc.
>
>
>#####################################
>This message is for the named person's use only. It may
>contain private, proprietary, or legally privileged information.
>No privilege is waived or lost by any mistransmission. If you
>receive this message in error, please immediately delete it and
>all copies of it from your system, destroy any hard copies of it,
>and notify the sender. You must not, directly or indirectly, use,
>disclose, distribute, print, or copy any part of this message if you
>are not the intended recipient. Health First reserves the right to
>monitor all e-mail communications through its networks. Any views
>or opinions expressed in this message are solely those of the
>individual sender, except (1) where the message states such views
>or opinions are on behalf of a particular entity; and (2) the sender
>is authorized by the entity to give such views or opinions.
>#####################################
>
|
