Hi Robert,
Yes, if you are ONLY doing client side deduplication there is no reason to run
a process on the server, and you can set your identifyprocess to 0 on the
stgpool.
Dean.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Robert Ouzen
Sent: October-31-11 7:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Question about Deduplcation feature with TSM6
Hi to all
I just beginning to test the DE duplication feature with TSM 6 , I did all the
configuration required
My node name as those parameters: dedup=clientorserver (server side) ,
deduplication YES (client side)
My Storage pool as those parameters: deduplicate=YES , identifyprocess=1
As I understand the manual if the nodename is configure with the option
dedup=clientorserver , during the backup client-side data deduplication
processing, duplicates are identified on the backup-archive client.
So why in the query process I see: need to change the parameter:
identifyprocess=0 ????
sm: POSTBACK>q pr
Process Process Description Status
Number
------- --------------------
-------------------------------------------------
119 Identify Duplicates Storage pool: DEDUP6. Volume: NONE. State:
idle.
State Date/Time: 10/31/2011 12:58:05.
Current
Physical File(bytes): 0. Total Files
Processed:
4. Total Duplicate Extents Found: 0. Total
Duplicate Bytes Found: 0.
Any help or tips on this matter will be appreciate
Here the output of a backup test
10/31/2011 12:58:08 ANE4952I (Session: 11856, Node: DEDUPNODE) Total
number
of objects inspected: 734 (SESSION: 11856)
10/31/2011 12:58:08 ANE4954I (Session: 11856, Node: DEDUPNODE) Total
number
of objects backed up: 513 (SESSION: 11856)
10/31/2011 12:58:08 ANE4958I (Session: 11856, Node: DEDUPNODE) Total
number
of objects updated: 0 (SESSION: 11856)
10/31/2011 12:58:08 ANE4960I (Session: 11856, Node: DEDUPNODE) Total
number
of objects rebound: 0 (SESSION: 11856)
10/31/2011 12:58:08 ANE4957I (Session: 11856, Node: DEDUPNODE) Total
number
of objects deleted: 0 (SESSION: 11856)
10/31/2011 12:58:08 ANE4970I (Session: 11856, Node: DEDUPNODE) Total
number
of objects expired: 0 (SESSION: 11856)
10/31/2011 12:58:08 ANE4959I (Session: 11856, Node: DEDUPNODE) Total
number
of objects failed: 0 (SESSION: 11856)
10/31/2011 12:58:08 ANE4982I (Session: 11856, Node: DEDUPNODE) ANE4982I
Total
objects deduplicated: 337 (SESSION: 11856)
10/31/2011 12:58:08 ANE4977I (Session: 11856, Node: DEDUPNODE) ANE4977I
Total
number of bytes inspected: 301.22 MB (SESSION:
11856)
10/31/2011 12:58:08 ANE4975I (Session: 11856, Node: DEDUPNODE) ANE4975I
Total
number of bytes processed: 244.40 MB (SESSION:
11856)
10/31/2011 12:58:08 ANE4984I (Session: 11856, Node: DEDUPNODE) ANE4984I
Total
bytes before deduplication: 288.07 MB (SESSION:
11856)
10/31/2011 12:58:08 ANE4198I (Session: 11856, Node: DEDUPNODE) Total bytes
after deduplication: 244.15 MB(SESSION: 11856)
10/31/2011 12:58:08 ANE4961I (Session: 11856, Node: DEDUPNODE) Total
number
of bytes transferred: 244.40 MB (SESSION: 11856)
10/31/2011 12:58:08 ANE4963I (Session: 11856, Node: DEDUPNODE) Data
transfer
time: 3.31 sec (SESSION: 11856)
10/31/2011 12:58:08 ANE4966I (Session: 11856, Node: DEDUPNODE) Network
data
transfer rate: 75,555.49 KB/sec (SESSION:
11856)
10/31/2011 12:58:08 ANE4967I (Session: 11856, Node: DEDUPNODE) Aggregate
data
transfer rate: 9,992.35 KB/sec (SESSION: 11856)
10/31/2011 12:58:08 ANE4968I (Session: 11856, Node: DEDUPNODE) Objects
compressed by: 0% (SESSION: 11856)
10/31/2011 12:58:08 ANE4981I (Session: 11856, Node: DEDUPNODE) ANE4981I
Deduplication reduction: 15.25%%
(SESSION:
11856)
10/31/2011 12:58:08 ANE4976I (Session: 11856, Node: DEDUPNODE) ANE4976I
Total
data reduction ratio: 18.87%% (SESSION:
11856)
10/31/2011 12:58:08 ANE4964I (Session: 11856, Node: DEDUPNODE) Elapsed
processing time: 00:00:25 (SESSION: 11856)
T.I.A Regards
Robert
Environment: TSM server V6.3.2.0
TSM client V6.3.0
|
