Re: Idea for a TSM feature
2002-02-27 12:12:04
I am sure others will reply, but why not use large cached primary disk
pools?
If you need to, define a separate pool for each "important" client, large
enough to hold a "full" backup. That way, all the active files will usually
be in the pool. (Exceptions will break this, eg a big file that changes
every day may flush out an "old" active file....)
True?
(See TSM Guide for disadvantages of cached pools...)
While I suspect that having active/inactive be in different storage pools
would "break" something in TSM, maybe we could get a "move data node=xxx
type=active" command...
> -----Original Message-----
> From: James Thompson [mailto:mezron AT HOTMAIL DOT COM]
> Sent: Wednesday, February 27, 2002 11:44 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Idea for a TSM feature
>
>
> Thought I would throw an idea I had for a TSM feature out on
> the listserv and get some thoughts no whether this would be useful or not.
>
> The feature that I would like to see is the ability to create
> a special disk storage pool, that would only migrate inactive versions of
> backup objects to the next storage pool. This would keep all the active
> versions on disk storage.
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Idea for a TSM feature, James Thompson
- Re: Idea for a TSM feature, Joe Cascanette
- Re: Idea for a TSM feature, James Thompson
- Re: Idea for a TSM feature,
Richard Cowen <=
- Re: Idea for a TSM feature, Doug Thorneycroft
- Re: Idea for a TSM feature, Alex Paschal
- Re: Idea for a TSM feature, James Thompson
- Re: Idea for a TSM feature, Joe Cascanette
- Re: Idea for a TSM feature, James Thompson
- Re: Idea for a TSM feature, James Thompson
- Re: Idea for a TSM feature, Matthew A. Bacchi
- Re: Idea for a TSM feature, Doug Thorneycroft
- Re: Idea for a TSM feature, George Lesho
- Re: Idea for a TSM feature, Doug Thorneycroft
|
|
|