I think you can use the command export node with the parameter
filedata=none. Example:
export node test filed=none tos=server1
Please, correct me if I'm wrong.
On Thu, Nov 20, 2008 at 9:13 PM, Wanda Prather [EMAIL PROTECTED] wrote:
You can't copy just some DB entries.
Other people have
thanks for comments so far.
Yeah, but wouldn't that lead to an empty node in the target server? Of
course I want to migrate the data, I just don't like the idea of
copying ten tapes worth of data to a set of temporary tapes and then
again to new storage pool tapes (I have not tried it yet, but I
I never used, but I think that might work for you...
If you use the command UPDATE LIBV, then you can change the owner of the
volumes...
-UPDate LIBVolume--library_name--volume_name--
--++--+---+---
'-STATus--=--+-PRIvate-+-'
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of Henrik Ahlgren
Sent: Friday, November 21, 2008 4:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] export/import nodes
thanks for comments so far.
Yeah, but wouldn't that lead to an empty node
Yeah, but wouldn't that lead to an empty node in the target server? Of
course I want to migrate the data, I just don't like the idea of
copying ten tapes worth of data to a set of temporary tapes and then
again to new storage pool tapes (I have not tried it yet, but I assume
TSM doesn't just
Hi,
I have a simple question.
Let's say that I'm splitting a large TSM server instances into few
smaller servers, using a shared library with library manager/client
architecture.
Now, if there are pretty big client nodes whose data is on collocated
tapes, can I move a node between
: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik
Ahlgren
Sent: Thursday, November 20, 2008 8:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] export/import nodes
Hi,
I have a simple question.
Let's say that I'm splitting a large TSM server instances into few
smaller servers
I've heard that this might be on the roadmap for tsm 6.X for X = 2
On 20 nov 2008, at 15:32, Henrik Ahlgren wrote:
Hi,
I have a simple question.
Let's say that I'm splitting a large TSM server instances into few
smaller servers, using a shared library with library manager/client
You can't copy just some DB entries.
Other people have reported success with restoring the TSM DB to the new
server, then deleting the unwanted filespaces/nodes on the new server.
But you need to review your tape inventory carefully. The fact that your
storage pool is collocated doesn't mean
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: [ADSM-L] Export / import nodes with shared library
Hi again,
Thank you Neil !
- Sorry, but 'UPD LIBV ... OWN=' do not solve the problem ...
--- ANR8969E The owner of volume XX can not be updated to owner TSM1.
- we also use 'EXPORT NODE ... TOSERVER
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von
Strand, Neil B.
Gesendet: Freitag, 27. Juni 2008 16:39
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: [ADSM-L] Export / import nodes with shared library
Otto,
- You should be able to just update the libvol owner
Hi TSM'ers,
We splitted our TSM Server up to five instances (four library clients, one
library manager, 3494)
To move the nodes to new instances we export/import them on tape
(TSM0 is library manager, TSM1-TSM4 are library clients)
(1) on instance TSM1: Export node to volume(s)
: [ADSM-L] Export / import nodes with shared library
Hi TSM'ers,
We splitted our TSM Server up to five instances (four library clients,
one library manager, 3494)
To move the nodes to new instances we export/import them on tape
(TSM0 is library manager, TSM1-TSM4 are library clients)
(1
13 matches
Mail list logo
