Do a DB Backup instead of a snapshot, and see what that does.  Not sure
of the difference, but I did a similar thing just a couple of weeks ago
with AIX and new hardware.

DB Backup to NFS mount on new TSM Server.
Restore DB to new server running same version (just 64bit instead of
32).
Restore db todate=today etc. etc.
Things went fine.  

Make sure the mount on the old server has the same directory structure
as the location on the new server.
Make sure to have just the volhist.out file, and not the devconfig
(that'll mess up where your new DB is located if its different from the
old).
Make sure to have your new server's db and log volumes formatted and
ready to use.  The restore seemingly reformats them, but I found that if
I didn't have them there and formatted things didn't go as well.  I
started up and tested the new server before I did the restore to make
sure it was working.
Make sure your new db is a little bigger than the old, just in case.

I was running 5.2.9 and upgraded to 5.5.1 after the move.

See Ya'
Howard

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Lee, Gary D.
> Sent: Wednesday, August 27, 2008 8:19 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Trouble doing a db restore
> 
> Server version 5.2.10
> OS solaris 8, and solaris 9.
> 
> Scenario:
> 
> Take db snapshot to nfs mounted filesystem from production server
> solaris v2.8 tsm v5.2.10.
> 
> Restore from snapshot onto test server v5.2.10 on solaris 9.
> 
> DB restore runs through, recovery log records are processed, and at
the
> end of it all, the server dies with message
> 
> ANR7821s: thread terminated due to segmentation violation.
> 
> This is testing a scenario for a migration of our tsm servers to new
> hardware.
> 
> Any ideas would be appreciated. I really would like to avoid having to
> export all our clients to a new server.
> 
> 
> 
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310