jharris
ADSM.ORG Member
- Joined
- May 24, 2004
- Messages
- 166
- Reaction score
- 0
- Points
- 0
- Location
- Victoria, Australia
- Website
- Visit site
Hi guys,
For those of you with TSM and Protectier deployment experience, rather than a de-dupe question, I have a compression question.
First of all, we have had the TS7650 running on a TSM 5.5 3-way clustered environment with 7 TSM servers and a TSM library manager for about a month. We've tested direct writing to tape, including lan-free and also the migration of quite a bit of our 3592 media, all without trouble.
Now, the IBM Protectier (Previous Diligent Product) recommends, no client compression / encryption when storing TSM data into the VTL as this maximises the amount of de-duplication possible via the appliance.
I've enabled compression on the the single virtual tape library I've created via the PTManager software to further minimise the back-end disk usage for virtual tape cartridges. As the Protectier is currently emulating LTO3 tape drives, I've defined our TSM device classes with type 'Ultrium3'.
My questions are:
1. Traditionally, although real tape drives are compression capable, the data was not actually compressed on the tape unless the device class was defined as 'Ultrium3c' within TSM. So even though I've enabled compression on the Protectier Library through the PTManager software, will the uncoompressed client data be getting maximum compression on the virtual LTO3 drives, if I have defined my device classes non-compressed?
The Protectier redbooks don't specifically talk about TSM at this level and just states to enable Protectier compression just turn it on for the virtual library created.
2. Also, I can see the current level of deduplication (hyperfactor ration) but where do I see my currently levels of compression being achieved?
For those of you with TSM and Protectier deployment experience, rather than a de-dupe question, I have a compression question.
First of all, we have had the TS7650 running on a TSM 5.5 3-way clustered environment with 7 TSM servers and a TSM library manager for about a month. We've tested direct writing to tape, including lan-free and also the migration of quite a bit of our 3592 media, all without trouble.
Now, the IBM Protectier (Previous Diligent Product) recommends, no client compression / encryption when storing TSM data into the VTL as this maximises the amount of de-duplication possible via the appliance.
I've enabled compression on the the single virtual tape library I've created via the PTManager software to further minimise the back-end disk usage for virtual tape cartridges. As the Protectier is currently emulating LTO3 tape drives, I've defined our TSM device classes with type 'Ultrium3'.
My questions are:
1. Traditionally, although real tape drives are compression capable, the data was not actually compressed on the tape unless the device class was defined as 'Ultrium3c' within TSM. So even though I've enabled compression on the Protectier Library through the PTManager software, will the uncoompressed client data be getting maximum compression on the virtual LTO3 drives, if I have defined my device classes non-compressed?
The Protectier redbooks don't specifically talk about TSM at this level and just states to enable Protectier compression just turn it on for the virtual library created.
2. Also, I can see the current level of deduplication (hyperfactor ration) but where do I see my currently levels of compression being achieved?