Forum Discussion

nasahasha's avatar
nasahasha
Level 5
11 years ago

Disable client side deduplication

Regarding deduplication, I found two options 1)Policies(disable client side deduplication) 2)Client attributes(host properties).

How does this both options work together?

If I disable it at policy level, then it wont consider client attributes or it will do media server deduplication?

When I see slow backups sometimes I will change client attribute to "always use media server" and sometimes to "prefer client side deduplication", viceversa and backups will run fast. How to decide which client is good for "media server deduplication" and which is good for "client side deduplication"?

7.6
Backing Up
Backup and Recovery
Basics
Best Practice
Linux
NetBackup
  • RamNagalla's avatar
    RamNagalla
    11 years ago

    Client side dedup require more CPU cycles , so if your client has the enough CPU cycle go with client side dedup..it will reduce the amount of data that needs to travel over the network between the client and media server and jobs will get finish quicky

    if Client does not have more power then use Media server dedup... all data will travel from client to media server and then it will get deduplicated and comit to disk.

    so this is all depends on how infra is capable of and designed..

     

    if you disable in policy level it will not consider it host properties one

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    11 years ago

    Hi,

     

    Let me explain again.

     

    First you set the attribute in host properties

    1. Always use media server
      1. No matter what you tick on the policy this client will always use media server
    2. Prefer Client side
      1. It will use client side if you dont make any changes in the policy
      2. It will use media server if you tick "disable client side" in the policy
  • RamNagalla's avatar
    RamNagalla
    Moderator
    11 years ago

    Client side dedup require more CPU cycles , so if your client has the enough CPU cycle go with client side dedup..it will reduce the amount of data that needs to travel over the network between the client and media server and jobs will get finish quicky

    if Client does not have more power then use Media server dedup... all data will travel from client to media server and then it will get deduplicated and comit to disk.

    so this is all depends on how infra is capable of and designed..

     

    if you disable in policy level it will not consider it host properties one

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hi,

     

    Regarding your first question, the policy comes last. So you would use this to say disable client side dedupe on your SQL Server's MS-SQL-SERVER policy, but retain client side dedupe for the same server's MS-WINDOWS policy (by not selecting disable client side dedupe in the policy, and having it set to preferred client side dedupe in host properties).

     

    As for choosing the deduplication method (source or target), in most cases you would use source (client side) for file system data where there are many smaller files (accelerator enhances this even further), and for larger data sets with fewer files (like databases) you would use media server.

     

    Having said that, its a good idea to test as you've done already to see which method fits your environment best.

     

    Nagalla's comments about processing power play a role as well.

  • nasahasha's avatar
    nasahasha
    Level 5
    11 years ago

    Riaan,

    To consider a scenario, at policy I didnt select "disable client side deduplication" and at attributes I set "Always use media server", now will it do client side or media server.

  • nasahasha's avatar
    nasahasha
    Level 5
    11 years ago

    more CPU cycles??

    How I know if it has enough CPU to do client side deduplication, Is there a easy way to calculate CPU vs data to deduplicate? or Do we have to do lot of math or be a windows admin? 

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hi,

     

    Let me explain again.

     

    First you set the attribute in host properties

    1. Always use media server
      1. No matter what you tick on the policy this client will always use media server
    2. Prefer Client side
      1. It will use client side if you dont make any changes in the policy
      2. It will use media server if you tick "disable client side" in the policy