Well, remember that "DRM" is for Disaster Recovery of your "environment".
If an SST crashes into your site, DRM is designed to allow you to build up a
TSM environment with pretty recent copies of your client's data and then
allow the clients to be rebuilt from your rebuilt TSM server.
I classify that as being pretty different than someone just asking to keep
specific data for a really long time.
One example of where an "export" of the node has been used in our
environment is... a bunch of seismic studies of land had been performed in
preparation for drilling oil wells, it was then decided not to develop a
large portion of these areas, this land is in a holding state with the
possibility of being sold later, all the seismic studies (already done)
could make the land more profitable... so rather than just throw the data
away, it was isolated on a client, that client was backed up, that client
was exported (to two different sets of tapes) and the physical client box
was turned off and thrown away... (I hope those tapes hang in there...)
So for the purpose of long term storage of data... if you're totally out in
the blue, you're not alone... I'm out there too.
Dwight
> ----------
> From: Henrik Hansson[SMTP:Henrik_Hansson AT ALBINT DOT COM]
> Reply To: ADSM: Dist Stor Manager
> Sent: Wednesday, August 02, 2000 8:28 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Export Node - Usage to fake Archiving
>
> Would this "Export Node" be something that could replace the Archiving
> command?.
> I understand that I have to keep track of the backups, and tapes myself.
> Maybe its still easier then letting DRM keep track of them and it will
> reduce the space used on the server right?? (Find the archiving somewhat
> tricky to set up, but I'm a newbie :-)) )
>
> Or am totaly out in the blue here??
>
> Henrik Hansson
> Nomafa AB
> Web; www.nomafa.com
> Mail; henrik_hansson AT albint DOT com
>
>
>
> "Cook, Dwight
> E" To: ADSM-L AT VM.MARIST DOT EDU
> <cookde AT BP DOT CO cc:
> M> Subject: Re: Export DB -
> Usage
> Sent by:
> "ADSM: Dist
> Stor Manager"
> <ADSM-L AT VM DOT MA
> RIST.EDU>
>
>
> 2000-08-01
> 21:14
> Please
> respond to
> "ADSM: Dist
> Stor Manager"
>
>
>
>
>
>
> 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
> >
>
|
