Re: Retention Request Problem

2005-07-16 Thread Allen S. Rout
==> On Fri, 15 Jul 2005 12:09:10 -0700, Robert Clark <[EMAIL PROTECTED]> said: > [ ... more baroqe than my scheme ... ] Dang. Sir, I bow to you. - Allen S. Rout

Re: Retention Request Problem

2005-07-16 Thread Allen S. Rout
==> On Fri, 15 Jul 2005 13:30:28 -0500, "Miller, Ryan" <[EMAIL PROTECTED]> said: > This will not produce the desired outcome from the request. We have used > this option when it is appropriate, but all this produces is a TSM server > archive of the client, in other words, all you end up with is

Re: Retention Request Problem

2005-07-15 Thread Robert Clark
Just thinking out loud. Do the first two steps you've mentioned. - Disable client access on the TSM server in question - Disable expiration scheduling on the TSM server in question Migrate/copy disk storage pools. Free disk storage pool volumes for use by new instance below. Move the existing ser

Re: Retention Request Problem

2005-07-15 Thread Robert Clark
Just thinking out loud. Do the first two steps you've mentioned. - Disable client access on the TSM server in question - Disable expiration scheduling on the TSM server in question Migrate/copy disk storage pools. Free disk storage pool volumes for use by new instance below. Move the existing ser

Re: Retention Request Problem

2005-07-15 Thread Miller, Ryan
Principal Financial Group Tivoli Certified Consultant Tivoli Storage Manager v4.1 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Friday, July 15, 2005 1:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Retention Request Problem ==&g

Re: Retention Request Problem

2005-07-15 Thread Allen S. Rout
==> On Fri, 15 Jul 2005 09:06:42 PDT, Sam Sheppard <[EMAIL PROTECTED]> said: > Our main customer is having some potential legal problems and has made the > following request: > "I am requesting that all File Server Backups taken prior to June 15, 2005 > be preserved pending further instructions."

Re: Retention Request Problem

2005-07-15 Thread Miller, Ryan
We have had to do several 'saves' like this for similar issues, we have used a variety solutions but it sounds like the easiest thing for you would be to create a new domain. The problem with this, or any other solution, short of restoring all data prior to June 15th and then archiving it again, i

Re: Retention Request Problem

2005-07-15 Thread Stapleton, Mark
The easiest solution is to run an EXPORT NODE to a tape (or set of tapes) for each TSM client affected. Granted, this will preserve everything up to today, but it will contain the data requested. It will not expire, and (most importantly) it will not affect your production environment. -- Mark Sta