I'm doing that...
Lots of different situations...
If they say the data is REALLY REALLY REALLY important I leave it in the tsm
server, have it in an isolated storage pool with a copypool copy of it AND I
export the node, twice, and give the end user one of the copies.
If it is REALLY important (like IRS data) I keep it in the server and have
an isolated primary and copy pool with it (and run periodic audits on the
volumes)
If they stand there picking their nose and say "Duh, we better keep this
around forever 'cause duh..." I just export the node, print the summary info
from the tsm server's activity log showing ALL THE VOLUMES AND THEIR
SEQUENCE, check the tapes out of the atl and stick the tapes in a rack with
the paper work in a folder at the end...
and when I export the client, I only export ACTIVE data...

GOD I LOVE TSM :-)

Dwight



> ----------
> From:         Siciliano, Gerald
> (Moody's)[SMTP:Gerald.Siciliano AT MOODYS DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, August 01, 2000 1:42 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Export DB - Usage
>
> Has anyone ever used 'export node' as long term storage for node data?
>
> I have about 24 nodes that are being retained for 10yrs, the data has not
> been accessed since the backups were initially done.  These nodes
> represent
> about 30% of my TSM server database.  To reclaim the space in the DB can
> the
> 'export node' command be used for this purpose?
>
> This is just a thought I had, any suggestions?
>
>
> Thanks,
> Jerry Siciliano
>