Re: Need to save permanent copy of all files currently being stored
Is all that really necessary?
How about creating a new "permanent retention" domain, copy all relevant
policy sets, management classes, copygroups, etc. to the new domain, but
change all retentions to NOLIMIT. Then move the affected client to the new
domain. Next incremental should rebind all existing data to the new
"NOLIMIT" management classes.
I recently had to do something similar, but for ALL clients. That's right,
ALL we are currently retaining all data permanently, hopefully only
temporarily. One interesting benefit of this excercise is that I now know
from real experience what the media cost is in our environment... and it
approximately doubled our LTO2 media consumption.
Robin Sharpe
"Prather, Wanda"
<[EMAIL PROTECTED]
HUAPL.EDU> To: [EMAIL PROTECTED]
Sent by: "ADSM: cc:
Dist StorSubject:
Manager" Re: Need to save permanent copy
of all files currently being stored
<[EMAIL PROTECTED]
T.EDU>
12/01/2004 11:13
AM
Please respond
to "ADSM: Dist
Stor Manager"
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:[EMAIL PROTECTED] On Behalf Of
Stapleton, Mark
Sent: Wednesday, December 01, 2004 10:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Need to save permanent copy of all files currently being
stored
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 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 y
Re: Need to save permanent copy of all files currently being stored
Hi Richard, yes you can suspend deletion. A bullet on the page says so. But you can't add this feature on to an existing server, so it won't help the original poster. See the redbook at http://www-1.ibm.com/support/docview.wss?uid=rdb2sg24709800 for an architectural overview. It only takes data from the api and needs a content manager type product to front-end it. - bill At 01:49 PM 12/1/2004, you wrote: >On Dec 1, 2004, at 12:18 PM, William F. Colwell wrote: > >>ITSM has announced a special version of tsm to meet regulatory needs. >>I forget the exact details, I think there is an extra charge. >> >>A query license output includes these 2 lines - >> >> Is Tivoli Storage Manager for Data Retention in use ?: No >>Is Tivoli Storage Manager for Data Retention licensed ?: No > >Hi, Bill - The web page is > http://www.ibm.com/software/tivoli/products/storage-mgr-data-reten/ >My reading of it is that it principally just guarantees that the data >won't be deleteable from TSM storage until it expires per retention >policies - but I don't perceive any capability for freezing data, per >se. >At expiration time, the data goes away, as usual. > > Richard Sims -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Re: Need to save permanent copy of all files currently being stored
On Dec 1, 2004, at 12:18 PM, William F. Colwell wrote: ITSM has announced a special version of tsm to meet regulatory needs. I forget the exact details, I think there is an extra charge. A query license output includes these 2 lines - Is Tivoli Storage Manager for Data Retention in use ?: No Is Tivoli Storage Manager for Data Retention licensed ?: No Hi, Bill - The web page is http://www.ibm.com/software/tivoli/products/storage-mgr-data-reten/ My reading of it is that it principally just guarantees that the data won't be deleteable from TSM storage until it expires per retention policies - but I don't perceive any capability for freezing data, per se. At expiration time, the data goes away, as usual. Richard Sims
Re: Need to save permanent copy of all files currently being stored
ITSM has announced a special version of tsm to meet regulatory needs. I forget the exact details, I think there is an extra charge. A query license output includes these 2 lines - Is Tivoli Storage Manager for Data Retention in use ?: No Is Tivoli Storage Manager for Data Retention licensed ?: No Hope this helps, Bill Colwell At 11:50 AM 12/1/2004, you wrote: >On Dec 1, 2004, at 11:13 AM, Prather, Wanda wrote: > >>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'll also add that the lack of a simple way to preserve data, as when >a sudden regulatory or emergency requirement arises, is an, um, >"opportunity for a product feature" (rather than a shortcoming :-). > >A further complication in the poster's need is the ability to capture >Inactive files, which a Backupset can't do. > >A partial, but perhaps satisfactory, measure might be to temporarily >create a "preservation" file system (name appropriately), perform a >-latest restoral of the subject directory into it, and perform a TSM >Archive on that, whereafter the file system can be disposed of. This >will at least capture all of the object names which are and have been >in that directory, in their most recent versions. > > Richard Sims http://people.bu.edu/rbs/ADSM.QuickFacts > > "Think different." -- Apple -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Re: Need to save permanent copy of all files currently being stored
On Dec 1, 2004, at 11:13 AM, Prather, Wanda wrote: 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'll also add that the lack of a simple way to preserve data, as when a sudden regulatory or emergency requirement arises, is an, um, "opportunity for a product feature" (rather than a shortcoming :-). A further complication in the poster's need is the ability to capture Inactive files, which a Backupset can't do. A partial, but perhaps satisfactory, measure might be to temporarily create a "preservation" file system (name appropriately), perform a -latest restoral of the subject directory into it, and perform a TSM Archive on that, whereafter the file system can be disposed of. This will at least capture all of the object names which are and have been in that directory, in their most recent versions. Richard Sims http://people.bu.edu/rbs/ADSM.QuickFacts "Think different." -- Apple
Re: Need to save permanent copy of all files currently being stored
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:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Wednesday, December 01, 2004 10:51 AM To: [EMAIL PROTECTED] Subject: Re: Need to save permanent copy of all files currently being stored From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 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 ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Need to save permanent copy of all files currently being stored
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 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 ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Need to save permanent copy of all files currently being stored
*SMers, 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! - Kevin Kinder 558-5914 x1988
