Re: Eternal Data retention brainstorming.....
2002-08-21 22:33:23
Hi All,
I've just come back from two weeks working on something else and caught up with
the list, and I can't help jumping in with this one even if it's late.
How about
backup TSM DB and shutdown current TSM instance (henceforth this is TSM-A)
create second TSM instance on same physical machine
Restore TSM DB to this instance (henceforth TSM-B)
TSM-B: delete disk volumes, disk storage storagepools, all copypool volumes and
all copypools. Checkout with eject all primary tape volumes. vary all tape
drives off.
TSM-A: checkout without eject all primary volumes. Mark all primary volumes as
destroyed.
TSM-A: continue operations as normal. over time run selectives on all nodes to
repopulate onsite tapes (or recover from copypool)
TSM-B: normally keep this down. during slack tape usage times, bring it up to
run reclaims to a high percentage (say 90-95%) to optimise tape usage, use move
data to refresh tapes etc.
When a new TSM version comes along, apply it to both instances.
This way no new copies of data are needed immediately, TSM versions are kept up
to date, "frozen" tapes are refreshed and restore from the "frozen" versions is
easy and quick.
The only downside is that TSM-A has its derriere exposed to a single tape
failure, although any data should be available from TSM-B if required.
I think that one is about $0.04 worth
Steve Harris
AIX and TSM Systems Admin
Queensland Health, Brisbane Australia.
**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.
Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail. You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: Eternal Data retention brainstorming....., (continued)
- Re: Eternal Data retention brainstorming....., Robin Sharpe
- Re: Eternal Data retention brainstorming....., bbullock
- Re: Eternal Data retention brainstorming....., Prather, Wanda
- Re: Eternal Data retention brainstorming....., Prather, Wanda
- Re: Eternal Data retention brainstorming....., Nicholas Cassimatis
- Re: Eternal Data retention brainstorming....., Prather, Wanda
- Re: Eternal Data retention brainstorming....., bbullock
- Re: Eternal Data retention brainstorming....., Zlatko Krastev/ACIT
- Re: Eternal Data retention brainstorming....., Seay, Paul
- Re: Eternal Data retention brainstorming....., Nicholas Cassimatis
- Re: Eternal Data retention brainstorming.....,
Steve Harris <=
|
|
|