I am trying to understand how client side dedupe is implemented, what are its pre-requisites etc.
To give a background, I have a OST plugin which does client side dedupe as well as appliance dedupe, we call it as optimized and pass through based on where the dedupe occurs. On a normal scenario we install the plugin on the media server, we configure storage server and OST device and do these backups both optimized and pass through by modifying a conf file setting.
BE gives 3 option for dedupe namely Deduplication storage folder, Open Storage & Remote agent deduplication. To make my appliance OST compliant I need to know which among these can be used.
From the admin guide I read this:-
Client-side deduplication enables a remote computer that is configured as a RemoteAgent for Deduplication to send data directly to an OpenStorage device or a deduplication storage folder. The remote agent is configured with direct access.
Q1) Can I install the OST plugin and remote agent on the client and point to a media server on a different host and run backups of the client.The data sourced by the plugin in the client side will do the dedupe and send the unique data to the disk storage (appliance) directly. The appliance runs OST server component.
Does this work this way?
Q2) Or in above case the dedupe data is send to media server first and then to appliance?
Q3) Or is the external OST plugin not required at all, BE implements client side dedupe in it's own way?
Q4)Both Media server and client side dedupe are software dedupe, are there any difference other than that they happen at different servers and that each has it's own adavantages and disadvantages?
Internally does both operate with the same design or algorithm?
thanks in advance for the comments.