Hi,
Regarding compression...
I have my TSM server devclass configured this way:
Device Class Name : DISK
Device Access Strategy : Random
Storage Pool Count : 1
Device Type :
Format :
Est/Max Capacity (MB) :
Mount Limit :
Mount Wait (min) :
Mount Retention (min) :
Label Prefix :
Drive Letter :
Library :
Directory :
Server Name :
Retry Period :
Retry Interval :
Twosided :
Shared :
High-level Address :
Minimum Capacity :
WORM : No
Drive Encryption :
Scaled Capacity :
Last Update by (administrator) :
Device Class Name : LTOCLASS3
Device Access Strategy : Sequential
Storage Pool Count : 2
Device Type : LTO
Format : ULTRIUM3C
Est/Max Capacity (MB) :
Mount Limit : DRIVES
Mount Wait (min) : 60
Mount Retention (min) : 60
Label Prefix : ADSM
Drive Letter :
Library : LB0.1.0.3
Directory :
Server Name :
Retry Period :
Retry Interval :
Twosided :
Shared :
High-level Address :
Minimum Capacity :
WORM : No
Drive Encryption : Allow
Scaled Capacity :
Last Update by (administrator) : ADMIN
Last Update Date/Time : 7/2/09 3:42:55 PM BST
----
I have linux "INT44" doing backup of some data "ndsg2" without any compression parameters
and a solaris machine "SUNV210" doing the same backup "ndsg2" with the compression=yes and compressalways=no.
In both cases "q node sunv210/int44 f=d" gives the output "Compression : Client"
(bellow)
Node Name : INT44
Type : Bkup
Filespace Name : ndsg2
FSID : 6
Storage Pool Name : LTOPOOL3
Number of Files : 1,208,640
Physical Space Occupied (MB) : 3,314,976
Logical Space Occupied (MB) : 3,314,975.75
Node Name : SUNV210
Type : Bkup
Filespace Name : ndsg2
FSID : 31
Storage Pool Name : LTOPOOL3
Number of Files : 1,208,640
Physical Space Occupied (MB) : 2,372,604.25
Logical Space Occupied (MB) : 2,372,603.5
--
You can see that the "SUNV210" client occupies considerable less amount of space in the storage pool than "INT44".But since the format is "Format : ULTRIUM3C" shouldn't the tsm server compress the data (on the server side) that came from INT44 ?Can I do something on the server side or i need to reconfigure all my clients with compression parameters ?
Appreciate your help. Thank you,Regards,Marco
Regarding compression...
I have my TSM server devclass configured this way:
Device Class Name : DISK
Device Access Strategy : Random
Storage Pool Count : 1
Device Type :
Format :
Est/Max Capacity (MB) :
Mount Limit :
Mount Wait (min) :
Mount Retention (min) :
Label Prefix :
Drive Letter :
Library :
Directory :
Server Name :
Retry Period :
Retry Interval :
Twosided :
Shared :
High-level Address :
Minimum Capacity :
WORM : No
Drive Encryption :
Scaled Capacity :
Last Update by (administrator) :
Device Class Name : LTOCLASS3
Device Access Strategy : Sequential
Storage Pool Count : 2
Device Type : LTO
Format : ULTRIUM3C
Est/Max Capacity (MB) :
Mount Limit : DRIVES
Mount Wait (min) : 60
Mount Retention (min) : 60
Label Prefix : ADSM
Drive Letter :
Library : LB0.1.0.3
Directory :
Server Name :
Retry Period :
Retry Interval :
Twosided :
Shared :
High-level Address :
Minimum Capacity :
WORM : No
Drive Encryption : Allow
Scaled Capacity :
Last Update by (administrator) : ADMIN
Last Update Date/Time : 7/2/09 3:42:55 PM BST
----
I have linux "INT44" doing backup of some data "ndsg2" without any compression parameters
and a solaris machine "SUNV210" doing the same backup "ndsg2" with the compression=yes and compressalways=no.
In both cases "q node sunv210/int44 f=d" gives the output "Compression : Client"
(bellow)
Node Name : INT44
Type : Bkup
Filespace Name : ndsg2
FSID : 6
Storage Pool Name : LTOPOOL3
Number of Files : 1,208,640
Physical Space Occupied (MB) : 3,314,976
Logical Space Occupied (MB) : 3,314,975.75
Node Name : SUNV210
Type : Bkup
Filespace Name : ndsg2
FSID : 31
Storage Pool Name : LTOPOOL3
Number of Files : 1,208,640
Physical Space Occupied (MB) : 2,372,604.25
Logical Space Occupied (MB) : 2,372,603.5
--
You can see that the "SUNV210" client occupies considerable less amount of space in the storage pool than "INT44".But since the format is "Format : ULTRIUM3C" shouldn't the tsm server compress the data (on the server side) that came from INT44 ?Can I do something on the server side or i need to reconfigure all my clients with compression parameters ?
Appreciate your help. Thank you,Regards,Marco