Druva Blog > Druva News

Druva inSync Roadmap

We receive numerous requests for throwing some light on inSync’s roadmap, so here it is. We have tried to include most of the  suggestions we received from the users. At the same time, we did not go for some features as they do not fit in our vision for data protection. We discuss our view point about some of such  features towards the end of this blog entry. Our focus, as always, is “Light-weight, Simple, Fast and Trustable” backup solution.

Version 2.2 (Oct 10th, 2008)

  1. Admin configured backup folders – The admin can choose “must have” folders for backup for each profile. Can also choose if user can configure more folders.
  2. Browser Restore – Enable user to restore files and folders using just the browser, when he is not at his desk.
  3. Linux Port (beta) – Initially support Ubuntu 8+, openSuse 10+ and RHEL 5+
  4. Advanced Reporting – 6 different reporting option for flexible and detailed reporting.
  5. Dump user data locally (on server) while disabling the user.
  6. Restore user data on server – We plan to allow a dumping user data locally (on server) in case a user is in disabled state. This could be useful for archiving a user’s data before the deleting the user.
  7. Publish configuration API – Publish the server configuration API to enable third party software vendors to integrate inSync backup in their management console.

Version 3.0 (Dec 21th, 2009)

  1. Full PC Backup – Use de-duplication to effectively backup entire PC (operating system, application executables in addition to the application configuration and data)
  2. Bare-metal Restore – Use restore points created by full PC backup to restore a machine that does not have a working operating system.
  3. Performance Improvements – for large (1GB+) file incremental backup.
  4. Search in Restore – Search files in restore.

Excluded Features

The features which we believe should not be implemented even though some key players offer them –

  1. Disable inSync client’s desktop visibility – Don’t show the inSync client running on the the user’s PC to hide backup. In our opinion, this is not a solution. The right approach is to provide a light weight backup solution that does not hamper the PC performance and hence, the user does not want to disable it.
  2. Server initiated backup– It is not useful for the PC backup environment, especially for mobile laptops that are not always connected. we may consider this for the server version of inSync.
  3. Allow USB backup or tape backup on users PC – We believe that media based backup is inherently unusable. With falling disk prices and Druvaa’s data de-duplication technology, the best backup policy is to maintain backups on hard-disks.


  1. TC 12 years ago

    I was promised Linux port and admin side folders two months back. I hope you stick to this date now :)

    Linux backup should have big market here in europe.

    v2.2 seems like a big release. Is there a beta for 2.2 or 3.0 ?

  2. Milind 12 years ago

    Admin side folders is addressed in 2.2. It’s the first item in the list.

    We are planning a controlled beta for Linux, tentatively by Oct 15. Keep watching the blog space.

    Beta is not planned for 2.2. We’ll certainly have it for 3.0.

  3. Aciampoli 12 years ago

    Automatic push to client when changes in the profile are detected.

    If I need to add a new folder to the backup right away, I need to make the changes and then generate a new key for every user. Then update the key on every laptop.

    This is ok for a small office but I have over 40 laptops in 5 different countries getting this done very quickly is almost impossible.

    If the update could get propagated to the user automatically that would make management and deployment so much simpler.

  4. Jaspreet 12 years ago


    This happens even now, profile changes are automatically pushed/applied to the client when the client requests a new backup.

    inSync is a client triggered backup architecture, where client always initiates all requests. So, before any new backup request, the client downloads and updates any new profile changes.

    The client triggered architecture has various advantages –
    1. Backup over WAN/Internet (where client doesn’t have visible IP)
    2. Secure – server never initiates a out-bound request.
    3. Scalable – backup intelligence is embedded into the client and hence load is distributed.

    I hope this information helped.

    – Jas

  5. Pete 12 years ago

    I have been testing this for a month, very smooth backup almost invisible.

    Can you please elaborate on new reporting ?

    Mac support ?

    What is the max. scalability of v2.2 on single backup server (4-core machine, 4 GB RAM) ? Can it take load for 500+ ?

  6. Faisal 12 years ago


    The new reporting mechanism is basically streamlining the current reporting process into something we can expand on fairly easily. For starters, we now have an idea of alerts and notifications. We have classified alerts into different levels of severity. This allows us to handle notifications and behavior with more fine-grained control. With subsequent releases, we hope to fine-tune this and allow more user control with the whole notification and reporting engine.

    W.r.t Mac support, it’s definitely in the pipeline. But I can’t commit on a date for that.


  7. Aciampoli 12 years ago

    Just wondering if 2.2 has been released yet.

  8. T Walton 12 years ago

    Started testing v2.1.1 this week.

    Have been using BackuExec DLO for some time.

    New features in v2.2 seem to resolve issues I already have. When are we likely to see this so we can test it?

  9. Jaspreet 12 years ago


    thanks for trying insync.

    the v2.2 would be available on the website in a day or so