ADSM-L

Re: Offsite Vaulting with Locked Canisters

2002-10-22 17:26:42
Subject: Re: Offsite Vaulting with Locked Canisters
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 22 Oct 2002 17:25:52 -0400
Mark,
Think for a second, if reclaimation supported a days option versus the
current percent utilized option.  If that was the case you could set that
number of days about 7 days less than when the closed boxes are to return
and achieve the goal.

Well, I have written the code to do just that via the MOVE DATA vvvvvv
RECONSTRUCT=YES based on the change date in the drmedia table.  We have been
doing this for about 9 months now, very successfully.

I still use DRM for its management functionality, but I would not require it
to achieve the goal.

Yes, I have quite a few scripts and some elaborate processing to do this,
but it works very successfully.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Mark Stapleton [mailto:stapleto AT BERBEE DOT COM]
Sent: Tuesday, October 22, 2002 4:55 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Offsite Vaulting with Locked Canisters


From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Joshua Bassi
> I am looking for feedback on using locked canisters for offsite
> vaulting.  I have setup DRM for several accounts who used open
> containers and I have setup poor man's tape rotation without DRM with
> open canisters, but I have never implemented a locked canister
> solution.
>
> The problem as I see it is that not all the data on the tapes will
> expire at the same time.  So what will happen is that some of the
> tapes in the canister are available for reclamation and then return to
> the data center, but other tapes will not be available at the same
> time, this will cause the tapes in the canister to be out of sync.
>
> I have thought of 2 ways to potentially deal with this problem:
>
> 1) Every week we can create a brand new copy storage pool and backup
> the primary pools to the offsite pool.  After 3 weeks all the data in
> the pool can be deleted and the tapes brought back onsite.  This is
> not utilizing TSM's incremental backup storage pool feature, but would
> guarantee that a complete set of data was taken offsite each week.
>
> 2) Use either import/export or generate backupset to create fresh
> tapes every week.

You're trying to fit a round peg in a square hole. Why do you want to
implement locked cannister mode? Security?

A backupset *can* be read without a db backup, as long as you're dealing
with like OS platforms. They're much less secure than an offsite pool.
Exports are similarly insecure.

Data from TSM's offsite tape pools cannot be read without a current database
backup and other required TSM server metadata.

--
Mark Stapleton (stapleton AT berbee DOT com)
Certified TSM consultant
Certified AIX system engineer
MCSE