Good Morning,
I am adding a new LTO3, 3310 library for use with HSM to replace the current
LTO2 library.
The question I have is can you add a second library for use by HSM so I can
migrate the data off the LTO2's to the new LTO3's?
If yes, what are the best practices to do so?
Thanks
Vince
hello group,
I have to implement TSM server. The client actual policy is keep everything
for 2 months and a month copy for a year (standart) and 3 or 5 years fore some
spicial request.
What will be te best way to do that without using to much tape. TSM server is
6.1.4 and client active data
Use the TSM Archive function for exceptional data retention which does not
constitute regular backups.
Richard Sims
On 21 jun 2011, at 17:04, D'Antonio III, Vincent E (N-Aerotek) wrote:
Good Morning,
I am adding a new LTO3, 3310 library for use with HSM to replace the current
LTO2 library.
The question I have is can you add a second library for use by HSM so I can
migrate the data off the LTO2's to
On 21 jun 2011, at 17:45, ritchi64 wrote:
hello group,
I have to implement TSM server. The client actual policy is keep everything
for 2 months and a month copy for a year (standart) and 3 or 5 years fore
some spicial request.
What will be te best way to do that without using to much
Humm!
What about the policy at your site? Can you share something useful?
On 21 jun 2011, at 19:45, remco wrote:
if you have to ask these questions for such a large environment, I'd suggest
finding a real TSM specialist. Somebody who is not afraid to tell the
customer what sensible backup
What Remco is saying that the discussion is much more complicated than the
simple strategy they are currently using. If they have so much data on tape
now, keeping the same strategy will keep too much data on tape in the future
too. So something must change. Keeping a month end copy doesn't
Hello,
I had a student ask me today What happens if you have collocation turned on
for a storage pool that you are deduplicating? I did not know what to answer
because in my mind I thought well, if the data is collocated then I need to
have a copy of that data on that client's tape, otherwise
Tape pools are not de-duped, so that is not a consideration.
On Tue, Jun 21, 2011 at 13:17, Mark Mooney mmoo...@aisconsulting.net wrote:
Hello,
I had a student ask me today What happens if you have collocation turned on
for a storage pool that you are deduplicating? I did not know what to
Doesn't it undup when it goes to tape?
Or am I still living in 5.5 and thinking in VTL dedup?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Mark Mooney
Sent: Tuesday, June 21, 2011 2:17 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L]
So data is deduplicated in a disk storage pool but when it is written to tape
the entire reconstructed file is written out? Is this the same for file device
classes?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew
Carlson
Sent:
Ok then, I will add some detail to the case,
The client as a 10 years restore service level that said, he can restore
everything that was present every night for 2 months. After that, he can
restore only the files that were present at the first friday of the month for a
year.
Two years ago a
Dedup only works in TSM storage pools that reside on disk (specifically
devtype=FILE pools).
If you have data that goes to a dedup pool, then gets migrated off to tape, it
is reduped (rehydrated, reinflated, whatever you want to call it.)
So collocation will still be in effect for that pool.
If it is a file device class with dedup turned off, yes.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark
Mooney
Sent: Tuesday, June 21, 2011 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
So data is
And that's why storage pool planning is very important. The less re-duping,
hydrating, inflating you do the better. Client data to a non-deduped (I
guess that would be a duped) pool that migrates to a deduped pool. But
backup stgpool before the migration happens to avoid the re.
This is where
Cool, Thanks :) I have questions about client dedup. Do you know of any
redbook detail on that?
Thanks,
Mooney
Prather, Wanda wprat...@icfi.com wrote:
Dedup only works in TSM storage pools that reside on disk (specifically
devtype=FILE pools).
If you have data that goes to a dedup pool,
https://www-304.ibm.com/support/docview.wss?context=SSGSG7lang=allrs=2077wv=1loc=en_UScs=UTF-8uid=swg27018576q1=tste_webcastdc=DA410
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark
Mooney
Sent: Tuesday, June 21, 2011 2:53 PM
To:
On 21 jun 2011, at 20:32, ritchi64 wrote:
Ok then, I will add some detail to the case,
The client as a 10 years restore service level that said, he can restore
everything that was present every night for 2 months. After that, he can
restore only the files that were present at the first
Makes perfect sense. However, as you've observed, the cost is too high.
What is required now is a rationalization of the data. Clearly (at least to
those outside the business) not all of the stuff captured in a backup may be
required in the future. You mention VMs. Most of what's in a VM
Even if a FILE devclass has dedup turned on, when the data is migrated,
reclaimed, or backed up (backup stgpool) to tape, then the files are
reconstructed from their pieces.
You cannot dedup on DISK stgpools.
DISK implies random access disk - e.g., devclass DISK.
FILE implies serial access disk
Thank you Wanda! Much Appreciated!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, June 21, 2011 9:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deduplication and Collocation
Ok then remco,
1- What do you think about using two TSM instance on the same backup server.
One for every day short term retention and an other one for the long term once
a month.
2- Somebody suggest only one instance but use the undelete option for long term
retention. I think it will get
On 21 jun 2011, at 21:38, ritchi64 wrote:
Ok then remco,
1- What do you think about using two TSM instance on the same backup server.
One for every day short term retention and an other one for the long term
once a month.
10 days at 1250 euro/day plus expenses and you'll find out ;-)
What do you think about using two TSM instance on the same backup server.
One for every day short term retention and an other one for the long term
once a month.
I have a customer who does that, because they were bought by a non-US parent
company that REQUIREs them to keep a monthly backup
24 matches
Mail list logo
