That is correct.  All of my TSM servers have their DB/LOGS on internal
mirrored drives.  Only SAN connection on most of my TSM servers are for
tape drives.  Two years was the first time we connected EMC SAN storage to
two of my Linux TSM servers (I was the "guinea pig" since we never did this
before) and it was an adventure.

Since the extract is only 40GB, I could do that on the V5.5 server but I
didn't see a way to tell the upgrade GUI to skip to the import step.

My testing (on a slow test system) showed it should take less than 6-hours
so I am doing it this Friday.  I might try the "network method" folks seem
to prefer.


On Mon, Jun 17, 2013 at 9:34 AM, Huebner, Andy <andy.huebner AT alcon DOT 
com>wrote:

> I am guessing the DB and Logs are on local drives.  I went from 5.4 to 6.2
> by giving the new servers a SAN copy of the DB and logs, performed the
> extract with the 5.5 upgrade tool to disk then loaded 6.2 from there.  You
> could also extract to a SAN drive and give that drive to the 6.x server.
>
> Andy Huebner
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Michael Roesch
> Sent: Monday, June 17, 2013 8:22 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Migrating last 5.5 server to 6.3.3 and new hardware
>
> Hi Zoltan,
>
> On Mon, Jun 17, 2013 at 3:16 PM, Zoltan Forray <zforray AT vcu DOT edu> wrote:
>
> > Way too much data to move (80TB)
>
>
> wow OK then that would be not the best idea :-)
>
> Regards,
> Michael
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html