(1). If I do generate backupsets for these nodes, can I then delete the
filespace data to free up Tape Library space?
>>Yes. But before you decide that is a good thing, think about what you
would do, if someone ever wanted to retrieve a file off the tape.
Deleting the filespace data means all the file entries are purged from
the TSM db. You have no "inventory" of the data any more.
I believe it is possible, although difficult, to retrieve a single file
off a backupset tape. Better try it.
2). If I opt for export node, could I export the nodes, remove all
references to the nodes and re-import to the same TSM server if I ever
need to?
>>Yes. In the case of EXPORT, all the TSM DB entries are removed as
well. To access ANY of the data, you have to re-import the tape.
>>Other issues.
In both cases, where will your tapes be stored?
And will you have an offsite copy of this data any more? When you
delete the filespace from the primary pool, it is deleted from the copy
pool, as well. So you will need to make and track TWO backupsets, or
TWO EXPORT tapes.
>>Possible options :
If you decide on backupsets or export, use SELECT on the BACKUPS table
to dump a list of the filenames/backup dates to a flat file. You can
use that as a "table of contents" reference so that 6 months from now,
if somebody wants to know if there was a particular file on the tape,
you can find it.
Another way:
If your TSM DB size isn't currently a problem, and you just need to
regain the storage space :
1) create a new storage pool called "OLDSTUFF".
2) run MOVE NODEDATA to move this client's data from the primary tape
pool to the OLDSTUFF pool.
3) use MOVE MEDIA to eject the OLDSTUFF tape(s) from the library and
store themt on a shelf.
-This retains the inventory of the client in the TSM DB, you can view it
any time with dsm -VIRTUALNODE or a SELECT on the TSM DB.
-The client's copy pool data is still in the copypool, offsite, managed
as usual.
-The tapes are tracked in the normal way in the storage pool and copy
pool, unlike backup sets and export tapes, which are tracked in volume
history.
- Your primary pool tapes will have space freed up, and go through
recycle, so that you get space back in your library.
If you decide to go to backup sets /export tapes later, you can still do
that by just checking in the OLDSTUFF tapes.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Marco Spagnuolo
Sent: Tuesday, March 22, 2005 11:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backupsets and Export Node
TSM Server 5.2.0.0 running on the Windows platform.
We have some issues at one of our offices. Here's what I've been able
to
decipher:
There are several Netware,Linux and Windows nodes (12 total) that no
longer exist and all hardware has been reused. They require one last
"backup/archive" of these nodes that they want kept around for a couple
of
years. Of course, since these nodes no longer physically exist, my
options are limited to backupsets and export node (I believe). Thrown
into the mix, the IBM 3583 Tape Library is at capacity and an upgrade is
pending but will take some time to get approved.
(1). If I do generate backupsets for these nodes, can I then delete the
filespace data to free up Tape Library space?
(2). If I opt for export node, could I export the nodes, remove all
references to the nodes and re-import to the same TSM server if I ever
need to?
Any other options out there?
I've reads through the numerous posts on Backupsets and Export Node but
none seem to address my concerns.
Thank you
Marco
|
