Only a few of our clients do compression before sending backup/archive
data and since clients backup directly to the local primary disk storage
pool with no NTFS compression it should not affect them. Then later as
part of the daily maint cycle the local disk pool will get migrated to
the compressed array. Then as the array fills the data gets migrated to
tape. If we use dev disk there will be no reclamation process but if we
 used dev file then performance for reclamations could suffer. The only
time clients would be impacted by compression is when they do restores
that come from the array which very infrequent. With lots of cpu power I
would think the NTFS compression wouldn't be too much of a issue. I'll
post what I find should we ever get there.

Rushforth, Tim wrote:

The 5.2.2 Performance Tuning Guide says:
"NTFS file compression should not be used on disk volumes that are used by
the TSM server, because of the potential for performance degradation."

We use client compression so I don't think it would buy us anything.

Report back if you try this out!

-----Original Message-----
From: Steve Bennett [mailto:steve_bennett AT ADMIN.STATE.AK DOT US]
Sent: Tuesday, September 21, 2004 12:11 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: disk storage pools and windows compressed file systems

Have any of you used disk primary storage pools which use windows
compressed file systems? Comments on performance, etc?

We are investigating use of a multi TB raid5 array to use as a buffer
between our local primary disk pool and the tapepool. Have seen the
posts regarding file vs disk device classes but what about compression?
Good, bad, etc.

Win 2000 sp4 with TSM server 5.2.3.2

--

Steve Bennett, (907) 465-5783
State of Alaska, Enterprise Technology Services, Technical Services Section

--

Steve Bennett, (907) 465-5783
State of Alaska, Enterprise Technology Services, Technical Services Section