Re: [ADSM-L] exporting a node from one TSM server to another

Richard...Thank you!


Looks like the command I use started the export from the beginning. Now
the question becomes which filespaces (extras) should I delete? I am
guessing the
botton filespaces.

SNIX222\f1    9 WinNT
SNIX222          \\SNIX222\c1
SNIX222          \\SNIX222\d1
SNIX222          \\SNIX222\e1


SNIX222\f2   15 WinNT

SNIX222          \\SNIX222\c2
SNIX222          \\SNIX222\d2
SNIX222          \\SNIX222\e2


Thanks



This is what the file space structure looks like on the source server.
(normal)

Node Name       Filespace   FSID Platform Filespace    Is        Capacity   Pct
               Name                      Type      Filespace        (MB)  Util
                                                   Unicode?
--------------- ----------- ---- -------- --------- --------- ----------- -----
SNIX222          SNIX222\Sys-    1 WinNT    VSS          Yes            0.0   
0.0
                temState\-
                NULL\Syst-
                em
                State\Sys-
                temState
SNIX222          ASR            2 WinNT    NTFS         Yes            0.0   0.0
SNIX222          \\SNIX222\f$    3 WinNT    NTFS         Yes       34,695.1   
6.6
SNIX222          \\SNIX222\c$    4 WinNT    NTFS         Yes       33,855.7  
56.9
SNIX222          \\SNIX222\d$    5 WinNT    NTFS         Yes       34,718.6  
34.3
SNIX222          \\SNIX222\e$    6 WinNT    NTFS         Yes       34,718.6  
13.0



This is the node now on the target server

Node Name       Filespace   FSID Platform Filespace    Is        Capacity   Pct

               Name                      Type      Filespace        (MB)  Util

                                                   Unicode?

--------------- ----------- ---- -------- --------- --------- ----------- -----

SNIX222           snix222\Sys-    1 WinNT    VSS          Yes            0.0   
0.0

                temState\-

                NULL\Syst-

                em

                State\Sys-

                temState

snix222          ASR            2 WinNT    NTFS         Yes            0.0   0.0

SNIX222          \\SNIX222\f$    3 WinNT    NTFS         Yes       30,718.0  
22.2

SNIX222          \\SNIX222\c$    4 WinNT    NTFS         Yes       30,710.2  
49.7

SNIX222          \\SNIX222\d$    5 WinNT    NTFS         Yes       30,718.0   
5.3

SNIX222          \\SNIX222\e$    6 WinNT    NTFS         Yes       30,718.0   
2.6

SNIX222           snix222\Sys-    7 WinNT    VSS          Yes            0.0   
0.0

                temState\-

                NULL\Syst-

                em

                State\Sys-

                temStat1

snix222          AS1            8 WinNT    NTFS         Yes            0.0   0.0

SNIX222          \\SNIX222\f1    9 WinNT    NTFS         Yes       34,695.1   
6.6

SNIX222          \\SNIX222\c1   10 WinNT    NTFS         Yes       33,855.7  
56.9

SNIX222          \\SNIX222\d1   11 WinNT    NTFS         Yes       34,718.6  
34.3

SNIX222          \\SNIX222\e1   12 WinNT    NTFS         Yes       34,718.6  
13.0

SNIX222          snix222\Sys-   13 WinNT    VSS          Yes            0.0   
0.0

                temState\-

                NULL\Syst-

                em

                State\Sys-

                temStat2

snix222          AS2           14 WinNT    NTFS         Yes            0.0   0.0

SNIX222          \\SNIX222\f2   15 WinNT    NTFS         Yes       34,695.1   
6.6

SNIX222          \\SNIX222\c2   16 WinNT    NTFS         Yes       33,855.7  
56.9

SNIX222          \\SNIX222\d2   17 WinNT    NTFS         Yes       34,718.6  
34.3

SNIX222          \\SNIX222\e2   18 WinNT    NTFS         Yes       34,718.6  13.













Richard Sims wrote:

See "restartable export" in IBM Tivoli Storage Manager Versions 5.4 and 5.5 
Technical Guide for the 5.5 enhancement which allows that.

On Feb 23, 2010, at 2:01 PM, Timothy Hughes wrote:

Hello all,

I have been exporting a node from one server to another the past couple
of days. I have had to cancel it a couple of times due to the log
filling up.

Does the export pick up from where it left off? I thought it did,
however I took a look at the filespace scenario and it looks wrong (too
many) on the TARGET SERVER.

Thanks