I don’t know if it’s of interest to you, Zoltan, but I keep a demo VM of 
WFW3.11 around with an ADSM 2.1.0.8 client.  I backup and restore it using a 
TSM 7.1.6.0 server with deduplicated container pools with no problem.  It’s fun 
to show this to prospects to demonstrate unsupported compatibility.  I’d 
restore C: and make another drive bootable if I could remember how to make one 
show up in File Manager.

The WFW also runs AOL Instant messenger and I can log onto my old AOL user 
account.

Browsing with Netscape Navigator doesn’t work well on any website so I’m not 
going back to WFW as my desktop any time soon.

___________________________
Bill Smoldt

From: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> on behalf of 
Zoltan Forray <zforray AT VCU DOT EDU>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Date: Wednesday, July 27, 2016 at 1:10 PM
To: "ADSM-L AT VM.MARIST DOT EDU" <ADSM-L AT VM.MARIST DOT EDU>
Subject: [ADSM-L] Restoring from really old TSM clients

I have a user who wants to archive their old Solaris SPARC system before
killing it, and keep the archives for 5-years.

This is a Solaris 5.9 system so the most current client is v5.5.

I am about to upgrade my servers to 7.1.6 (from 6.3.5.100). What are the
chances the archives will be restore/retrieve-able in 5-years when SP V10
or 11 is the server level?

This isn't our oldest client.  There are 2-Solaris 5.8 servers with 5.3
client still backing up.  Until last year, we still had a 4.x client.

How do you handle long-term archiving (yes I realize 5-years really isn't
that long) or discontinued/decommissioned servers?

What is the largest gap between client and server version that someone has
successfully restored/retrieved data from?

--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT edu<mailto: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