What about an incremental or asynchronous restore (or whatever we may
want to call it)... 

The file space may have 2TB but how much of it is changing every day ?
5%, 10 %, 15% ?

I Would try the following:

1) copy the dsm.opt file to the target machine
2) target machine only: 
        Issue a "dsmc restore /source_mount_point/ /target_mount_point/
-subd=y
        You can wait until it completes, even if it takes days because
the production FS is yet on the source machine
3) target machine only:
        Issue a dsmc restore /source_mount_point/ /target_mount_point/
-subd=y -ifnewer
        the "ifnewer" option will restore only the changed files
        You can do this several times until you get a better picture of
how much files and GB are changing per day.

4) Pick a day to shift and a timeout for the all operation
5) Source machine: stop the sharing service
6) Source Machine: final incr backup 
7) Target machine: restore with if-newer option
8) "Go" or "No go"
8.a) If restore finishes before the time out, shift the service to the
target machine
8.b) If timeout reached before restore completes, Start the service
again on the source machine. Rethink.


Does this makes sense ?

Cheers,
jmc


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Huebner,Andy,FORT WORTH,IT
Sent: sexta-feira, 12 de Dezembro de 2008 19:08
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Best way to use TSM to move 2Tb of data

Again this is not a TSM solution, but we use an EMC product to duplicate
disks.  As long as both disks are available to the system at the same
time take a look at OpenMigrater if you have access to EMC software.  It
does a block level copy while the system is up.  When it is done it
keeps the drives synced until a reboot replaces the old drive with the
new one.  We usually see about 20-30GB an hour.  We have done 10 million
+ file systems in just a few hours.

Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nicholas Rodolfich
Sent: Friday, December 12, 2008 11:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Best way to use TSM to move 2Tb of data

Well, it turns out that the client has no downtime for this system so I
don't think the image thing is an option. Not to mention one of the
admins installed the LVSA code through the GUI setup wizard the night
before and chose to reboot later and the system crashed with a bugcheck
for TSMLVSA.sys yesterday. IBM had multiple tickets where this had
occurred at other customers in their database. We are waiting on a
reasonable explanation from IBM but the client is not too comfortable
with the image idea at this point and is looking to use their old Backup
Exec system where they have been successful doing this in the past
(SHAME! SHAME!). I suggested the robocopy method to them but it is their
decision/data.

Thanks for all of your help!! Your are a great bunch of folks!!

Nicholas



If you assume a file create rate of about 100,000/hour then you are
looking at a 20 hour restore if all else goes well.  You might squeeze
more file creates out of your new server, but who really knows?  If you
assume a 200 GB/hour transfer rate and use image instead, you can cut
the restore time in half. You can't improve the file create rate by
using multiple streams.
In fact, that actually reduces the rate.

I'm still advocating the image route.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nicholas Rodolfich
Sent: Thursday, December 11, 2008 3:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Best way to use TSM to move 2Tb of data

It is ~2,000,000 individual files after hours.


This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this e-mail or
its attachments. If you have received this e-mail in error, please
notify the sender immediately by return e-mail and delete all copies of
this message and any attachments.
Thank you.


Please help Logica to respect the environment by not printing this email  /  
Merci d'aider Logica à préserver l'environnement en évitant d'imprimer ce mail 
/  Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei 
die Umwelt zu schuetzen  /  Por favor ajude a Logica a respeitar o ambiente não 
imprimindo este correio electrónico.



This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.