ADSM-L

Re: [ADSM-L] Best way to use TSM to move 2Tb of data

2008-12-11 14:58:27
Subject: Re: [ADSM-L] Best way to use TSM to move 2Tb of data
From: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 11 Dec 2008 14:57:17 -0500
What kinid of data is it:  static files that don't change much (stuff),
database, lots of files being created/deleted.

Rick






             Nicholas
             Rodolfich
             <NRodolfich@CMAON                                          To
             THEWEB.COM>               ADSM-L AT VM.MARIST DOT EDU
             Sent by: "ADSM:                                            cc
             Dist Stor
             Manager"                                              Subject
             <[email protected]         Best way to use TSM to move 2Tb of
             .EDU>                     data


             12/11/2008 02:36
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Hello All,

I have a client that needs to move a 2Tb volume on their Windows file
server. Their TSM sever is also on Windows w/TSM v5.3.4. What is the
fastest/best  way to accomplish this. We tested an archive but it only got
340Gb overnight. They don't have enough disk based pool space to land it
there so we will have to use tape. I suggest kicking up the
resourceutilization parameter on the client to enable multiple sessions but
I am hoping you guys/gals can teach me something.

Thanks for all your help!!



Nicholas

-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.