What I would recommend instead, since you have hardware available:

Install 6.2.3 on the new box, load your DB as a DR exercise.
Then upgrade 7.1 over it.
You can do that at your leisure, without impacting your production at all, or 
having to shut production down.

If you have no problems, then just flop the 7.1 code on top of your production 
system.
Upgrading the code takes usually less than 30 minutes.

That will make your test easy, and minimize the production downtime.

(Upgrading from 5.x to 6.x is hard.  Once you are on 6.x, the upgrades are 
easy.  Just always make sure you have a DB backup, just in case.)

W


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Ryder, Michael S
Sent: Thursday, April 03, 2014 12:24 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM 7.1 upgrade path(s) on Windows

Hello Folks:

I'm preparing to upgrade our TSM 6.2.3 server to TSM 7.1 -- both are on Windows.

It's a side-by-side upgrade, and if possible I'd like to leave the existing TSM 
6.2.3 environment alone during the upgrade, so that I can easily halt the 
upgrade if I run into any problems.

I've been searching TSM documentation and the Internet for a few days now and 
can't find anything reliable -- is there an upgrade path I can take to let me 
do that?  I was hoping for something like... this -- copy database files and 
configuration to brand new server... install 6.2.3, and then 7.1 over it.

Is there any documentation in this respect, best practices or good community 
experiences?  Please relate to me anything you can share!

Best regards,

Mike Ryder
RMD IT Client Services