Mark's right, there is no GOOD way to do this.
You can't create an "archive" with data that is already on TSM tapes,
except as a backupset, which can be a pain to track and can't be
browsed.
I've done this by using EXPORT along with some management class games
(Mark, if you can find a hole in this scheme, PLEASE let me know!):
* Export THISNODEs filespace that contains the desired directory;
make sure you specify ALL to get the inactive data
* Rename THISNODE to "TEMPCLIENT"
* Import the filespace
* Now you have a second copy of that filespace under the original
name THISNODE
* Rename the imported THISNODE to something new, like
THISNODE-PERM
* Rename TEMPCLIENT back to THISNODE. THISNODE is now back to
normal.
* Copy the POLICY DOMAIN to a new domain called DOMAIN_PERM. Use
COPY, not DEFINE to make sure the management classes have the same
names.
* Change THISNODE-PERM to the new domain (update node
THISNODE-PERM DOMAIN=DOMAIN_PERM; no data actually moves).
* Change the backup copy groups in DOMAIN_PERM so that nothing
ever expires.
* Remember to activate the policy set to make the changes
effective
It's a royal pain in the patootie, because of the time it takes to
EXPORT and IMPORT, and like Mark said, you have to take the WHOLE
filespace. It's something you don't want to do if the node owns
terabytes of data.
BUT, it leaves a perm copy of THISNODEs filespace that can be browsed
with the GUI, restored, etc., by pointing the client to THISNODE-PERM.
And the data is on normal storage pool tapes, so it is managed with
your other copy pool tapes.
And you don't have to mess with tracking the extra EXPORT or BACKUPSET
tapes, or wondering what's on them.
Hope that helps.
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
Stapleton, Mark
Sent: Wednesday, December 01, 2004 10:51 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Need to save permanent copy of all files currently being
stored
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of Kevin Kinder
>I have been ordered to create a permanent copy of one
>directory (including all files and subdirectories that I
>currently have stored on TSM for a particular client. These
>files currently have a 30 day retention, and many of them
>change daily, so I have 30 copies of a number of these files.
>
>What is the best way (any way) to move everything on the
>backed up directory (both active and inactive files and
>folders) over to an archive that has no limits on retention?
>We currently do not utilize archives, only backups, so this is
>my first experience in this area. I've read the client and
>admin reference, but I don't see anything that helps me
>achieve this. Thanks for your help!
Well, you can't archive data from a backup. However, you can do one of
two things:
1. Create a backupset
2. Export the node
Both have drawbacks. They can both be performed at the filesystem level,
but not the directory level. An export does not have an expiration date,
and a backupset's expiration can be set to NOLIMIT. If you do an export,
you probably want to use the FILEDATA=ALLACTIVE flag.
You cannot browse an export in order to perform an import, and an import
will overwrite all data concerning the node. A backupset's contents can
be examined by using the QUERY BACKUPSETCONTENTS command, but you cannot
browse in order to select individual files for restore; the only way to
bring back an individual file is to know the file's nane and the
directory it is located in.
The most pertinent question is: why is a permanent copy needed?
--
Mark Stapleton (stapleton AT berbee DOT com)
Berbee Information Networks
Office 262.521.5627
|
